Share via

Failing to Transfer FSMO Roles From 2012 to 2016 After AD Upgrade

Question

Saturday, August 31, 2019 8:31 PM

I have VMs running Windows Server 2012 and 2016. The 2012 server is the domain controller with all roles. 

I successfully installed Active Directory services onto the 2016 server and promoted it to a domain controller following this guide.

When I get to the last steps of Migrating FSMO Roles, I try to do it in powershell, (ISE and non-ISE, Run as Admin, logged in as domain admin) and every time, it gives me the error:

PS C:\Windows\system32> Move-ADDirectoryServerOperationMasterRole -Identity servername -OperationMasterRole SchemaMaster, DomainNamingMaster, PDCEmulator, RIDMaster, InfrastructureMaster
Move-ADDirectoryServerOperationMasterRole : Could not find attribute: 'dNSHostName' on object: 
'CN=servername,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Domain,DC=local'.
At line:1 char:1
+ Move-ADDirectoryServerOperationMasterRole -Identity PPG-7 -OperationM ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (servername:ADDirectoryServer) [Move-ADDirector...ationMast 
   erRole], ADException
    + FullyQualifiedErrorId : ActiveDirectoryServer:0,Microsoft.ActiveDirectory.Management.Command 
   s.MoveADDirectoryServerOperationMasterRole

The guide recommended that I set the primary DNS on the target server to be its own IP, with the old DC as secondary. I did this and got the error so I tried swapping them and also trying with 8.8.8.8 and got the same error each time. I went into the target servers network settings and enabled IPv6 as well but it produced the same error. I’ve tried fresh starts on both servers with no luck. I haven’t been able to find a tremendous amount of info on this particular error at all, and almost nothing for this configuration. If anyone has some ideas for what to try next, that would be greatly appreciated, thanks!

All replies (4)

Saturday, August 31, 2019 8:33 PM

Please run;

  • Dcdiag /v /c /d /e /s:%computername% >c:\dcdiag.log

  • repadmin /showrepl >C:\repl.txt

  • ipconfig /all > C:\dc1.txt

  • ipconfig /all > C:\dc2.txt

    then put unzipped text files up on OneDrive and share a link.

 

 

Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management

Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

Friday, September 6, 2019 1:06 AM

Hi,

 

Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

 

Best Regards,

Vicky

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Tuesday, September 24, 2019 1:32 AM

Hi,

 

Just want to confirm the current situations.

 

Please feel free to let us know if you need further assistance.

 

Best Regards,

Vicky

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Wednesday, July 22, 2020 12:50 PM

I know it's a year later, so you probably fixed this somehow, but I kept getting this error over and over again. 

Like you, I thought it was a DNS issue and spent ages messing with DNS server settings.

When I changed -Identity servername to -Identity SERVERNAME (in capitals) in the command it worked!

Don't ask me why, I know it shouldn't make a difference, but it solved my problem.

Just leaving this here for future reference.

  • Last updated on