This is not a feature that has been asked for by any of my
users as everyone has their own PC and work area. This
sounds like going part way toward a terminal server
approach. If I joined each PC to the domain anyway are
there any *other* drawbacks or benefits?
If you back up anything the
From: Craig White [EMAIL PROTECTED]
It's rather unfair to ask such basic Windows
Administration questions to this list. This is a samba
list and there are thousands of books, millions of web
pages, endless classes and certifications directed towards
the advancement of the Microsoft Networking
From: Greg Talbot [EMAIL PROTECTED]
Bruce,
I would implement a domain if you have 75 users. 3-5
then no, but if you have been using NDS you are going to
want more control over that many users, i.e. central
logins, and even profile policies if you have to support
the desktops. Plus
I've set up a test Samba PDC with a few test shares. From
the first Windows PC I logged on to a local computer account
and mapped drives to the shares on the Samba PDC. From the
second Windows PC I joined the domain and used a logon
script to connect to the shares.
My question:
What are the
Once a windows computer is joined to the domain, it will use the PDC to
authenticate for everything, so centralising the user accounts. There is
no need to have local accounts on the clients. If you have few accounts
then this isn't so much of a bonus
Also, there are other nice features of
[EMAIL PROTECTED] wrote:
I've set up a test Samba PDC with a few test shares.
From the first Windows PC I logged on to a local
computer account and mapped drives to the shares on the
Samba PDC. From the second Windows PC I joined the
domain and used a logon script to connect to the
On Sat, 2004-07-24 at 11:11, [EMAIL PROTECTED] wrote:
OK. So by joining a PC to the domain anyone with an account
on the Samba PDC can log onto that PC. And, if I also
configure roaming profiles the users personal settings will
also be loaded. Did I understand this correctly?
---
yes
---
