Endpoint Protection

 View Only

  • 1.  SEP12.1 RU1 Liveupdate Policies Process Question - management server plus liveupdate server

    Posted Jun 18, 2012 09:45 AM

    Good morning,

    We are deploying SEP12.1 RU1 clients, our liveupdate policy has both the 'Use the default management server' plus the 'Use the default symantec live update server' options selected.

    I have noticed that a fresh install of a managed SEP 12.1 Ru1 client will immediately connect to the symantec liveupdate server to get the updates (we are pushing a package with no updates bundled).  Is this due to the fact that we have both live update options above selected in our policy?  Shouldnt it first try the management server and then try to the symantec liveupdate servers if the management server does not respond? 

    How do i set the policy to force the updates from our management server after a new install but also give the users the ability to use symantec's server down the road if they need to to?

    Regards,

     

     



  • 2.  RE: SEP12.1 RU1 Liveupdate Policies Process Question - management server plus liveupdate server

    Trusted Advisor
    Posted Jun 18, 2012 09:52 AM

    Hello,

    This may contain some answers:

    What happens when both LiveUpdate Server and Default Management server are configured in a LiveUpdate policy?

    http://www.symantec.com/docs/TECH140817

    Symantec Endpoint Protection Manager 12.1 - LiveUpdate - Policies explained

    http://www.symantec.com/docs/TECH178257

    Please do keep the thread up to date with your progress if this article does not contain the answer you were seeking!



  • 3.  RE: SEP12.1 RU1 Liveupdate Policies Process Question - management server plus liveupdate server

    Broadcom Employee
    Posted Jun 19, 2012 06:18 AM

    Hi,

    When configuring the LiveUpdate policy, there is no option to configure LiveUpdate as a backup only in case the client can not connect to the SEPM.   This can, however, be achieved through the use of different Locations.

    Configuring both sources in LiveUpdate policy can cause the following problems :

    • The client may have to download a large full.zip set of definitions from the SEPM if it downloaded a previous revision from LiveUpdate that is not present on the SEPM (SEPM will be unable to create the appropriate delta)
    • If a definition roll back is configured on the SEPM, it will be ignored by LiveUpdate.
    • If the SEPM definitions are always behind because of definition testing, then the client will most likely always update from LiveUpdate.

    As such, this configuration is usually not recommended and should only be used with a good understanding of the above.