Additional Information
The number of operational GUIDs that appear in the CN=Operations,CN=ForestUpdates container and in the CN=Operations,CN=DomainUpdates container depends on the upgrade path of the forest and its domains. Various operations that are performed by beta versions of Adprep.exe have been removed in the original released version of Windows Server 2003. The released version of Adprep.exe does not remove GUIDs that were added to the CN=Operations,CN=ForestUpdates container and to the CN=Operations,DomainUpdates container by beta versions of Adprep.exe. Therefore, a forest or domain that was prepared with Beta 3, Release Candidate (RC) 1 or with early RC2 versions of Adprep.exe will contain more operational GUIDs than one that was prepared with a released version.
Finally, objects under the CN=Operations,CN=ForestUpdates container and the CN=Operations,CN=DomainUpdates container are not exclusively created by Adprep.exe. Adprep.exe will add the operational GUIDs that represent the actions that Adprep.exe can perform. Similarly, the operating system installation process or the installation scripts may create additional operational GUIDs that are essentially registry keys that replicate between the correct scope of domain controllers.
Ordinarily there are 50 objects that are created by the
adprep /domainprep command under CN=Operations,CN=DomainUpdates,CN=System,DC=
X and 36 objects that are created by the
adprep /forestprep command under CN=Operations,CN=ForestUpdates,CN=Configuration,DC=
X. However, when a Windows 2000 Server Service Pack 3 (SP3) domain controller is directly upgraded with Windows Server build 3777 or a later version of Adprep.exe, an additional GUID, CN=6E157EDF-4E72-4052-A82A-EC3F91021A22, is created in the CN=ForestUpdates container. This container is not removed by later versions of Adprep.exe. Similarly, domains that were updated by early versions of Adprep.exe may also contain a CN=Windows2002Update container that is also not removed by later versions of Adprep.exe. There are known differences in NTSD/default security descriptor definitions between a forest that was prepared with the original released version of Windows Server 2003 and a forest that used a different upgrade path. The divergence in the number of operational GUID objects is by design.
Build 3777 (and later) versions of the Windows Server 2003
adprep /domainprep command creates two additional objects under CN=Operations,CN=DomainUpdates,CN=System,DC=
X that are defined in the DomainUpdates section of Schema.ini.
[DomainUpdates]
[7ffef925-405b-440a-8d58-35e8cd6e98c3]
nTSecurityDescriptor=O:DAG:DAD:(A;;RPLCLORC;;;AU)(A;;RPWPCRLCLOCCDCRCWDWOSW;;;DA)(A;;RPWPCRLCLOCCDCRCWDWOSDDTSW;;;SY)
objectClass= Container
objectCategory= Container
[8ddf6913-1c7b-4c59-a5af-b9ca3b3d2c4c]
nTSecurityDescriptor=O:DAG:DAD:(A;;RPLCLORC;;;AU)(A;;RPWPCRLCLOCCDCRCWDWOSW;;;DA)(A;;RPWPCRLCLOCCDCRCWDWOSDDTSW;;;SY)
objectClass= Container
objectCategory= Container
Important New IPSEC filters that are created between the execution of
adprep /forestprep and
adprep /domainprep will not apply to Windows 2000, Windows XP and Windows Server 2003 domain computers until
adprep /domainprep has been executed in those domains where the IPSEC filter was created. IPSEC filters that are defined before the execution of
adrprep /forestprep and after the execution of
adprep /domainprep in each domain will continue to apply normally. As a best practice, Microsoft suggests that administrators promptly run
adprep /domainprep on the infrastructure master domain controller for each domain in the forest following the execution and inbound replication of
adprep /forestprep changes.