SBS2011 Migration Exchange 2010 to 2013, and AD

We have an SBS2011 single Domain AD and we created a new AD Server WIn2012R2 and added it as a second Domain Controller, then we migrated Exchange 2010 to Exchange 2013 SP1 (Win2012 R2) so it's been a couple of months and I shut down all of the Exchange 2010 Services on the SBS2011 Server and it's been about a month with no issues, the Exchange migration was Co-Existence, so what would be the next graceful process to remove Exchange 2010 from the Domain/SBS2011 Server, Should we be able to just un-install it off the SBS Server and will that remove it correctly out of the Active Directory?, also to Demote the SBS Server once we get the Exchange removed move the FSMO Roles over to the new AD Server and then perform DCPromo and remove the Domain Services?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

FOXActive Directory/Exchange EngineerCommented:
AD- move all the fsmo roles to the 2012 server then afterwards from a command prompt run this command -- netdom query fsmo  --  to verify all the roles all homed on the new server.  You can then run a dc promo to remove it as a domain controller.    If it gives you a problem with regular dc promo , do a start run     dcpromo /forceremoval

Exchange- Once you have verified that all you services are now on the Exchange 2013 servers , you must uninstall exchange 2010 which will also remove it from Active Directory.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dtssupportAuthor Commented:
Should I uninstall Exchange 2010 first or move the FSMO roles and demote SBS?
Cris HannaSr IT Support EngineerCommented:
Yes   uninstall Exchange first
Introduction to Web Design

Develop a strong foundation and understanding of web design by learning HTML, CSS, and additional tools to help you develop your own website.

dtssupportAuthor Commented:
once I remove Exchange then move the FSMO rules over then verify, then how long should I wait to demote the SBS 2011 Server? Do I need to be concerned about that it was an SBS Active Directory and now it won't be?
and since I had the Exchange 2010 Services off, should I turn them back on for the Un-install?
FOXActive Directory/Exchange EngineerCommented:
I'm assuming when you brought the other domain controller in to the environment you updated the schema and so forth.  It should have done it automatically during the install.  On the new domain controller, on your nic, in DNS ip make the preferred  ip point to itself and add alternate ip of sbs domain controller as the secondary ip for now.  On the SBS server, on the nic, make sure the secondary ip in your dns ip entry has the ip of the new domain controller.  If your mail is flowing correctly on the new server feel free to uninstall exchange.  The graceful uninstall will remove it from active directory.  I don't believe you need to have the services on for the uninstall, the uninstall will error if you do need them on, if so you can just fire them up.  After the exchange uninstall move the roles over to the new domain controller if you haven't done so already and VERIFY THEY ARE ALL THERE ON THE NEW DOMAIN CONTROLLER.  After verification you can now demote that domain controller.  After demotion you will need to do a little cleanup.  Go in to the DNS of the new domain controller, in forward lookups delete any entries of the old domain controller, do the same if you have any entries in reverse lookup as well.  On the nic of the new domain controller remove the alternate ip in dns entries of the old domain controller if you did in fact put in there.  In active directory users and computers>Domain Controllers, after the demotion, the OLD domain controller should have purged itself out, if not delete .
dtssupportAuthor Commented:
thank you
FOXActive Directory/Exchange EngineerCommented:
Being that you are moving all the fsmo roles to the new domain controller you can run a simple powershell command that will handle it for you.
1. On the ]NEW domain controller right click the powershell icon and run as administrator
2. type   import-module ActiveDirectory  then press enter
3.  enter this command
 Move-ADDirectoryServerOperationMasterRole -Identity newdomaincontrollername -OperationMasterRole 0,1,2,3,4

*enter the name of your new domain controller where I have newdomaincontrollername
dtssupportAuthor Commented:
thank you, what is the time line of demote the SBS server once you do this?
FOXActive Directory/Exchange EngineerCommented:
On another note- Were all your workstations pointing to the DNS of your original domain controller? Was this being handled automatically in dhcp with a helper file?  If so you will need to add the ip of the new domain controller to the helper file so your workstations can now pick up this server.
FOXActive Directory/Exchange EngineerCommented:
Before you demote it I want you to open a command prompt on the new domain controller.

type repadmin /replsummary

Make sure there are no fails...this will verify replication was good before you demote it
Cris HannaSr IT Support EngineerCommented:
Once you move the FSMO roles it's 7 days
dtssupportAuthor Commented:
No Fails
FOXActive Directory/Exchange EngineerCommented:
What is 7 days?  if replication is good, the fsmo roles have been transferred, everything in the dns of the new server is correct, you can demote the sbs server whenever you want.
Cris HannaSr IT Support EngineerCommented:
With SBS servers, once you move the FSMO have 7 days to demote the SBS Server and shut it down or it starts rebooting hourly
FOXActive Directory/Exchange EngineerCommented:
Oh ok, I see what you are saying now Cris.  If you don't demote and shut it down within 7 days it starts going haywire.
Cris HannaSr IT Support EngineerCommented:
correct.   There a patch that can be applied to extend that to 21 days, but this seems far enough a long that the patch would not be required
dtssupportAuthor Commented:
thanks Chris and FoxLuv, I am looking to do this tomorrow, will advise how it goes, thx Mike
FOXActive Directory/Exchange EngineerCommented:
If you have a separate network engineer working with you make sure he is in line with your objectives in case anything needs to be done on his/her end.
dtssupportAuthor Commented:
thx just one person,  small business, 1 Domain Forest, thx
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.