symantec endpoint protection for mac error live update

Symantec instructions on configuring the Web site work as documented other than the above.

Assign the .mil signed by the standalone CA as shown:

Create new Web site named “LUA” and bind to the dedicated IP using only https as shown below.

Create server certificate for .mil using the standalone certificate authority.

Be sure to bind the Default Web Site to the original WSUS IP (172.24.4.14) so that it will not conflict with Symantec AV:.

(Server 2008 R2 IIS 7.5 would already have this as an installable IIS Role Service.)

Webdav installed from Microsoft download as documented.

Create new AD group “SymAV” with a user “lua”.

Do not use the default Web site as that is reserved for WSUS.

Provide new IP so that new Web site can be created (172.24.4.68).

Restart the server after installation to be sure that all files and services created OK. Also, for troubleshooting be sure to install the following from Health and Diagnostics section of IIS Role Services: “HTTP Logging”, “Logging Tools”, “Request Monitor”, and “Tracing”.

IIS Role Services: Both “Basic Authentication” and “Directory Browsing” must be installed.

(Server 2008 R2 is similar but has its own page and also includes WebDAV as installable Role Service.) Follow steps below: Found reference which is specific to Windows Server 2008 and IIS 7.

Setup IIS to be the “Distribution Center” that clients can access.

We actually used our existing WSUS server!

Added only Symantec AntiVirus for Linux on the target server.

In this paper, we specifically document the *differences* between our install and the standard “Next-Next-Next” Symantec LiveUpdate Server install.

This article shows how we solved this requirement by creating a local Symantec LiveUpdate Server within our lab environment. Symantec Endpoint Protection (SEP) depends on having up-to-date virus signatures pushed automatically from a centralized location.

Symantec endpoint protection for mac error live update