Joe makes a good point about PAS here. Changes to the partial attribute set are what generally force the reset status on GCs not the schema change itself. If you custom extensions have not been configured for inclusion in the GC, there should not be a full sync triggered.
Aric
_____________________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of joe
Sent: Thursday, January 29, 2004 10:23 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] schema updates
Test them all together. It should be fine. Then slam them into production all together. You don't want to force multiple syncs because of PAS changes.
joe
_____________________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of marcus
Sent: Friday, January 30, 2004 12:39 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] schema updates
Sorry if this has come up before (haven’t seen it hit the list).
We have some schema updates to do… but was curious whether stacking them up back to back was a very good idea since they all require full gc syncs. We’ve tested the extensions individually in the lab, and they all act fine… any comments on why you should or should not do this? J
