Change from peer network to client/server??

[marsha]

Those who have followed my other posts know that we are using
a simple peer-to-peer setup right now with a single folder on one
computer that is the data source that a special program keeps track
of. The users add to and change the data in that folder. Naturally,
they have to be able to access the folder.

There are now 6 users. We have purchased a new computer to be
the server and Windows 2003 Server (or will when the boss returns
from vacation).

The question is should we go to a Domain situation with Active Directory.
All the users have the same privileges. The can read, write, change data
in that folder. They shouldn't mess with anything else on the server.
Considering
the simplicity of our needs, should I set up an Active Directory which I
gather
implies setting up Domains. We do have two xp home machines but I don't
mind changing them out to either w2k or xp pro in order for them to work as
part of the domain.

Thanks!!!!!!!!!!!!!

 

[Richard G. Harper]

If you are working happily without a domain, then continue to do so. Keep
in mind that the main thing that an Active Directory domain will bring you
is centralized management - management of identities and credentials,
security, software deployment, and so on. If you need none of these then
you don't need Active Directory.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[Frankster]

Those who have followed my other posts know that we are using

a simple peer-to-peer setup right now with a single folder on one
computer that is the data source that a special program keeps track
of. The users add to and change the data in that folder. Naturally,
they have to be able to access the folder.

There are now 6 users. We have purchased a new computer to be
the server and Windows 2003 Server (or will when the boss returns
from vacation).

The question is should we go to a Domain situation with Active Directory.
All the users have the same privileges. The can read, write, change data
in that folder. They shouldn't mess with anything else on the server.
Considering
the simplicity of our needs, should I set up an Active Directory which I
gather
implies setting up Domains. We do have two xp home machines but I don't
mind changing them out to either w2k or xp pro in order for them to work
as
part of the domain.

Thanks!!!!!!!!!!!!!

First, I agree with Richard's post.

In your scenario, the main disadvantage of a workgroup is user management
(not centrallized). You will have to ensure, manually, that each user has a
userID/pswd on the server as well as on their own machine. Also, on any
other machine where they might need to logon. Also, if you change
passwords, you'll have to change the password on every machine where that
userID exists.

If you are happy with the above, keep it simple with workgroup.

If you prefer more centralized management, install a domain. When you
install W2K3 as a domain controller, it must use DNS (required by AD). That
means you will also have to become somewhat familiar with DNS. Especially if
you are allowing Internet access to your users from this network. AD,
itself, can be just left alone, you don't really have to configure it or
learn much about it if you don't need to separate groups. You can continue
to use NTFS file permissions just as before and pretty much ignore AD if you
choose.

-Frank

 

[Phillip Windell]

Well I say go with the Domain. Keep it simple, go with the Defaults,..don't
do something just because it is "there" or because you "can".

I suggest this for one particular reason,...you will have less strange
behavor like what most of your posts have been about. And then we will be
able to help easier than we can with the convoluted mess that workgroups
create. So I guess I am suggesting it for selfish reasons