I am not for certain if everyone is aware of this, so thought I would pass it on here. I discovered it when troubleshooting some collection updates for our OSD process that were time sensitive. The process makes sense, although it is easy to overlook the cost on the back end.
When a limiting collection performs a full update, then all collections with that collection as its limiting collection are updated as well. Depending on how many collections are using it (consider an All Servers or an All Workstations limiting collection) and the size of your environment, that can be pretty costly. I noticed in the colleval.log that when our All Workstations limiting collection does a full update - either on schedule or when someone clicks the Update Membership button - it starts a chain reaction of roughly an hour of down-level full evaluations of collections (your mileage may vary). If you have such a collection, then your best bet is to configure it to use incremental updates, and set its full update schedule to happen off hours. Don't make the same mistake I made of scheduling it to do a full update every four hours! Duncan Russell The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
