Intel,Altiris Group

We have Ru5 installed and now we have the new GUP settings withing our Live Update policies.  We have about 24 remote sites that have issues with GUP since all our remote servers are on a different subnet then our clients.  With RU5 it was suppose to bring new features t hat would enable setting up GUP's like the way Locations are set up with Rules for where a client reports to.  However, I see a problem with what I am trying to do.  I would like to list all my GUP's on one policy like RU5 is suppose to do, however, we run into the problem that our GUP's are on a different subnet then our workstations.    As you can see below the new Group Update Provider list would be great if all our GUP's and clients where on the same subnet.  However, this feature seems void since the line at the bottom is where I can only put one GUP name if it is on a different subnet??????  Am I just looking at this wrong or am I correct?

https://www-secure.symantec.com/connect/articles/configuring-group-update-providers-symantec-endpoint-protection-110-ru5

https://www-secure.symantec.com/connect/articles/types-group-update-providers-ru5-release-symantec-endpoint-protection-110

You are correct, clients will first attempt to use a dynamic GUP in their subnet. If they cannot find one they will fall back to the 'outside of subnet' GUP, of which there can be only one.

On the plus side, the client does evaluate by (IP address + subnet mask) whether or not the GUPs available are on their subnet. So you could change your subnet mask to allow them to see the servers as being on their subnet.

You could have avoided having 24 policies and used "localhost" as the hostname. This allows you to have the same LU policy for all your GUPS.
For me this has worked well, so I don't think I'm even going to mess around with the settings in RU5.

(r a single LU policy, specifiying all the GUPs.

Have you got the localhost method working under RU5? I have tried configuring GUPs using this method, which worked very well before, and my RU5 system does not seem to like it.  The clients with the LU policy containing localhost as the GUP do not become GUPs any more.  Clients, GUP candidate and SEPM are all on RU5.

I have looked at the GUP list method but wanted to avoid the clients deciding which GUP to use, themselves - preferring to specify this explicitly through policy.

Any help appreciated.