Endpoint Protection

Morning guys,

When i am trying to edit a shared policy (i want to add a scheduled scan) i am getting the error message above. Our SEPM is only 1 version below the latest but according to Symantec it should have already been fixed with our version. I tried some of the workarounds like restarting the service or logging in with a user that the policy i am trying to edit is not applying on (I created a local admin account and logged in) but i am getting the same error message.

Any idea what's going on?

Thanks guys!

have you tried restarting the server ? 

what happens when you run the Management server configuration Wizard ?

finally you may want to try and run a repair install of SEPM, if that doesn't fix mostly likely the support will ask you to upgrade to the latest version of SEPM

Yes, I do remember this issue in a prior version and it should've been fixed. May want to engage support to see what they think. You can also try 12.1.6 MP5 though, if possible.

How can i run the managment server configuration wizard Praveen?

On the SEPM go to Start >> All Programs >> Symantec Endpoint Protection Manager >> Symantec Endpoint Protection Manager Tools >> Management Server Configuration Wizard

Cool, i'm here. Where am i going from here?

When trying to repair i am getting an error message that the MSI is missing. This was installed a long long time ago by somebody else so i do not recall ever seeing that MSI installation package. Any idea?

there is noting visible, can you upload the file as an attachement 

ooops... my bad.

Here is is :)

Had same issue. Running it won't solve your issue. Just fyi

just click next and keep going don't change any settings.

some times runing MSCW does resolve few problems, so I guess its worth a shot

Not in this case it will not

Should I say "yes" or "no" on this one?

oh man, do you even have the cert in the recovery file??

I'm not sure. This is all very new to me

I hit "yes" after i read on this article that there is no risk:

https://support.symantec.com/en_US/article.TECH232077.html

However, KateUp was right and it still did not resolve my issue

Any other options guys other than upgrading to the latest?

Perhaps creating a new policy, with the same settings as the old one, and assigning it to your groups may take care of it.

That did the trick. Looks like it was a broken policy.
By the way, is the latest version 12.1.6 MP5?

That's great to hear. I'm glad it is working.

Yes, the latest version is 12.1.6 MP5, even though the build number is 12.1.7004.6500, which has confused some folks.

You can find the most up to date release info here:

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