for 12.1 (IDSDefs & VDefs)

The instructions for SEP11 can be found in the below article:

http://www.symantec.com/docs/TECH104779

The steps for including them in a SEP12.1 package (if you don't want to bother with exprting a new package altogether) are the same, but I've not been able to find an article with all the correct locations for each def type (VirusDefs/IPS/32bit/64bit).

The closest I've found is below, you may have to rummage around a bit on your SEPM to find the others:

http://www.symantec.com/docs/TECH183672

hi Vijay,

Check this thread.

https://www-secure.symantec.com/connect/forums/adding-latest-definition-files-existing-sep-121-ru1-client-package

Hello,

What version of SEPM are you running?

Incase of SEP 11.x, please check this Article:

How to deploy the Symantec Endpoint Protection (SEP) client Release Update 5 or newer with current virus definitions and intrusion prevention signatures.

http://www.symantec.com/docs/TECH104779

However, for SEP 12.1, when SEP version 12.1 clients are deployed with Packages from SEPM, these packages are created with Latest virus definitions in it. So, as soon as SEP clients gets installed these clients are installed with latest virus definitions.

However, the condition is the packages are supposed to be created on the same date / time as deployment.

In reference to the IPS signatures, check this Article:

How to manually update IPS definition inside SEP 12.1 install package?

http://www.symantec.com/docs/TECH183672

Check this IDEA: https://www-secure.symantec.com/connect/ideas/include-latest-content-updates-exported-sep-clients-packages

Hope that helps!!

Hi,

For SEP 11 you will have to perform manual steps as stated above.

In SEP 12.1 SEPM should be updated. If SEPM is updated then packages will contain latest definitions in it.

Upgrade all the clients to the latest version i.e. SEP 12.1

After exporting packages save it in a DDMMYY format so in the future you will come to know when it was exported last time.

I was looking for the same thing to make sure that the Vdefhub and Ipsdef signature files were up to date in the exported package. I knew which ones were for the Vdefhub but not the intrusion prevention signatures until I came across the article below :

http://service1.symantec.com/SUPPORT/ent-security.nsf/2326c6a13572aeb788257363002b62aa/c7a72ad01d122b13882574330072026a

Regards,

Jon Logan.