Downloading LiveUpdate (LU) content to Symantec Endpoint Protection clients for Mac and Linux.
In Symantec Endpoint Protection (SEP) 14.1.x and later, you have at least two options for downloading LiveUpdate (LU) content to Symantec Endpoint Protection clients for Mac and Linux.
Note: Linux client support is added with Symantec Endpoint Protection 12.1.5 and is only available starting with that release.
Below are the instructions to set up the Apache web server in Symantec Endpoint Protection Manager to allow Symantec Endpoint Protection clients for Mac and Linux to download LiveUpdate (LU) content by the webserver. Please note that this solution enables Symantec Endpoint Protection Manager to act as a cache: it does not process Mac or Linux definitions into .dax files as it does with Windows definitions. It does not enable Symantec Endpoint Protection clients for Mac or Linux to update from a Group Update Provider (GUP).
Note: Installing and configuring a reverse proxy is beyond the scope of what support can assist with, this article is provided as-is to show an example of how it can be achieved
Take the following steps to configure Apache web server to serve as a reverse proxy:
If the files are not present, copy the files from the downloaded installation folder or DVD from \Tools\Apache-ReverseProxy to SEPM_Install\apache\modules. Refer to the section Security and Compatibility below for more details.
#
to comment it out, as shown: #AsyncSendFile anydirectory
AsyncSendFile givendirectory
ForceAsyncSendFile "SEPM_Install/Inetpub/content"
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%h %l %u %t %{cache-status}e \"%r\" %>s %b" common
# SEPM_APACHE_AS_PROXY_START Preserve this line to maintain configuration across SEPM upgrades LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_http_module modules/mod_proxy_http.so LoadModule cache_module modules/mod_cache.so LoadModule cache_disk_module modules/mod_cache_disk.so LoadModule setenvif_module modules/mod_setenvif.so <IfModule mod_proxy.c> <IfModule mod_cache.c> <IfModule mod_cache_disk.c> <IfModule mod_setenvif.c> SetEnvIf Request_URI "/luproxy/" dolog SetEnvIf Request_URI "/luproxy/.*_livetri.zip" no-cache CustomLog "|| bin/rotatelogs.exe logs/access-%Z.log 25M" common env=dolog </IfModule> ProxyPass /luproxy/ http://liveupdate.symantecliveupdate.com/ retry=0 smax=0 ttl=60 CacheRoot "cache-root" # CacheRoot is a path defined relative to [SEPM_Install]/apache/ CacheEnable disk /luproxy/ CacheDirLevels 1 CacheDirLength 5 # directives to override any caching prohibitions in LiveUpdate content headers # see TECH230862 CacheStoreNoStore On CacheIgnoreCacheControl On CacheStoreExpired On CacheIgnoreHeaders Cache-Control Pragma #allow downloads up to 1 GB CacheMaxFileSize 1000000000 </IfModule> </IfModule> </IfModule> # SEPM_APACHE_AS_PROXY_END Preserve this line to maintain configuration across SEPM upgrades
To test that the proxy server is running by downloading an LU file, click Start > Run, and then enter http://localhost:8014/luproxy/masttri.zip. If your Symantec Endpoint Protection Manager Apache web server uses a different port than 8014, replace 8014 with your actual port number in the above URL.
Note: While the massttri.zip file is requested via a local URL address, the request is passed to Symantec's public LiveUpdate server. Make sure that the connection to LiveUpdate web domains can be established from the Symantec Endpoint Protection Manager server according to TECH102059. The reverse proxy also requires a direct connection to Symantec's LiveUpdate servers - it cannot itself go through another proxy.
The reverse proxy will fail to download content from Symantec if the environment requires use of a (forward) proxy for outbound connections. The reverse proxy ignores any proxy settings that are configured in the SEPM server properties or Windows Internet Options. You can use ProxyRemote directive to go to another proxy but will be effective only with forwarding proxies that do not require authentication.- Reverse proxy does not use Endpoint Protection Manager's proxy settings
The LU download requests to the Apache web server are logged in a separate log file, located in SEPM_Install\apache\logs\access-%Z.log.
Take the following steps to update your LiveUpdate policy for Mac and Linux clients for your desired groups. Once the policy is updated, these clients will point to the newly configured Apache web server for downloading LU content.
Additionally, on SEP 12.1.x clients for Linux, edit the liveupdate.conf file and set serverlogging=false. SEP For Linux 14.0 does not require this setting. See TECH230862.
To manage the size of your cache file, take the following steps.
This will run the htcacheclean tool in daemon mode. The cache cleaning will be done on a daily interval. The maximum cache size allowed on disk is 1 GB.
To automatically start the htcacheclean daemon every time Windows starts, take the following steps.
Since the task does not run until you restart the system, you can run it now. In the Task Scheduler, right-click the task you created, and then click Run.
Note: Ensure that the user account running the task has full control on the folder SEPM_Install\apache\cache-root.
This configuration is designed for small numbers of Mac and/or Linux clients. You should only use this setup if there are only a few Mac and/or Linux clients and the network connecting clients and Symantec Endpoint Protection Manager has good bandwidth throughput. Assuming that each client downloads roughly 500KB of LU content on daily basis, 2000 Mac or Linux clients will result in a download of approximately 1 GB of LU content daily from the Apache web server. For configurations having large numbers of clients, you should consider an alternative like Symantec LiveUpdate Administrator.
Symantec suggests the use of only Symantec-signed binaries for Apache modules that are mentioned in this article. These signed binaries are available on the Symantec Endpoint Protection downloaded installation file. Note that the required binaries also get installed along with Symantec Endpoint Protection Manager for versions 12.1.4 and later.
For Symantec Endpoint Protection 14:
Because new vulnerabilities may be published after the publication of this article, please check the vulnerabilities published by the Apache project for the appropriate version of Apache web server: http://httpd.apache.org/security/
Note that upgrading the SEP Manager may reset or overwrite this configuration file. As such, after a SEPM upgrade ensure the changes made to httpd.conf are checked and corrected.