Endpoint Protection

 View Only
Expand all | Collapse all

How to use FQDN to active feature GUP on multiple server ?

  • 1.  How to use FQDN to active feature GUP on multiple server ?

    Posted Jan 20, 2011 11:05 AM

    hi

    Description Architecture simplified

    we have several sites ( 250 )

    Server SEPM MRU6A

    Workstation : MRU5

    Every site have a specific vlan for Server ( 10.1 ) and specific vlan for workstation  (10.2.100)

    Site A ---> 1000 clients  10 .2.X---> 1 server GUP  10.1

    Site B ---> 2000 clients ----> 1 server GUP

    .......

    I don't want to create 250 policies Liveupdate to manage update signature clients and i can't use the feature "Multiple Group update  providers" because this feature is not compatible when the gup is not present in the same subnet workstation.

    I try  to find a solution to active gup with a resolution FQDN. I want to use this method but i m not sure that the client SEP search the gup locally. Indeed i create  only one hostname to multiple adresse Ip ( Round Robin)

    gup.XXX.com 10.1.1.2

    gup.XXX.com 10.1.10.2

    gup.XXX.com 10.1.100.2

    gup.XXX.com 10.1.200.2

    Any idea about this ?

    I would like the client SEP  has the same process with GUP like  It locate a domain controller !

    thanks

     

     



  • 2.  RE: How to use FQDN to active feature GUP on multiple server ?

    Posted Jan 20, 2011 11:20 AM

    I am confused as to what you are asking.  If you have the same GUP same on each subnet or each domain, you can just specify the hostname in a LU policy.  If the first part of the name is always the same, you can specify gup* in the LU policy and any machine that starts with gup on the same subnet as the clients would be the GUP.  You can also create a specific registry key on each machine you want to be a GUP, then qualify it as a GUP in the LiveUpdate policy by the registry key.  In terms of Round Robin format, a client is always going to use GUP's on their own subnet, but if you have multiple GUP's on your subnet, and each one has a limit of 10 connections at a time, I believe that if your client could not connect to GUP A because it was maxed out, that as long as GUP B was on the local subnet, it would try GUP B or C or D....

    Hopefully this helps.



  • 3.  RE: How to use FQDN to active feature GUP on multiple server ?

    Posted Jan 20, 2011 12:29 PM

    Hi Mikael,

     

    One fix in Release Update 6 (RU6) to be aware of:

    GUP can no longer be set to an FQDN in the LiveUpdate policy
    Fix ID: 1854618
    Symptom: GUP can no longer be set to an FQDN in the LiveUpdate policy.
    Solution: Corrected to allow FQDN to be used in the GUP server settings.

     

    Upgrading may be necessary if thos eclients are still on old RU5.

     

    Hope this helps!!

     

    Thanks and best regards,

     

    Mick



  • 4.  RE: How to use FQDN to active feature GUP on multiple server ?

    Posted Jan 20, 2011 04:19 PM

    Thanks for your answers

    sorry , i didn't give  enough  details about my architecture . The "GUP" server 's name  on each subnet is different . (So it was too easy )  . I want to create one policy LiveUpdate and only one . Therefore i look for a solution with FQDN

    For the client 's version , i will upgrade the clients if it 's really  necessary !!

    After this upgrading ,  Mick  have you got any idea how  i could  create a policy LU  with FQDN / GUP ?

    Thanks  for your help !

     

    best regards



  • 5.  RE: How to use FQDN to active feature GUP on multiple server ?

    Posted Jan 20, 2011 04:59 PM

    Will the all the different GUP's names have something in common?  Maybe GupSanFrancisco, GupTokyo, GupLondon...

    You could create one LU policy, and set the Multiple GUP settings to Gup*.  That's all.  Then each client would search for a hostname that started with Gup* on their local subnet and use them for content updates.

    If you can't find an easy way to define them, create a custom registry key on each machine you want to be a GUP.  then you can set them as a GUP in the LU policy by pointing to this custom reg key.

    There are many ways to accomplish what you are wanting to do



  • 6.  RE: How to use FQDN to active feature GUP on multiple server ?

    Posted Jan 21, 2011 03:30 AM

    Hi Blenahan

    you said :"Then each client would search for a hostname that started with Gup* on their local subnet and use them for content updates."

    But the Gup server is a on a subnet 10.1.X.X and my workstation are on a subnet 10.100.X.X. Therefore the Multiple GUP Settings  (gup* or key registry ) is not working ! in this case , the update client failed !!



  • 7.  RE: How to use FQDN to active feature GUP on multiple server ?

    Posted Apr 03, 2011 03:37 AM

    I'd like to bump this, as this is also an issue I have with the way the GUP has been architectured.

    It doesn't allow for wanting to use the Multiple GUP feature in a multi-site design where servers often sit on their own VLANS, and simply putting a GUP in each vlan is overkill. The idea is to deploy a GUP for each site, which contacts the SEPM over WAN, while managing only one liveupdate policy. While breaking away from the intended design of the Multigup feature, I would prefer not consider which VLAN the GUP is in.

     

    If anyone has any feedback on how to get around this, that would be greatly apprecaited.

     

     

    Cheers.



  • 8.  RE: How to use FQDN to active feature GUP on multiple server ?

    Posted Apr 03, 2011 06:13 PM

    My understanding of the original question was as follows:

    Can mikael use one LU policy that states to contact gup.mydomain.com, but then have a DNS alias for every workstation subnet that points to the server at the local site.

    If you have a local DNS server per site, I believe you can achieve that. If you have only two DNS servers centrally like we do, then I think not. Every DNS server could have a static entry pointing gup.mydomain.com to the local server instead of pointing to one machine. effectively this would become a local alias per site.

    Sounds like an elegant plan to work around the SEP restrictions. Would like to know if anybody is willing or has already tried this.



  • 9.  RE: How to use FQDN to active feature GUP on multiple server ?

    Posted Apr 07, 2011 01:07 AM

    I'll keep you updated - I've just moved 5 sites onto a single LU Policy using a Static alias GUP at each site (DNS at each site). Deploying a reg key as a way of defining a gup.



  • 10.  RE: How to use FQDN to active feature GUP on multiple server ?

    Posted Apr 13, 2011 07:05 PM

    Hi Andrew.

    Have you got any update for us? Are your updates working? Is the DNS alias responding correctly? Are the clients downloading from the local GUP only?



  • 11.  RE: How to use FQDN to active feature GUP on multiple server ?

    Posted Apr 23, 2011 11:46 PM

    Hi Ian,

    Yes this has been tested and is a good workaround for this type of environment.

     

    Just to summarise, I've deployed the below regkey 'EnableGUP' to all the designated gup servers.

    Created a cname/alias Gup01 in DNS to put to the fqdn of the gup server. e.g server1.contoso.com

    Entered Gup01 in the optional box below, to workaround where either the client is pre 11.0.5002.333 and doesn't support multiple GUP's, or cannot find a gup on the same VLAN (servers/clients on different vlans as originally described in previous posts)

     

     

    I recommend using location policies for mobile users where you may wish to use LiveUpdate.



  • 12.  RE: How to use FQDN to active feature GUP on multiple server ?

    Posted Sep 22, 2011 04:21 AM

    Hi Andrew, hi Mikael,

    i have the same issue like you.

    Sites with a lot of VLANs. I want to use only 1 GUP per site.

    Please can you explain / send me your architecture more in detail.

    Thanks in advance,

    Stefan