Академический Документы
Профессиональный Документы
Культура Документы
com/canitpro/2017/05/24/step-by-step-migrating-active-
directory-fsmo-roles-from-windows-server-2012-r2-to-2016/
With Windows server 2016 was released for public (GA), many businesses are working on
migrating their services to the new offering. This post will walk you through the steps needed to
migrate Active Directory FSMO roles running on Windows Server 2012 R2 to Windows Server
2016 Active Directory. The same steps are valid for migrating from Windows Server 2012,
Windows Server 2008 R2 and Windows Server 2008.
In this setup, the Windows Server 2012 R2 domain controller is setup as a PDC. The Windows
Server 2016 machine has already been added to the existing domain.
Current domain and forest functional level of the domain is windows server 2012 R2.
So, let's start with the migrate process.
2. Check the IP address details and put the local host IP address as the primary DNS and another AD
server as secondary DNS. This is because after AD install, server itself will act as DNS server
3. Run servermanager.exe form PowerShell to open server manager (there is many ways to open it)Â
I assume by now you have idea what is FSMO roles. If not search my blog and you will find article
explaining those roles.Â
There are 2 ways to move the FSMO roles from one AD server to another. One is using GUI and other
one is using command line. I had already written articles about GUI method before so I am going to use
PowerShell this time to move FSMO roles. If you like to use GUI mode search my blog and you will find
articles on it.Â
2) Open up the Powershell as administrator. Then type netdom query fsmo. This will list down the FSMO
roles and its current owner.Â
3) In my demo, the windows server 2012 R2 DC server holds all 5 fsmo roles. Now to move fsmo roles
over, type Move-ADDirectoryServerOperationMasterRole -Identity REBELTEST-PDC01 -
OperationMasterRole SchemaMaster, DomainNamingMaster, PDCEmulator, RIDMaster,
InfrastructureMaster and press enter
In here REBELTEST-PDC01 is the windows server 2016 DC. If FSMO roles are placed on different servers,
you can migrate each and every FSMO roles to different servers.Â
4) Once its completed, type netdom query fsmo again and you can see now its windows server 2016 DC
is the new FSMO roles owner.Â
Upgrade the forest and domain functional levels to windows server 2016
Now we have the windows server 2012 R2 domain controllers demoted, next step is to upgrade domain
and forest functional levels.Â
1) Log in to windows server 2016 DC as enterprise administratorÂ
Tags Active Directory Active Directory Forest AD 2016 AD DS 2016 FSMO How to How-To MVP server
2016 Step-By-Step Windows Server 2016 Windows Server 2016 and tagged active direcotry