Never sat down and checked them ... I would guess some of
them are PAS enabled simply due to the fact that they're used on both common
domain NC objects and those in the config. (and possibly the
schema).
Maybe it took so much extra disk space to maintain the
PAS=1 they decided against it :-) or "since they're already everywhere,
why bother" may have crossed their minds.
Seriously, the primary reason has to be it serves no
purpose since the GC maintains only those PAS enabled attributes populated on
objects within the domain NC. Sure it's got a copy of the config. and
schema but not because of its GC'ness.
--
Dean Wells
MSEtechnology
( Tel: +1 (954)
501-4307
* Email: dwells@msetechnology.com
http://msetechnology.com
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joe
Sent: Saturday, July 10, 2004 6:44 PM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] Thought of the Day
How come all attributes of all objects that live entirely
in the configuration NC and Schema NC aren't PAS
enabled?
