Re: Moving Active Directory in Windows 2000 into a new server
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Sun, 3 Dec 2006 10:47:50 -0600
"Wessam" <Wessam@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A433FA47-7212-43B2-A16C-2C20DBE23C36@xxxxxxxxxxxxxxxx
Hello there,
I wonder if some can help please.
I have we have a Windows 2000 active directory which has been treated very
badly over the years. I want to move it into another Windows 2000 server.
Is there anything actually WRONG with it?
How do you know?
DCDiag and RepAdmin (or ReplMon GUI) can help.
Is there a list of commands any where that would help me to?
a) Repair it and check for its consistency?
DCDiag and RepAdmin
[Technically NTDSUtil might be useful but its
repair facilities are NOT to be used as long as
you have other options.]
b) Do the migration?
I would suggest NOT migrating (technically a
migration refers to moving to a new domain.)
You might consider
c) Move the FSMO Roles?
GUI tools* or NTDSUtil is actually easier when
moving all 5 roles.
* All three of:
AD Users and Computers
AD Domains and Trusts
AD Schema Editor
d) Move DNS?
Build another copy of the Zone (AD Integrated or
just a Secondary) to transfer this to another DNS
server.
e) Move DHCP?
If you have enough addresses to spare it is easier
to just create a new DCHP server and scope with
different addresss range. Moving it possible but
a pain.
The problem is to know what to expect.
Probably no problems. AD is very resilient; most
AD 'problems' are actually DNS issue.
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
.
- Follow-Ups:
- Prev by Date: Re: Cannot sync Server2 with Server1 Domain
- Next by Date: Re: Moving Active Directory in Windows 2000 into a new server
- Previous by thread: Cannot sync Server2 with Server1 Domain
- Next by thread: Re: Moving Active Directory in Windows 2000 into a new server
- Index(es):
Relevant Pages
|
