Before remove the "old server" Check:
- If the server is member of DFS.
- If it's DNS server.
- If it holds any Master Roles.
- If you're migrating form 2000 to 2003 then: Before you upgrade your AD
domain you need to make sure you understand what exactly exists in the
domain. There is a change in 2003 that enables SMB signing for all
communications, if you have clients that can't communicate at this level
then you need to either disable this or upgrade your clients. This includes
appliances such as Fax servers, etc. Clients such as Win98, ME and NT will
need to load the DSClient..
Common Mistakes When Upgrading a Windows 2000 Domain To a Windows 2003
Cannot Upgrade Windows 2000 Server to Windows Server 2003 with Windows
Services for UNIX 2.0 Installed
Incorrect Schema extension for OS X prevents ForestPrep from completing in
- If exchange 2000 exists in the forest you need to be aware of possibly
mangling three specific attributes:
Windows Server 2003 adprep /forestprep Command Causes Mangled Attributes in
Windows 2000 Forests That Contain Exchange 2000 Servers
I hop that helps
Post by firstname.lastname@example.org
I work in an AD environment rather simple : we got international
branches that have their own domain controller. The domain is unique
and looks like "corp.company.local".
I have to migrate one those DC on a new machine. What is the right way
to do the migration ?
I assume i have to put out of the network the DC, then bring up the new
one, run a dcpromo and wait for replication...Is that all ?