When the OU at the domain root level has the same name as a future child domain, you might encounter database problems.To illustrate this, consider a scenario where you delete an OU named "marketing" to create a child domain with the same name, e.g. marketing.contoso.com (leftmost label of the child domain FQDN name has the same name).The OU is deleted and during the tombstone lifetime of the OU you create a child domain that has the same name is created, deleted, and created again. In this scenario, a duplicate record name in the ESE database causes a phantom-phantom name collision when the child domain is re-created. This problem prevents the configuration container from replicating.Note a similar name conflict might also happen with other RDN name types under certain conditions, not restricted to DC and OU name types:951323 Error message when you add a group as a member of another group from a different domain in Windows Server 2003 Active Directory: "Directory Service is too busy"http://support.microsoft.com/default.aspx?scid=kb;EN-US;951323
Table of reserved words
Reserved words for namesWindows NT 4.0Windows 2000Windows Server 2003ANONYMOUSXXXAUTHENTICATED USERXXBATCHXXXBUILTINXXXCREATOR GROUPXXXCREATOR GROUP SERVERXXXCREATOR OWNERXXXCREATOR OWNER SERVERXXXDIALUPXXXDIGEST AUTHXINTERACTIVEXXXINTERNETXXLOCALXXXLOCAL SYSTEMXNETWORKXXXNETWORK SERVICEXNT AUTHORITYXXXNT DOMAINXXXNTLM AUTHXNULLXXXPROXYXXREMOTE INTERACTIVEXRESTRICTEDXXSCHANNEL AUTHXSELFXXSERVERXXSERVICEXXXSYSTEMXXXTERMINAL SERVERXXTHIS ORGANIZATIONXUSERSXWORLD
The OU is deleted and during the tombstone lifetime of the OU you create a child domain that has the same name is created, deleted, and created again. In this scenario, a duplicate record name in the ESE database causes a phantom-phantom name collision when the child domain is re-created. This problem prevents the configuration container from replicating
No comments:
Post a Comment