During synchronization of computer objects from the source domain to the target domain, the tool successfully creates the computer object (e.g., Contoso-WS01) in the default Computers container on the target.
Later, the object is moved in the source domain to a sub-OU such as:OU=Quarantined,OU=ClientComputers,DC=contoso,DC=local.
During the next sync, the object’s CN is unexpectedly modified on the target to include part of the source OU path, resulting in a name like:CN=Contoso-WS01,OU=Quarantined.
The sync tool calculates the TargetDN using the source object’s full distinguishedName (DN) to preserve the source OU hierarchy on the target.
When the target is configured to use the default CN=Computers container (a non-hierarchical container), the tool cannot replicate the source OU structure. To reconcile this, it incorporates part of the source OU path (e.g., OU=Quarantined) into the object's CN, which leads to an incorrect and misleading object name.
This CN modification is a direct result of the object's move within the source domain to a sub-OU. The tool attempts to maintain the source hierarchy even when the target structure does not support it.
To avoid unintended CN modification during synchronization:
Do not use the default CN=Computers container as the target OU when syncing from a structured source OU hierarchy.
Ensure that the target domain includes a matching OU structure, including sub-OUs like Quarantined, to allow accurate OU mapping.
If a flat OU structure is required, set a target OU to another staging OU.
