Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

IPS definitions status conflict in SEPM

Created: 06 Feb 2012 | 8 comments
Yahya's picture
0 0 Votes
Login to vote

I am using SEPM 12.1 RU1, the same goes for SEP clients. All definitions seems okay. However, for IPS, in the client view (group view) the defitions for IPS are shown as vaild and up-to-date

But when I check one of the clients properties, the IPS definitions are not vaild

The two status are in conflict, and the IPS is really up-to-date. The issue is for all clients on both SEPM.

Did anyone encounter such issue and how did you fix it?

Comments

pete_4u2002's picture
06
Feb
2012
0 Votes 0
Login to vote

change the date

change the date format

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

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 DDMMYY 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
Yahya's picture
06
Feb
2012
0 Votes 0
Login to vote

Didn't work

 

 

I can't see how this is related. Anyway, I have tried and didn't work.

 
 

pete_4u2002's picture
06
Feb
2012
0 Votes 0
Login to vote

if the client is showing the

if the client is showing the wrong information as that of SEPM, can you pass on the sylink log from client?

Yahya's picture
06
Feb
2012
0 Votes 0
Login to vote

Again

 

 

Pete,

Can you read the issue again, I think you got it wrong. SEPM showing different status for IPS, one is correct in client group and one is wrong in client properties. see the screenshots, they both from SEPM and they don't match.

 
 

pete_4u2002's picture
06
Feb
2012
0 Votes 0
Login to vote

I'm sorry for misreading the

I'm sorry for misreading the issue :-(.

I did check on my test setup, it seems to be reflecting correct on client properties.

can you open a support case ?

can you try deleting one such client from SEPM and check if back once it report, does it report correct status?

Yahya's picture
07
Feb
2012
0 Votes 0
Login to vote

Support Case

 

 

I opened a case a week ago, and the answer was to repair SEPM and delete the problematice client from SEPM. But it is showing on all clients, not one. And on both SEPMs. I don't want to repair and reconfigure both SEPM and delete all clients for cosmatic issue. I was wondering it is appearing with others.

 

P.S I had them upgrade from SEP11 to SEP12.1

 
 

pete_4u2002's picture
07
Feb
2012
0 Votes 0
Login to vote

yes, however it would be

yes, however it would be great to test by deleting one SEP client from SEPM console and monitor it reflects back with correct entry.

be ensured that the client will connect back to SEPM ( if no communication issue).

Simpson Homer's picture
06
Feb
2012
1 Vote -1
Login to vote