How to setup new 2012 R2 server as primary domain controller and demote 2008.
We bought a new server with 2012 R2 on it to replace a 2008 SBS server. They are both on the same subnet and I have already made the 2012 a domain controller and AD is replicating. What are the steps to demote the 2008 server and make the 2012 the primary domain controller.?
Stuart
You need to install the 2012 r2 server as a DC in an existing domain. SBS will need to retain the FSMO roles however when you are ready to you can dcpromo the SBS server and the 2012 will become your primary. Check this out - http://blogs.technet.com/b/sbs/archive/2007/10/04/debunking-the-myth-about-additional-domain-controllers-replica-dcs-in-an-sbs-domain.aspx
Its important to manually transfer the FSMO roles prior to demoting the SBS server. Manually transfer the roles and make sure to wait a bit to allow all the roles to rep;icate.
Scott
Scott
First, I assume you're not using Exchange anymore.
To do this properly:
1. Perform a FULL backup on the existing server. TWICE. Just to be safe.
2. Run DCDIAG /C /E /V on the existing DC. Resolve any unexplained errors.
3. Add the 2012 server to the domain.
4. Promote the 2012 server so that it is a DC in your network.
5. Wait a day and run DCDIAG /C /E /V on both servers. Resolve any unexplained errors.
6. Transfer / migrate / re-setup everything on the new server - files, printers, DHCP, etc.
7. Once everything is off the SBS server, SHUT IT DOWN. DO NOT Demote or transfer roles.
8. If everything works fine with the SBS server off for a day, turn it back on and transfer the fsmo roles.
9. Demote the SBS Server and remove it from the network.
10. Run DCDIAG /C /E /V and confirm everything is ok.
Done.
Now, if you want an honest professional opinion, keep reading. If not stop here.
If you do not know how to do more than 2 of the steps above, then hire a pro. Or spend a few months setting up test labs and practicing this. Otherwise, MAYBE it works fine... but maybe it doesn't and recovering from messing this up probably costs you a lot more in down time and consulting/repair fees.
To do this properly:
1. Perform a FULL backup on the existing server. TWICE. Just to be safe.
2. Run DCDIAG /C /E /V on the existing DC. Resolve any unexplained errors.
3. Add the 2012 server to the domain.
4. Promote the 2012 server so that it is a DC in your network.
5. Wait a day and run DCDIAG /C /E /V on both servers. Resolve any unexplained errors.
6. Transfer / migrate / re-setup everything on the new server - files, printers, DHCP, etc.
7. Once everything is off the SBS server, SHUT IT DOWN. DO NOT Demote or transfer roles.
8. If everything works fine with the SBS server off for a day, turn it back on and transfer the fsmo roles.
9. Demote the SBS Server and remove it from the network.
10. Run DCDIAG /C /E /V and confirm everything is ok.
Done.
Now, if you want an honest professional opinion, keep reading. If not stop here.
If you do not know how to do more than 2 of the steps above, then hire a pro. Or spend a few months setting up test labs and practicing this. Otherwise, MAYBE it works fine... but maybe it doesn't and recovering from messing this up probably costs you a lot more in down time and consulting/repair fees.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I'm going to Echo Lees comments here.
ASKER
I've run into an issue where the NETLOGON folder is missing on the 2012. I haven't transferred roles. I've tried restarting particular services but no NETLOGON. Any ideas?