| Previous | Next |
| ERROR_DS_NO_PKT_PRIVACY_ON_CONNECTION | ERROR_DS_DESTINATION_DOMAIN_NOT_IN_FOREST |
ERROR_DS_SOURCE_DOMAIN_IN_FOREST
This migration path requires separate source and destination forests
SID-history insertion through DsAddSidHistory is designed for inter-forest migration. The API rejects a source domain in the same forest because duplicate primary or historical SIDs must not be introduced within one forest security boundary. Moving an object between domains of one forest is a different operation and uses coordinated cross-domain move semantics.
Identify the forest root and forest SID namespace for both domains. For an in-forest relocation, use a supported cross-domain move against the source and target RID masters instead of SID-history migration. For an inter-forest migration, verify that the source really belongs to a distinct forest and that trust, auditing, credentials, and source-PDC prerequisites are met before retrying.
What to inspect
- Resolve both domains to their forest roots.
- Choose Move-ADObject for an in-forest domain move.
- Reserve DsAddSidHistory for the documented inter-forest case.
References
- Microsoft: DsAddSidHistory forest requirements
- Microsoft: in-forest cross-domain moves
- MS-ADTS: cross-domain move control
Looking for a different code? Search another status or error code.