Originally Posted By: Roger
In this case, it's not a network problem. It's SCCM attempting to be scalable by having the client only pull fresh policy on a schedule. In this case, you just have to wait. Even if you manually trigger a refresh, it still doesn't do it immediately.

That is, in fact, exactly what I meant, and exactly what I hate.

It's the same for AD, DNS, Exchange, et al. As an admin with more work to do than I really have time for, "wait" is a despicable answer.
_________________________
Bitt Faulk