If you search either the TechNet (
http://www.microsoft.com/technet) or MSDN
(
http://msdn.microsoft.com) websites you'll find much detailed information
on setting up domains, domain controllers and Active Directory - but in a
nutshell:
When you have a "Peer-to-Peer" network (like yours currently is configured),
each PC stores its own security information. It has the list of who is
permitted to log onto it, who may access files and folders, and so on.
There is no central security database, so each PC must be configured
separately.
When you establish a domain, one or more servers (known as domain
controllers) hold a central security database. This database is accessed by
each domain member when a user logs on and it will determine who can log
onto each PC, what shared files and folders are accessible to users, and so
on.
You could conceivably configure each PC as you want without a domain but the
problem then would be that any PC user could change your
carefully-considered settings. In a domain the security is central to the
domain controller(s) so each user has only the rights you give them and no
others. Short of guessing or stealing the domain administrator password
they would be unable to alter your security settings.
--
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
yba02 said:
Thanks Richard and pleasure to have a MVP attending my inquiry.
In fact, yse, my network is setup as a domain. Can u please elaborate on
the steps or any page where I can find detailed resources on the steps to
do
so.
Thanks in advance.
yba
Richard G. Harper said:
If you set your network up as a domain you can limit users to which PCs
they
can log onto with Active Directory. Otherwise you'll need to create user
accounts on each PC and enforce logon for each PC.
--
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
yba02 said:
Hi,
I have a network of 10 PCs and a file server running Windows Server
2k3.
I need to bind the user to a his unique PC. That is, if any user tries
to
logon to the system from any PC apart from his designated one, he won't
be
allowed in.
One way to this is to activate BIOS password at startup. But this
looks
very premitive. Any idea out there on how to do this on server, rather
than
PC, lever?
Thanks
Yba
