Windows Firewall Status - Showing Not Controlled by SEP

[Migration User]

Sometimes I randomly notice that the Windows 7 firewall is not being controlled by SEP (as I would like it to be). Also, if the Windows Firewall service is restrated, the message "These settings are being managed by vendor application Symantec Enpoint Protection....." is no longer there.

The only way I can seem to fix this is by doing a repair option under Control Panel/Programs/SEP
or
Sometimes restarting the comp will work.

1) What is it that SEP does under the hood to set/tell windows (in the repair operation) to make the message reappear saying "These settings are being managed by vendor application Symantec Enpoint Protection....."
2) Is there any other way to fix this other then repair/reboot
3) I would like to write a small c# app to monitor this, and make sure SEP is on control at all times, so any info here would be greatly appreciated.


CORRECT**




NOT CORRECT**

[Migration User]

On one of the machine upgrade the SEP version to RU6 a. I had dealt with a customer who faced a similar issue last week and it helped. Please keep me updated.

[Migration User]

I am using SEP 12.0.1001.95, I thought RUP was for version 11?

This is stand alone un-managed machine running Windows 7 Ultimate 64-bit.

[Migration User]

In this case you are using SEP Small Business ver 12.0 the version in use is the latest version. I am yet to test it on a 64 bit Windows 7 machine. In the meanwhile I had checked the site and the screenshot below shows that it has an Unmanaged client option only for 32 bit. I will let you know once i check this information.

[Migration User]

Hi Sandip,

I think I got to the bottom of this -- I just tested it out.

If I restart the Windows Firewall service, Windows no longer shows that SEP is 'controlling' the settings.
If I then restart the "Symantec Management Client" service Serice name "SmcService"  - The firewall returns back to the **Correct state, showing SEP is in control.

I am going to do some testing adding the Windows Firewall as a dependency to the Symantec Management Client service, to ensure that SEP starts after the Firewall service.

[Migration User]

Thanks for the update

[Migration User]

In order to completly resolve this issue, I just set the windows firewall service to Disabled.