Archived from groups: microsoft.public.win2000.active_directory (
More info?)
"Tomi" <pops@pops.com> wrote in message
news:erTw5dUZFHA.3572@TK2MSFTNGP12.phx.gbl...
> need a step by step AD guide that will answer my questions in what is does
> and what we'll need to do - set it up
> as we are on Novell 5.1 currently
How about this?
Active Directory Step-by-Step Guides
<http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies
/directory/activedirectory/stepbystep/default.mspx>
Technically you posted to a Win2000 newsgroup but I sent you
the Win2003 link since you really should plan to use Win2003
for new domains or new installs.
Use a Google search like this to find such items for most major
subsystems:
[ "active directory" "step by step" site:microsoft.com ]
Add 2000 or 2003 to specify the OS version:
[ "active directory" "step by step" 2003 site:microsoft.com ]
You can search the built-in help for both "step-by-step" and
"checklist" using such searches as:
[ Active Directory checklist ] or
[ Active Directory step-by-step ]
(again, most any interesting subsystem of the OS has a 'checklist'.)
Basically you will install a Server, then run DCPromo. You should
just install one now and try it. Later you can run DCPromo and turn
the DC back into a regular server (as many times as you wish.)
Note: Any time you remove the 'last DC' from a domain you destroy
that domain but for test purposes this is usually exactly what you wish
when practicing.
After you have a domain, you can DCPromo additonal Domain
Controllers etc.
You will need dynamic DNS but Windows Server is perfectly willing
to set that up for you during DCPromo.
Here are guidelines for DNS to work for AD (for your later production
domain OR for any lab test machines):
[We will be happy to help with any specific question or you can even
call me if you get confused or just wish to get a quick start....]
DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)
netdiag /fix
....or maybe:
dcdiag /fix
(Win2003 can do this from Support tools):
nltest /dsregdns /server
C-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/
Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.
Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.
Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
Facebook
Twitter
Instagram