Video Screencast Help

Intrusion prevention signature failures

Created: 16 Oct 2012 | 10 comments
ksu's picture

How can i solve this problem?

 

Comments 10 CommentsJump to latest comment

Ashish-Sharma's picture

HI,

You can check this artical may be help

Symantec Endpoint Protection Manager 12.1 console home page showing Security Status - Attention needed

http://www.symantec.com/business/support/index?page=content&id=TECH164272

This is a known issue which has been fixed in SEP 12.1 RU1. For more information read the following document: New fixes and features in Symantec Endpoint Protection 12.1 Release Update 1

A possible workaround for this issue is to change the date format used by the SEPM for logs and reports. Note: making the below changes will modify all reports and logs displayed in the SEPM to use the MMDDYY format.

To Modify the date format used by the SEPM:

  1. Log into the SEPM Console
  2. Click the Preferences link In the  Security Status section on the SEPM Home tab
  3. Select the Logs and Reports tab
  4. Select  MMDDYY from the Date format combo box
  5. Click the OK button to close the Preferences page
  6. The changes to these settings may take a few minutes to take effect. You may also refresh the Home page by clicking on the Refresh option on the top right corner.

Thanks In Advance

Ashish Sharma

 

 

Ashish-Sharma's picture

This is a known issue which has been fixed in SEP 12.1 RU1. For more information read the following document: New fixes and features in Symantec Endpoint Protection 12.1 Release Update 1

Thanks In Advance

Ashish Sharma

 

 

pete_4u2002's picture

the latest one is oct 16th, how many systems are in the nework with IPS ?

are all showing out of date?

ksu's picture

What you mean by how many systems are in the network with IPS?

No only intrusion prevention signature.

.Brian's picture

What was the solution?

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

ksu's picture

I have restarted the SEPM server and restarted the symantec embedded database service.

 

Thanks