How to manually update definitions for a managed Symantec Endpoint Protection Client using the .jdb file
|Article:TECH104363|||||Created: 2008-01-07|||||Updated: 2012-08-30|||||Article URL http://www.symantec.com/docs/TECH104363|
You would like to know how to update definitions for the Symantec Endpoint Protection (SEP) client using the .jdb file.
In a managed environment, the Daily Certified or Rapid Release .jdb file can be used to update virus definitions for the SEP client.
To update a managed client with a .jdb file:
- In the Symantec Endpoint Protection Manager, go to Clients.
- Select the group in which the client or clients can be found that need to be updated manually.
- Edit the LiveUpdate Settings Policy.
- In the LiveUpdate Policy, choose Server Settings in the left pane.
- In the right pane, under Third Party Management, enable the option "Enable third party content management".
- On the SEP client, make sure that the client received the policy change by checking for the existence of the 'inbox' directory as following paths:
%ALLUSERSPROFILE%\Symantec\Symantec Endpoint Protection\inbox
%ALLUSERSPROFILE%\Symantec\Symantec Endpoint Protection\CurrentVersion\inbox
(Please note that on SEP 12.1.x clients the \inbox directory is always present, please check the Policy serial number to ensure it's matching the one published by SEPM)
- Download the .jdb file from the Symantec Security Response Website:
- http://www.symantec.com/avcenter/defs.download.html for Certified Definitions.
- http://www.symantec.com/avcenter/rapidrelease.download.html for Rapid Release Definitions.
Note: the file extension may change to .zip upon download. If this is occurs, change it back to .jdb.
- For each SEP client that needs to be updated, copy the .jdb file into the folder noted in #6 above.
- After a few minutes the .jdb file will be automatically processed. When complete, the client should reflect new antivirus definitions.
If a TPM update fails, the content copied to the inbox will be moved to a folder called "invalid". Possible reasons:
- TPM has not been enabled
- The file type is not supported
- The file structure is incorrect
- The content being installed via TPM is already installed or is older than what is installed
For more details on TPM and updates regarding SEP 12.1 clients, see TECH106028, "
Article URL http://www.symantec.com/docs/TECH104363