Issue 1: Domain join
You have a new computer, and you want to join it to a domain of the forest. The same computer host name is already used in another domain. In this situation, the domain join operation reports success. After you click OK, you will see the following dialog box. The erased strings are the old and the new primary suffix of the computer:
The error message resembles the following:
While processing a change to the DNS Host Name for an object, the Service Principal Name values could not be kept in sync.
After restart, the computer will report itself as a domain member, but interactive logon with a domain account will fail, and you will receive the following error message:
The security database on the server does not have a computer account for this workstation trust relationship.
You will also receive the following error message in the Netsetup.log file:
0: 000021C7: DSID-03200BA6, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 90303 (servicePrincipalName)
NetpModifyComputerObjectInDs: ldap_modify_s failed: 0x13 0x57
Issue 2: Intra-forest migration
If you perform an intra-forest user migration that has service principal name (SPN) or user principal name (UPN) defined or intra-forest computer migration, the migration fails because the account still exists in the global catalog as the object is introduced in the target domain that has these attributes populated. If the object was saved in the new domain, a duplicate SPN would be created.
Note The tools to drive the migrations might be Active Directory Migration Tool (ADMT), external migration tools or the Move-ADObject cmdlet by using Active Directory PowerShell.
Issue 3: SPN conflicts with SPN on restored object
You had an account with SPNs in use on an account that is deleted now. You add an SPN to the object that used to have another user or computer account in the forest. When you now try to restore the deleted account, the action fails because of the duplicate SPN.
Note In all three issues, event ID 2974 that resembles the following is logged in the Directory Service log of the domain controller: The error number 8647 translates to symbolic name is ERROR_DS_SPN_VALUE_NOT_UNIQUE_IN_FOREST. For deplicate UPN, the error would be number 8648 and ERROR_DS_UPN_VALUE_NOT_UNIQUE_IN_FOREST.
In the issues that were described in this article, it prevents administrative tasks where the effect is not obvious.
Such a preparation change might not be possible in all cases. Therefore, Microsoft has developed an update that enables controlling the domain controller behavior. This update applies to Windows Server 2012 R2-based domain controllers. You can also install this update on member servers that are candidate for promotion to a domain controller in the future.
With this update, Microsoft provides a forest level switch to turn off or turn on uniqueness check through the dSHeuristics attribute.
The following are the supported dSHeuristics values:
- dSHeuristic = 1: AD DS allows adding duplicate user principal names (UPNs)
- dSHeuristic = 2: AD DS allows adding duplicate service principal names (SPNs)
- dSHeuristic = 3: AD DS allows adding duplicate SPNs and UPNs
- dSHeuristic = Any other value: AD DS enforces uniqueness check for both SPNs and UPNs
- For disabling UPN uniqueness check, set the 21st character of dSHeuristics to "1" (000000000100000000021)
- For disabling SPN uniqueness check, set the 21st character of dSHeuristics to "2" (000000000100000000022)
- For disabling UPN and SPN uniqueness checks, set the 21st character of dSHeuristics to "3" (000000000100000000023)
We recommend that you set the value back to 0 when you know problematic changes are not occurring any longer. This can be the case especially for intra-forest migrations.
Hotfix informationImportant If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesTo apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1 or Windows Server 2012 R2.
Registry informationTo use the hotfix in this package, you do not have to make any changes to the registry.
Restart requirementYou may have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
You may also see Event ID 11 — Service Principal Name Configuration for more information.
Ask Premiere Field Engineer (PFE) Platforms blog: Third-party Active Directory Migration Tools and KB 3070083.