Reading Time: 3 minutes
Share:
Twitter
LinkedIn
Facebook
Reddit
Whatsapp
Follow by Email

Now Windows Server 2016 has been out for a few months I have decided to update my lab Domain to 2016 forest functional level. But first I need to migrate the FSMO (Flexible Single Master Operation) Roles to my new Windows Server 2016 Domain Controllers.

In this Step by Step Guide, I am going to try and explain how to move the FSMO Roles and share some practices I like to follow when doing so.

Prerequisites

At least one Domain Controller running Server 2016

Finding who has the FSMO Roles

This is the easy bit!

1. Open PowerShell with elevated credentials

2. Type

netdom query fsmo

3. Press Enter

Plan your FSMO Role Move

In most cases, you can keep all FSMO Roles on the same Domain Controller. I find that if I have two Domain Controllers in one site where all my users are based, and both Domain Controllers are Global Catalogues, then everything will work fine with all 5 FSMO Roles running on one DC.

When you have multiple sites where users are based. I always please the Primary Domain Controller FSMO Role on the Domain Controller that is going to be used most by the users. This may not be Best Practice, but it’s what I like to do.

One thing we must remember is if one of our Domain controllers does not host a Global Catalogue, then the Infrastructure Master FSMO Role Must be installed on it. If you have more than one Domain Controller without a Global Catalogue, then you can choose which server (out of the ones not hosting a Global Catalogue) to host your Infrastructure Master FSMO Role on.

Moving The FSMO Roles

In my Lab, I only have two domain controllers, one Windows Server 2012 r2 and one Windows Server 2016. So I will be moving all the FSMO Roles from my Windows Server 2012 r2 Domain Controller to my Windows Server 2016 Domain Controller.

1. On the Windows Server 2016 Domain Controller open PowerShell with elevated credentials

2. Type

Move-ADDirectoryServerOperationMasterRole -Identity PIXEL-DC03 -OperationMasterRole SchemaMaster, DomainNamingMaster, PDCEmulator, RIDMaster, InfrastructureMaster

3. Press Enter

4. Type Y per line or A for all.

To confirm that the Roles have been moved use the following command

Netdom query fsmo

You should see all FSMO Roles now site on PIXEL-DC03

Notes

You can always use the above command to move the roles to different servers. Just pick which server you want to move a role to and pick what role you want to move.

So, for example, you can move the Infrastructure Master Role to PIXEL-DC04 (if I had one) by using the following command

Hope this has helped someone, any feedback please leave a comment.

Share:
Twitter
LinkedIn
Facebook
Reddit
Whatsapp
Follow by Email

Pixel Robots.

I’m Richard Hooper aka Pixel Robots. I started this blog in 2016 for a couple reasons. The first reason was basically just a place for me to store my step by step guides, troubleshooting guides and just plain ideas about being a sysadmin. The second reason was to share what I have learned and found out with other people like me. Hopefully, you can find something useful on the site.

1 Comment

Transfer FSMO Roles · June 20, 2017 at 8:46 am

Thanks for the amazing article. My two cents about FSMO Roles and steps to transfer FSMO Roles.

http://www.itingredients.com/what-is-fsmo-roles-flexible-single-master-operations/

Leave a Reply

Your email address will not be published. Required fields are marked *

*

I agree