Downloading content from LiveUpdate to your devices
Symantec Endpoint Security, a LiveUpdate server downloads content directly to the clients from the cloud console, rather than to a management server and then to the clients. By default, the clients download content updates from the public Symantec LiveUpdate servers.
FAQs about downloading content
Which LiveUpdate server should download the content?
You can specify either a public Symantec LiveUpdate server (recommended), or one or more internal LiveUpdate servers that have previously been installed and configured.
If you decide to use one or more internal LiveUpdate servers, you should add the Symantec public LiveUpdate server as the last entry. If your clients cannot reach any server on the list, then they are still able to update from the Symantec LiveUpdate server. You should also upgrade your internal LiveUpdate servers to the latest version of LiveUpdate Administrator. See:
How many content revisions should the domain store?
The LiveUpdate server stores only the most recent full content package, plus incremental deltas. This approach reduces the disk space that is required to store multiple content revisions on the server.
The number of revisions the server stores depends on the number of devices that you install.
How often should I schedule LiveUpdate to check for content updates?
The default schedule of running LiveUpdate every four hours is a best practice.
What operating systems am I downloading content to?
LiveUpdate downloads the content for Windows devices. Even if you do not have Mac clients, the content is available for them to download.
What types of content does LiveUpdate download to the clients?
LiveUpdate downloads all content types automatically. The content includes virus and spyware definitions, behavioral analysis heuristic signatures, Intrusion Prevention signatures, submission control signatures, reputation settings, and advanced machine learning. You cannot choose which content you want to download.
In addition, LiveUpdate downloads software updates for the clients in that domain.
You configure the schedule for client updates in the
Client Upgrade Settingssection of the System policy. See:
Should I test engine updates before they are released?
For large organizations, you should test the new engine updates and definitions before they are rolled out to all client devices. You want to test new engine updates with the minimal amount of disruption and downtime.
To test engine updates, select the
Use the Symantec LiveUpdate server for prereleased contentoption.
Configuring a LiveUpdate server and schedule
- To configure a LiveUpdate server and schedule
- Go toEndpoint>Policies>Default System Policy.Default System Policy (14)is the default policy for the hybrid management only.
- UnderLiveUpdate Server, select one of the choices for a LiveUpdate server:Use the default Symantec LiveUpdate server by defaultis for the public LiveUpdate server that Symantec set up.
- To test beta content, selectUse the Symantec LiveUpdate server for prereleased content.
- To use multiple LiveUpdate servers, selectUse a specified internal LiveUpdate serverand then selectAdd. Specify the information that identifies internal LiveUpdate servers that you have installed, and then pressAdd.You can add more than one server for failover purposes. If one server goes offline, the other server provides support. You can also add the public Symantec LiveUpdate server as the last server in the list. If you add the public server, usehttp://liveupdate.symantecliveupdate.comas the URL.If you use a UNC server, then LiveUpdate requires that you use the domain or workgroup as part of the user name.If the computer is in a domain, use the formatdomain_name\user_name.If the computer is in a workgroup, use the formatcomputer_name\user_name.
- In theLiveUpdate Schedulinggroup box, selectShow Advanced, and choose the options for how often and when the server should download updates to the clients.
- SelectSave Policy>Yes>Yes.