RU5 allows you to designate a GUP on a different subnet in the same LiveUpdate policy, which would allow clients on one subnet to use a GUP on a completely different subnet. (not possible in previous versions of SEP 11)

Is that really what you want to do?  Or do you want to define a seperate GUP for each subnet, and have machines on each subnet use their local GUP?  If this is what you want, you would need to create a new location and LiveUpdate policy for each subnet, and assign the appropriate LU policy to each location. (2 locations, 2 LU polices)

Hope this helps...

If you are using the single GUP option in RU5 or the GUP in the earlier version,the GUP functionality will work with respect o the group which it is located.This is irrespective of the subnets which clients present.(i.e,The GUP and the clients should be present in same group.Subnet will not come to picture at all.) .

If you are using Multiple GUP options in RU5,it is fully depend on the subnet which the clients present.It is not group dependent.i.e,Client will receive updates only from a GUP which is present in it's on subnet only until and unless a PC which not present in that subnet specified in the liveupdate policy (specify the host name or IP address of a Group Update provider on a different subnet to be used ,if Group Update providers in the same subnet is not available option.) .Also assure that you are assigning same policy for both the groups--for the group which client present and for the group which GUP is present.

I want to have a GUP for each subnet and have workstation use their local GUP.  the Multiple GUP policy has the host names to use as GUP's.

My question though is, can those GUP and clients all be in the same client group?  djfurther is telling me no, and Rafeeq is telling me yes.

if you can create multiple GUPs in single policy, well that policy need to be appplied to a group, if you can do first, second is also true.