SVAdmin Posted July 31, 2015 Posted July 31, 2015 (edited) I have the image installed and working on the new server off the network at this point. The old server is still on the network and running. There is also a bdc. I need to know the process to remove the old and replace with the new. This is my thinking: 1. Down grade both the old pdc & new server (since the image was made while it was the PDC) 2. Remove the old server by shutting it down and disconnecting it 3. Connect the new server on turn it on 4. Promote it back to the pdc Is all this necessary? Are more steps required? I apologize for posting in the 2008 server thread & not the 2003 thread. Edited July 31, 2015 by SVAdmin
3s-gtech Posted July 31, 2015 Posted July 31, 2015 You need to: Update the schema for your domain to support the new DC Promote the new DC Move the FSMO roles across Make sure no roles are left on it Demote it Check again that it's not running anything! DNS, DHCP, file and print services etc Turn it off. Check again. Relax.
SVAdmin Posted July 31, 2015 Author Posted July 31, 2015 Thank you for that information. A couple of questions. The new DC is still 2003 & has the same name, etc. since it is a clone of the old sever. Would that still require updating the schema? Will it work without even demoting it since I'm replacing it with an exact copy of itself?
3s-gtech Posted August 1, 2015 Posted August 1, 2015 That's an unusual situation! My first point must be that 2003 is an end-of-life product without security updates. I wouldn't even recommend having it on the network, let alone on a DC! You won't need to update the schema, though no harm in doing so. I guess you're effectively just moving the server across. Again, no you won't need to demote, promote or anything. As you said, just turn old one off, turn new on, give it the same IP address, away you go. I got the wrong end of the stick there. I would say - consider virtualising if possible - keep your existing DC, use the new hardware to virtualise if possible, update to a newer version of Windows Server, and go from there. Just a matter of extra cost in licensing. I'll repeat though. Server 2003 is end of life, and I recommend you retire it ASAP.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now