H
harsh_bapat
Hi,
Microsoft describes a mechanism "Polling for Changes Using USNChanged"
for AD.
http://msdn.microsoft.com/library/d...d/ad/polling_for_changes_using_usnchanged.asp
I am wondering if this mechanism holds true for a Global Catalog
scenario. I am new to the Global Catalog concept. From what I
understand, GCs host a copy of every partition in the forest (a full
copy of their own domain's domain partition, a full copy of the schema
partition, a full copy of the configuration partition, and a read-only
copy of every other domain's domain partition with only a subset of
attributes for each object), then an object addition/modification to
any domain will cause replication to all DCs in that domain, as well as
to all GCs, whether or not they are DCs for that domain. Attributes
uSNChanged and uSNCreated are available in GC as read-only attributes.
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adschema/adschema/a_usnchanged.asp).
Definition of 'uSNChanged' says - USN value assigned by the *local
directory* for the latest change, including creation. So at local AD
level 'uSNChanged' value is unique for each change. I am wondering how
this is taken care at GC level as it is maintainaing 'uSNChanged' from
various *local* ADs? i.e. How changes are tracked at Global Catalog
level? Any ideas?
~Harsh
Microsoft describes a mechanism "Polling for Changes Using USNChanged"
for AD.
http://msdn.microsoft.com/library/d...d/ad/polling_for_changes_using_usnchanged.asp
I am wondering if this mechanism holds true for a Global Catalog
scenario. I am new to the Global Catalog concept. From what I
understand, GCs host a copy of every partition in the forest (a full
copy of their own domain's domain partition, a full copy of the schema
partition, a full copy of the configuration partition, and a read-only
copy of every other domain's domain partition with only a subset of
attributes for each object), then an object addition/modification to
any domain will cause replication to all DCs in that domain, as well as
to all GCs, whether or not they are DCs for that domain. Attributes
uSNChanged and uSNCreated are available in GC as read-only attributes.
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adschema/adschema/a_usnchanged.asp).
Definition of 'uSNChanged' says - USN value assigned by the *local
directory* for the latest change, including creation. So at local AD
level 'uSNChanged' value is unique for each change. I am wondering how
this is taken care at GC level as it is maintainaing 'uSNChanged' from
various *local* ADs? i.e. How changes are tracked at Global Catalog
level? Any ideas?
~Harsh