Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 96
  • Last Modified:

SBS 2008 Standard - move FSMO rules to Windows 2012R2

Hello,

I am in the final phases of migrating an SBS 2008 Standard server to Windows 2012R2.

Exchange has been moved to a separate Windows 2012 R2 with Exchange 2013 (soon to be moved to another Exchange 2016).

I need to move FSMO roles now to the Windows 2012R2 server so I can disjoin SBS2008 from the domain and shut it down.

Just to double check, can you furnish the proper steps to migrate FSMO rules?  I just want to make sure I do not miss anything.

Thanks in advance.

Regards,
Real-Timer
0
realtimer
Asked:
realtimer
2 Solutions
 
Phil DavidsonCommented:
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
It's relatively simple - here's the proceedure I'd recommend:
1. Run DCDIAG /C /E /V on all DCs (including SBS) and REPADMIN /SHOWREPL to ensure everything is working properly.
2. Turn OFF the SBS server for a few days - confirm that everything works. Then, next week:
3. Power Up the SBS Server and transfer the FSMO roles - you can use PowerShell, NTDSUtil, or the GUI tools (I prefer NTDSUtil myself and because I have better things to remember exact details of, I usually use Dan Petri's instructions here: https://www.petri.com/transferring_fsmo_roles
4. once transferred, run NetDOM /query FSMO from a command prompt and make sure they are correct.
5. Uninstall Exchange from the SBS server.
6. Demote the SBS Server using DCPROMO
7. Remove from the network entirely.
0
 
realtimerAuthor Commented:
Thank you very much.  Have not implemented the solution yet, but will do so very soon.

Regards,
Real-Timer
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now