Greetings all.
For those who have moved to 12.1 RU5, and who also use Explicit GUP policies, please keep a look out for what we believe is a bug in the RU5 SEPM.
We're still investigating, but after a year of harmony in this space, across multiple customers, ever since we've upgraded the SEPM to RU5, the Explicit GUP policies are randomly going haywire on the SEP Agents' end, and there is no fix that we can tell. We reboot the system, or cycle the SEP Agent services which seems to temporarily fix it, but very soon after it starts all over again. Just ongoing lines of "Using Group Update Provider type: Mapped Group Update Providers" and it does nothing, it stops updating.
Note that we have made NO changes to our GUP policies or Location logic that have worked perforectly find for all releases of SEP 12.1. It's remained the same since RU2, RU4, and RU4MP1. Only the move to RU5 has created this problem.
Our SEP Agents for all affected customers still contain a mix of RU2, RU4, and RU4MP1. We're trying to determine if all 3 SEP Agent versions are affected. RU2 definitely is.
We've yet to deploy any RU5 Agents in PROD, but in the desperate hope that Symantec may have broken something that affects older agents, we are going to trial a few RU5 Agents to see if it too replicates this issue.
Cheers.