Why does it take 30 minutes for changes to Collections to be reflected in ConfigMgr 2012 R2?

I’ve got several nested Collections in my ConfigMgr 2012 R2 implementation. I’ve noticed that if I make a change to a Collection either through the Console or by PowerShell it can take up to 30 minutes for the changes to be completed.

The problem even happens if I make a change such as changing the description and don’t modify the Membership Rules.

You need a subscription to access the answer.

This content is restricted to subscribers

Login to leave your feedback!

Leave a Reply