We recently spun up a third SEPM site, which will be used to migrate 2 separate sites we are currently managing. When replication was setup between the 3 sites, IPS signatures failed to update on our GUPs.
We have been updating IPS signatures manually with success. Adding the JDB file is allowing the GUPs to grab it and clients update successfully. We have a case open to work out whether replication may have broken the GUP's ability to pull the IPS sigs from SEPMs.
We have successfully used the JDB file for RU1 to update the GUPs, which are running MP2.
We are mid-upgrade from MP2 (14.0.2415.0200) to RU1 MP1 (14.0.3897.1101), and the GUPs failed to be upgraded before our workstation clients. Yesterday most of the GUPs were upgraded to RU1 MP1.
Today, we went to manually update the IPS signatures with the latest available, as is routine at this point, and only the non-upgraded GUPs pulled that latest IPS sig. The upgraded GUPs are still failing to update. I understand that this is a mess on the upgrade front, but it doesn't make sense that the RU1 MP1 GUPs aren't updating signatures, while the non updated GUP clients are. Clearly a compounded issue, but reaching out to see if there's something I might be missing.
**GUP install package for the upgrade kept all GUPs in their respective groups, with the same policies applied. No changes at all, except the client upgrade.
**All of our SEPMs were upgraded to RU1 MP1 prior to any client upgrades.