This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Error 0x0000214d SPN name values could not be kept in sync

Hello all-

My customer has a bunch of Windows 2008 (not R2) application servers. I've successfully migrated thousands of workstations and dozens of servers (all 2008 R2 or greater) without issue. This is a child to parent (intra-forest) domain consolidation.

When I try to migrate a 2008 system using the RUM, the move fails. The RUM's error message is:

"Error 0x214d. While processing a change to the DNS Host Name for an object, the Service Principal Name values could not be kept in sync."

Inspecting the netsetup.log (attached) I see the following:

" NetpJoinDomain: status of setting DnsHostName and SPN: 0x57"

Due to a very tight time window (24/7 casino) I had to manually move it to the parent domain and it was successful. I then removed the old computer object from the source child domain and once SPNs regenerated, all was good.

The ONLY commonality I can see is 2008 vs 2008 R2. 2008 R2 systems migrate using the RUM without issue. Regular 2008 do not. The Forest Functional Level is set to 2003 and Domain Functional Level is 2012 R2. 

Anyone seen anything like this? I have not moved any regular 2008 in many years but I have never seen this error.

As always, thanks in advance.

Eric

NetSetup.LOG

Parents
  • Hi Chris-
    Yes, an intra-forest move.
    I've read that article before. Essentially I have two choices: move and not select a destination and all systems will move to the default Computers OU, or copy the computer objects in advance using QMMAD, filter SPN and the objects will be put in the target OU of my choosing and the RUM will enable the target system and AD will rebuild the SPNs.
    This error only occurs on 2008 Standard, not R2 servers. All 2008 R2, 2012, 2012R2 servers move with no issue.
    Eric
Reply
  • Hi Chris-
    Yes, an intra-forest move.
    I've read that article before. Essentially I have two choices: move and not select a destination and all systems will move to the default Computers OU, or copy the computer objects in advance using QMMAD, filter SPN and the objects will be put in the target OU of my choosing and the RUM will enable the target system and AD will rebuild the SPNs.
    This error only occurs on 2008 Standard, not R2 servers. All 2008 R2, 2012, 2012R2 servers move with no issue.
    Eric
Children
No Data