Configuring a site to download content updates

Article:HOWTO55200  |  Created: 2011-06-29  |  Updated: 2011-12-16  |  Article URL
Article Type
How To


Configuring a site to download content updates

When you configure a site to download LiveUpdate content, you have to make a number of decisions.

Table: Decisions about content downloads



How often should my site check for LiveUpdate content updates?

The default schedule of having Symantec Endpoint Protection Manager run LiveUpdate every four hours is a best practice.

What content types should I download to the site?

Make sure that the site downloads all content updates that are specified in your client LiveUpdate Content policies.

See About the types of content that LiveUpdate can provide.

See Configuring the types of content used to update client computers.

What languages should be downloaded for product updates?

This setting on the Site Properties dialog box applies only to product updates; the content updates are suitable for all languages.

What LiveUpdate server should serve the content to the site?

You can specify either an external Symantec LiveUpdate server (recommended), or one or more internal LiveUpdate servers that have previously been installed and configured.

See Setting up an external LiveUpdate server.

You should not install Symantec Endpoint Protection Manager and an internal LiveUpdate server on the same physical hardware or virtual machine. Installation on the same computer can result in significant server performance problems.

If you decide to use one or more internal LiveUpdate servers, you may want to 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.


If you use LiveUpdate Administrator version 1.x to manage your internal LiveUpdate server, you need to make a change if you applied custom Response packages. LiveUpdate clients that use the current release cannot authenticate custom Response packages. You should remove any custom packages from the central LiveUpdate server.

See Setting up an internal LiveUpdate server.

How many content revisions should the site store and should the client packages be stored unzipped?

One good reason to store multiple revisions of a single content type is to provide the ability to create and distribute deltas to clients. When Symantec Endpoint Protection Manager and the client have a content revision in common, Symantec Endpoint Protection Manager can use it as a base for a delta to send to clients. Clients can apply that delta to the same base locally to get the latest content. Deltas are typically much smaller than full packages, which results in major bandwidth savings.

You might also store content revisions because you might want to test the latest content before you roll it out to all your clients. You might want to keep earlier versions of the content so that you can roll back if necessary.


When you keep a large number of revisions, more disk space is required on the Symantec Endpoint Protection Manager.

See Configuring the disk space that is used for LiveUpdate downloads.

See Controlling the content revisions that clients use.

To configure a site to download updates

  1. In the console, click Admin, and then click Servers.

  2. Under Servers, right-click Local Site, and then click Edit Properties.

  3. On the LiveUpdate tab, in the Download Schedule group box, click Edit Schedule, set the options for how often the server should check for updates.

  4. Click OK.

  5. Under Content Types to Download, inspect the list of update types that are downloaded.

  6. To add or delete an update type, click Change Selection, modify the list, and then click OK.

    The list should match the list of content types that you include in the LiveUpdate Content policy for your client computers.

  7. Under Languages to Download, inspect the list of languages of the update types that are downloaded.

  8. To add or delete a language, click Change Selection, modify the list, and then click OK.

  9. Under Platforms to Download, click Change Platforms and then inspect the platforms list. Uncheck the platforms that you do not want to download content to.

  10. Under LiveUpdate Source Servers, click Edit Source Servers and then inspect the current LiveUpdate server that is used to update the management server. This server is Symantec LiveUpdate server by default. Then do one of the following:

    • To use the existing LiveUpdate Source server, click OK.

    • To use an internal LiveUpdate server, click Use a specified internal LiveUpdate server and then click Add.

  11. If you selected Use a specified internal LiveUpdate server, in the Add LiveUpdate Server dialog box, complete the boxes with the information that identifies the LiveUpdate server, and then click OK.

    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 Symantec public LiveUpdate server as the last server in the list. If you add the public server, use as 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 format domain_name\user_name.

    If the computer is in a workgroup, use the format computer_name\user_name.

  12. In the LiveUpdate Servers dialog box, click OK.

  13. Under Disk Space Management for Downloads, type the number of LiveUpdate content revisions to keep.

    More disk space is required for the storage of a large number of content revisions. Client packages that are stored in expanded format also require more disk space.

  14. Check or uncheck Store client packages unzipped to provide better network performance for upgrades.


    Disabling this option also disables the ability of Symantec Endpoint Protection to construct deltas between content revisions and may adversely affect network performance for updates.

  15. Click OK.

See Managing content updates

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices