Configuring a site to download content updates

Article:HOWTO80915  |  Created: 2012-10-24  |  Updated: 2014-09-21  |  Article URL http://www.symantec.com/docs/HOWTO80915
Article Type
How To


Subject


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

Decision

Description

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 for Symantec Endpoint Protection clients.

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.

Note:

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 for Symantec Endpoint Protection clients.

How many content revisions should the site store?

In Symantec Endpoint Protection version 12.1.5, LiveUpdate content revisions are stored differently on the management server than in previous versions. Earlier releases stored full content for every revision. Now, the server stores only the most recent full content package, plus incremental deltas for as many revisions as you specify here. This approach reduces the disk space that is required to store multiple content revisions on the server.

The number of clients you select during the Symantec Endpoint Protection Manager installation defines the number of revisions the server stores.

For each LiveUpdate content type, the default values are as follows:

  • If you select fewer than 100 clients, Symantec Endpoint Protection Manager stores 12 revisions.

  • If you select 100 to 500 clients, Symantec Endpoint Protection Manager stores 21 revisions.

  • If you select 500 to 1,000 clients, Symantec Endpoint Protection Manager stores 42 revisions.

  • If you select more than 1,000 clients, then Symantec Endpoint Protection Manager stores 90 revisions.

In most instances during an upgrade, the installation increases the number of revisions to match these new defaults. This increase occurs if the number of revisions you had before the upgrade is less than the new minimum default, based on the above criteria.

See Configuring 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 Site 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 http://liveupdate.symantecliveupdate.com as the URL.

    Note:

    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.

  14. Click OK.

See Managing content updates


Legacy ID



v39542706_v81626096


Article URL http://www.symantec.com/docs/HOWTO80915


Terms of use for this information are found in Legal Notices