Guest JPCLYONS Posted September 4, 2007 Posted September 4, 2007 Can anyone point me to a references for replacing a Windows 2000 server with a Windows 2003 server? I need a step by step guide - since this project was inherited and my credentials right now are just an MCP. The current server is in a mixed mode Active Directory structure. It is the PDC, DNS and file server. The new Windows 2003 server will replace all these functions. So far, I have installed the server in the rack, assigned the two NICS with IP's, and gotten all service packs. It is still in WORKGROUP - I have not added it to the domain. Without disrupting logins, DNS, etc, I need to know the sequence of how to proceed. I do not want DHCP on, or any other services that are not absolutely essential. I also realize that this answer might already be somewhere on these forums, and I will look, it's just that I do not want this to linger, as the old server has hardly any disk space - the new one has 400 gigs. Any and all answers will be gratefully appreciated. Jim Lyons J P C LYONS AT GEE MAIL DOT COM
Guest Meinolf Weber Posted September 4, 2007 Posted September 4, 2007 Re: Windows 2000 Server - replace with Windows 2003 server Hello JPCLYONS, - on the 2000 DC, if not done, make DNS as Active directory integrated zone, easier for administration and replication - on the 2003 server, point DNS on the NIC only to the 2000 DNS server - prepare the schema master 2000 for the new schema with adprep /forestprep adprep /domainprep from the 2003 installation cd with an account that is member of the schema admins - run dcpromo on the 2003 server, make it DNS server and check that DNS is active directory integrated, let it time for replication from DNS - if the new one is ready so far, run dcdiag and netdiag against the new server to check for errors - if no errors make it a global catalog server Open Active directory site and services, go to Sites, default first site name, servers, choose the server, right click NTDS settings, open properties and checkmark Global catalog (check event viewer after it, in Directory service you must find event id 1110 and 1119) - move the 5 FSMO roles to the new 2003 machine, check in eventviewer>directory services for entries about success or failure http://support.microsoft.com/kb/324801 - check again with dcdiag and netdiag for errors - change DNS settings from the new server to point to itself as primary server, change the 2000 machine to point to the new 2003 server as primary DNS server - give it some time and test that your environment it still running, web, shares, login etc. Also again dcdiag and netdiag - do not forget to reconfigure your clients for the new DNS server - if you have done all your server preparation, you can copy your data to new locations with keeping your security settings with xcopy or robocopy - if everything is ok, you can start demoting the old server, do NOT delete them from AD, run dcpromo on the 2000 DC and follow the wizard, read carefully. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. > Can anyone point me to a references for replacing a Windows 2000 > server with a Windows 2003 server? > > I need a step by step guide - since this project was inherited and my > credentials right now are just an MCP. > > The current server is in a mixed mode Active Directory structure. > It is the PDC, DNS and file server. The new Windows 2003 server will > replace all these functions. > So far, I have installed the server in the rack, assigned the two NICS > with IP's, and gotten all service packs. It is still in WORKGROUP - I > have not added it to the domain. > > Without disrupting logins, DNS, etc, I need to know the sequence of > how to proceed. > > I do not want DHCP on, or any other services that are not absolutely > essential. > > I also realize that this answer might already be somewhere on these > forums, and I will look, it's just that I do not want this to linger, > as the old server has hardly any disk space - the new one has 400 > gigs. > > Any and all answers will be gratefully appreciated. > > Jim Lyons > > J P C LYONS AT GEE MAIL DOT COM >
Recommended Posts