dustaine
asked on
Removing a secondary 2008 R2 DC
I have a domain that is at 2008 R2 Functional Level with 2 Domain Controllers. This Domain is part of a trust relationship with another domain. The DC's also perform the function of DNS and DHCP. I have a secondary DC that does not house the FSMO roles acting a lot flaky. I am thinking about removing this machine as a DC and removing it from the Domain Then re-adding it and re-adding the role of DC. What process do I need to follow? What kinds of issues can I expect? Would it be better to recreate the machine (It is a VM on ESXI 5.5) name it exactly as the other and re-create the roles exactly as the other?
By flaky, it was restored and has not worked right since. I had a host failure and now the windows time service will not restart. I just want to essentially start from scratch, but would like a road map of sorts.
Or would it be better do take this opportunity to add my first 2012 DC? What issues might I have there?
Thanks in advance.
By flaky, it was restored and has not worked right since. I had a host failure and now the windows time service will not restart. I just want to essentially start from scratch, but would like a road map of sorts.
Or would it be better do take this opportunity to add my first 2012 DC? What issues might I have there?
Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I am guessing you have exchange 2010. There will be no problems.
Please note : You need to add the 2012 DC before removing the secondary 2008 DC. This is just for redundancy purposes. I would also check that the 2012 DC is fully updated before moving the roles to it by using repadmin /syncall command.
Regards
Please note : You need to add the 2012 DC before removing the secondary 2008 DC. This is just for redundancy purposes. I would also check that the 2012 DC is fully updated before moving the roles to it by using repadmin /syncall command.
Regards
Adding a 2012 DC shouldn't cause any issues with Exhange its when you raise the functional level you need to be careful, eg if you are running Exchange 2003 this will not run under 2012 FFL
I had an issue a while back upgrading the functional level where exchange lost its Kerberos sync it was just a case of running a command to refresh it - I will try and dig out the article
By the sounds of your question though it doesn't look like this will affect you :)
I had an issue a while back upgrading the functional level where exchange lost its Kerberos sync it was just a case of running a command to refresh it - I will try and dig out the article
By the sounds of your question though it doesn't look like this will affect you :)
KDC issues I mentioned were 2003-2008 so disregard that :)
ASKER
Everything we have is 2008 level and Exchange is at 2010, so based on what I am reading, I should have no problems. Leroy, when you say fully updated, I assume you mean with patches etc. I would have it fully updated prior to adding the roles of DC, etc.
I believe he meant to check the AD replication was up to date - repadmin /showrepl on the new DC should show this before any FSMO roles are moved
Although I would also say yes to fully patching the server.
Although I would also say yes to fully patching the server.
Yes i meant AD is updated but I also agree on a fully patched server.
ASKER
Cool beans, I would rather be sure of something and ask the seemingly obvious questions rather than leave anything to chance. I think I will make preparations and go the 2012 Route... gonna have to do it at some point, might as well be now.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
ASKER