Domain Network or P2P?

[Mike]

We have a closed network (NT Server PDC & seven work stations) We upgrade
the server hardware & and Server 2003 OS.
What are the compelling reasons to setup the server as a true server vs
P2P?. Where can I d/l instructions foer setting up the server 2003 OS?

Thanks,

Mike

 

[Mike]

For the foreseeable future no more than 10 PC, including server will be on
the network

 

[Richard G. Harper]

Both TechNet and MSDN have many Windows Server 2003 resources available, you
can also start your research at the Windows Server page:

http://www.microsoft.com/windowsserver2003/default.mspx

The main problem with a peer-to-peer network is that managing identities and
rights will shift from the domain controller to the individual computers on
the network. If PC1 will have a printer that you want others to access you
will need to go to PC1 and add (and keep updated) all the usernames and
passwords of accounts whose users will be authorized to use that printer.
Same for file shares. But in a domain, the domain controller handles the
user list and all member computers can refer to this single definitive
source for permissions and rights.

--
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

 

[Mike]

Both TechNet and MSDN have many Windows Server 2003 resources available,
you can also start your research at the Windows Server page:

http://www.microsoft.com/windowsserver2003/default.mspx

The main problem with a peer-to-peer network is that managing identities
and rights will shift from the domain controller to the individual
computers on the network. If PC1 will have a printer that you want others
to access you will need to go to PC1 and add (and keep updated) all the
usernames and passwords of accounts whose users will be authorized to use
that printer. Same for file shares. But in a domain, the domain
controller handles the user list and all member computers can refer to
this single definitive source for permissions and rights.

--
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

Thanks for clearing that up and the useful link.

Mike

 

[Richard G. Harper]

You're welcome.

--
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

Both TechNet and MSDN have many Windows Server 2003 resources available,
you can also start your research at the Windows Server page:

http://www.microsoft.com/windowsserver2003/default.mspx

The main problem with a peer-to-peer network is that managing identities
and rights will shift from the domain controller to the individual
computers on the network. If PC1 will have a printer that you want
others to access you will need to go to PC1 and add (and keep updated)
all the usernames and passwords of accounts whose users will be
authorized to use that printer. Same for file shares. But in a domain,
the domain controller handles the user list and all member computers can
refer to this single definitive source for permissions and rights.

--
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

Thanks for clearing that up and the useful link.

Mike