Multiple Gups
Created: 22 Mar 2011 | 5 comments
Hi,
We have over 10,000 subnets. How do I make sure that each subnet has at least one or two gups? Server and clients are also on different subnets. There must be a clever way of doing this without deploying registry key and making everything a gup? Need your help pelase, thanks in advance!
Discussion Filed Under:
Comments
Go to the liveupdate
Go to the liveupdate policy-GUP-Multiple GUP, and type the ip address of atleast opne computer in each subnet ( GUP)..use OR expression...
-VKalani
Can you deploy a registry key
Can you deploy a registry key to each designated GUP, and create one policy to set the gup based on querying that key?
Multiplte GUP assignment
When you say you have 10,000 subnets, are they also assigned to different groups? If not, you can create a LiveUpdate policy with multiple GUPs.
Select clients to be made into a GUP. List down their hostname/IP. Create a LiveUpdate policy with GUP enabled and enter those hosts. Assign the policy to the group that will be using them. I recommend to move those clients to a different group so you can further change their policy to suit your needs.
If there are 10k subnets and they don't have network sharing between each other, then, the specific IP for that GUP will only be the one to be the source of their updates. Otherwise, they'll also be looking into other subnets as well.
What I did was create 700+ GUP policies for the 700+ groups. Took me a while to finish and I wouldn't recommend it.
“Your most unhappy customers are your greatest source of learning.”
Hi, why did you do it this
Hi, why did you do it this way and what would you reccomend? The reason I ask is that I'm finding myslef going down a similar path that I would really prefer not to. I have tried multiple GUP lists and have not seen clients updating properly yet.
Thank you,
Chris
Sit back, take a deep breath...
I did it this way since that's the best option I saw in our clients network. GUP assignment is basically telling the clients to look to these designated PCs for their updates. I chose to assign them for each group to prevent them from looking into other remote locations and consuming bandwidth. Which means that policy inheritance is disabled to these 700+ groups. No other method that I know of for that. Sorry.
It took a while before the changes take effect. The gups would download complete and delta updates for their clients. And clients will ask for updates from the server after 4 or 5 hours of trying from the GUP with Heartbeat interval set at 2.5 hrs so that it will check back to the GUP at least 2 times before going to the server.
Taking the 10k groups as an example. It would be time consuming to create and assign LU policies for each group which also includes disabling policy inheritance. But assigning 10k clients for these groups would mean that each PC would be checking on thousands of PCs for their updates.
If possible, you may want to further divide these groups into manageable subgroups and assigning a few GUPs for them. That way you can still have group inheritance for each sub-group. I'm assuming that they're spread over a wide range and uses VPN over WAN. Use that as a start for grouping the groups. But if there's still a few PCs laying around, maybe use them as LiveUpdate servers for each locale. Our goal here is to spread out the sources of definition updates so that there won't be bottlenecks in the SEP management server.
“Your most unhappy customers are your greatest source of learning.”
Would you like to reply?
Login or Register to post your comment.