There can also be inherent delays if using an SCCM environment with a CAS. App Portal will communicate with the CAS and update the collection membership rules there for the appropriate catalog item collection. The collection rules then have to replicate to each primary site where collection evaluation is run. After each primary site has evaluated the collection membership, that membership is replicated back to the CAS. The problem with policy evaluation is that we use the SCCM client notification channel (when that box is checked) to notify the client that it should check for new policies. If that client notification happens before the collection evaluation is completed (and policies updated accordingly), then the client won't get the new policy until the next standard client polling interval (normally an hour). Is that what you've been seeing, or is it something different?
Anything expressed here is my own view and not necessarily that of my employer, Flexera. If my reply answers a question you have raised, please click "ACCEPT AS SOLUTION".
