Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

SBS 2008 Standard - move FSMO rules to Windows 2012R2

Posted on 2016-08-02
3
Medium Priority
?
90 Views
Last Modified: 2016-08-15
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
Comment
Question by:realtimer
3 Comments
 
LVL 7

Assisted Solution

by:Phil Davidson
Phil Davidson earned 1000 total points
ID: 41739923
0
 
LVL 96

Accepted Solution

by:
Lee W, MVP earned 1000 total points
ID: 41739953
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
 

Author Closing Comment

by:realtimer
ID: 41756556
Thank you very much.  Have not implemented the solution yet, but will do so very soon.

Regards,
Real-Timer
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Windows Server 2003 introduced persistent Volume Shadow Copies and made 2003 a must-do upgrade.  Since then, it's been a must-implement feature for all servers doing any kind of file sharing.
How to deal with a specific error when using the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service, for an existing user in an on-premises Active Directory.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…
Suggested Courses

886 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question