Question about GUPs, GUP lists, and limiting GUPs
I have a question about GUPs on SEP 12.4. We have over 1000 machines including servers, laptops, workstations across our state. We have 27 districts made up of multiple counties. A single District Server supports all the counties within that district. Each county has its own subnet.
Initialy we set up our GUP list within LiveUpdate policy using IP addresses of our Remote District Servers. Thus, the only GUPs we had were the 27 District Servers. I had forgotten that clients ONLY talk to a GUP if it is in that client's subnet. Thus, the outlying counties in a district did not talk to the District Server\GUP. Any updates those clients needed came directly from our SEPM server. A single server.
We've had problems with tens of thousands of SEP sessions overloading our firewall at our main office where our SEPM server resides.
We chose to add an OS check to our GUP list, so that any machine with an OS of "XP" or "win7x64" could now become a GUP in addition to our District Servers. We now have nearly 800 GUPs. That's out of a total of just over 1000 machines.
1) Is there a way to limit the number of GUPs created?
2) When GUPs request updates, do they get the delta from SEPM, or do they also check the GUP list like clients do?