Printable View
Hello,
We are planning to migrate a Windows 2000 AD that have an Exchange 2003 server to Windows 2003 AD while keeping the MS exchange server 2003 in place.we have 2 windows 2000 additional DC's.
i need to know the steps to complete this migration.
Thank you
Najeem.
see here for more suggestion : http://forums.techarena.in/active-directory/1062821.htm
http://forums.techarena.in/active-directory/420155.htm
How to replace single domain controller in domain with a single domain controller?
The following article describe a guidelines to replace exiting Windows 2003
Domain Controller with a new server.
The article assume the following pre-requirement settings.
1. There no Exchange/SQL server etc. on the current Domain Controller.
2. There only one domain, and there only one domain controller function as:
DHCP/WINS/DNS/File Server/Print Server.
3. The source server using regular (No SBS) Windows 2003 Standard or higher.
The following steps need to be taken to replace the exiting Domain Controller.
1. Install the Windows 2003 Standard or higher on a new server.
Tip: You will need to setup the current Domain Controller as DNS server.
2. Promote the new server to become Domain Controller (in the same domain).
Step-by-Step Guide to Setting Up Additional Domain Controllers
http://www.microsoft.com/technet/pro.../addomcon.mspx
3. Promote the new Domain Controller to be "Global Catalog" and reboot the server.
Enable or disable a global catalog
http://www.microsoft.com/technet/pro...910575f61.mspx
4. Install DNS server on the new Domain Controller.
How To Integrate Windows Server 2003 DNS with an Existing DNS Infrastructure in Windows Server 2003
http://support.microsoft.com/kb/323417
How To Install and Configure DNS Server in Windows Server 2003
http://support.microsoft.com/default...b;en-us;814591
5. Set the local IP of the new Domain Controller as DNS server.
6. Option - Install WINS service on the new Domain Controller and change
the Domain Controller IP settings to point on the local IP as WINS server IP.
Tip: You can migrate the current WINS database to the new server.
How to migrate a WINS Database from Windows 2000-based WINS server to a Windows 2003-based WINS server
http://support.microsoft.com/default...b;en-us;875419
7. Move FSMO rules to the new Domain Controller.
How to view and transfer FSMO roles in the graphical user interface
http://support.microsoft.com/default...b;en-us;255690
8. Demote the original Domain Controller from using as "Global Catalog" and reboot the server.
Enable or disable a global catalog
http://www.microsoft.com/technet/pro...910575f61.mspx
9. Demote the original Domain Controller from using as "Domain Controller".
10. Migrate printer settings from the old server to the new one by using "Windows Print Migrator 3.1" tool.
Microsoft Windows Server 2003 Print Migrator 3.1
http://www.microsoft.com/WindowsServ...grator3.1.mspx
11. Migrate File Server settings from the old server to the new one by using "Microsoft File Server Migration Toolkit".
Microsoft File Server Migration Toolkit
http://www.microsoft.com/windowsserv...ocs/msfsc.mspx
12. Install DHCP server on the Domain Controller and migrate the DHCP settings from the old server.
How to move a DHCP database from a computer that is running Windows NT Server 4.0, Windows 2000, or Windows Server 2003 to a computer that is running Windows Server 2003
http://support.microsoft.com/default...b;en-us;325473
Tip: Don’t forget to set the new Domain Controller as DNS & WINS (Optionally) for the DHCP scope/s.
13. Edit users profiles and/or user logon scripts to point to the new Domain Controller as File Server and
Printer server.
14. Uninstall unnecessary services from the old Domain Controller.
15. Install third party tools on the new Domain Controller (Backup Software, Antivirus etc.)
16. Re-register users computers in the new DHCP by using ipconfig /release and ipconfig /renew.
Quote:
Originally Posted by najeemnh
just checkout below it may help you a bit.
http://support.microsoft.com/kb/325379
Windows 2000 DC called ms-mvps with a Windows 2003 DC called chicagotech. He just promote to Windows 2003 server to a domain controller Now, he asks for an assistance to transfer all DC role, DNS, WINS and DHCP from Windows 2000 DC to the 2003 DC.
These to transfer all DC role, DNS, WINS and DHCP from Windows 2000 DC to the 2003 DC, but 2003 server doesn't function like DC. We experience the following issues when we shutdown the Windows 2000 DC for a test:
- Some users can’t logon with “no domain available” message.
- Some user logon but not logon script running to map the network drives.
- Using set command on the workstations displays Logonserver is ms-mvps (2000 DC) instead of chicagotech (2003 DC).