I know that you will be giving me the same advice about "read the
document"
Why do you say that? I have a strong tendency to offer short, clear
explanations
of various topic (sometimes with references) while others are much better at
providing links to documents (I don't have all those bookmarked nor
memorized.)
but I have NEVER been so frustrated as I have been when I try to read the
doc on AD.
Which doc on AD? AD is a big subject, with many -- both good and bad --
explanations for each area.
The TOTAL lack of examples (at least in what I have read) leave
you guessing as to what to do.
What do you wish to accomplish?
And then the example of a domain name like
"blah.microsoft.com". Yah, that makes sense to name my domain
"...microsoft.com". ?????????
I don't think that *I* use examples ending in Microsoft.com that often;
usually I use "Domain.Com" or (my) LearnQuick.Com or YourDomain.Com
Can you suggest a source of GOOD doc/explanation of AD?
Active Directory is -- first and foremost -- and ACCOUNTS Database.
Database means a place where you can store & lookup (account)
information.
It replaces the earlier NT SAM (security account manager) database
It has User, Computer, & Group accounts as well as the new "Organization
Units"
which allow an adminstrator to more easily delegate and set options
for the users
and computers
And more -- it includes other objects for managing the domain itself and
the network
It is also extensible
(the schema or rules about what can and cannot be stored in AD can
be extended)
What type of other objects? Group Policy is the best example of a new type
of object
that makes management easier for the Domain or for the individual OUs
Group Policy allows the administrator to (from a central console):
Deploy software and updates to computers or users
Set Security settings and run Startup/Shutdown & Logon/Logoff
Set other System and Application options using Administrative
Templates to modify
almost anything that can be controlled through the registry.
What other major differences does AD provide?
Multi-Mastered database & replication
In NT only the PDC can accept or make changes to the database
In AD any DC (not BDC) can accept changes and replicate these to
it's partners
Site based replication control
In NT, all changes were replicated from the SINGLE master PDC to
each BDC
In AD, changes are replicated almost immediately to other DCs in
that site and...
...administrators control the frequency and schedule of the
(compressed)
replication between automatically selected DCs (bridgehead
servers) in each
site with another in the (usually adjacent) sites.
Changes can be made on any DC and they are efficiently replicated.
What do you want to do today?
