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.

Centralized exception not working

Updated: 21 May 2010 | 3 comments
manish-SecPol's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

I have made a few Centralized exception from SEP Manager Console but the client is not taking the exceptions.
However when I create those exception locally from the client it works.
What can be the issue?

Comments

Vikram Kumar-SAV to SEP's picture
05
Oct
2009
1 Vote +1
Login to vote

Exceptions

 What do you mean by not taking ?
From MR3 onwards the Admin-Defined exceptions are not shown on the clients.
When you create User-Defined exceptions from from the SEP GUI it will be shown on the client.
to make sure your Client has received the exception from SEPM you will have to check the registry entries.
Read this article point9
https://www-secure.symantec.com/connect/articles/symantec-endpoint-protection-few-registry-tweaks

sandip_sali's picture
05
Oct
2009
0 Votes 0
Login to vote

Centralized exception not working

Hi,

       You mentioned that the exception work locally from the client and not from the SEP Manager Console. When you assign the policy from the SEPM to the group to which the client belongs check the policy serial number at SEPM console and also at the client end this would help us understand whether the right policy is being assigned to the client.

policy serial number.JPG

Thanks & Regards Sandip C Sali

manish-SecPol's picture
05
Oct
2009
0 Votes 0
Login to vote

Hi Sandip, the client is

Hi Sandip,
the client is policy updates and policy number is same on both.

Hi Vikram,
I think you are right i just checked the registry entries as per the link you gave me and it looks the client is taking the exception policy.
thank you for all your help.