MR4MP2 - some clients connecting to liveupdate.symantecliveupdate.com

The LU policy that you ,have  shows that if the Cleint doesnot take update from the SEPM, there may be diffrent reasons for that , it will take the update from the Symantec server.

uncheck the option that says Use the default Symantec LU server

Hi,

       You have selected both the options the default managemeent server as well as the Symantec default live update server. In this scenario  if a client is not able to communicate with the SEPM server it will fetch its updates from the Symantec default live update server

Correct me if I'm wrong.  If you have both options enabled (default management server and live update server), clients will try both servers to get updates and not going to the default management server first.  The following is from the help file:

If both options are enabled, clients try to retrieve updates from both sources. Typically, do not enable both options unless you have a specific reason. If the management server provides named update versions to clients, and the clients have previously downloaded the latest updates from a LiveUpdate server, the clients do not download and install the named (previous) versions.

 If you have both checked as per default schedule the client will try connecting to internet every 4 hrs.

We have a number of mobile computers that are connected part of the time to our hard-wired internal network, at other times to our network via VPN, and at other times to the Internet via various ISPs.  I am looking for the best way to configure updates so these computers get updated regardless of connection mode.

We are currently running SAV version 10.1.x, which allows to configure LiveUpdate to connect to the default server whenever the definitions are more than a few days old.  Under this arrangement, most clients update every day from their parent servers; but if a mobile computer is away from the network for a while, LiveUpdate kicks in to download updates.

Since SEP does not allow this option, I need to find another way to configure updates for computers that are on our internal network only part of the time.  What would be the preferred way to keep definitions current on these machines?

Use a location based policy that will check to see if it cannot connect to a SEPM server, it will connect to a live update server:

Thanks!  I was thinking a location-based policy might help, but I wasn't aware of the "cannot connect to Management Server" condition.  That's just what I need.