SEP11 MR4 MP2: some clients have Network Threat Protection (firewall) some NOT
Updated: 21 May 2010 | 5 comments
Hello,
we are using Symantec Endpoint 11 (ver. MR4 MP2) on our site. Symantec Endpoint Protection Manager is installed on Server. Server takes care of 11 clients. Server is IBM xSeries with OS: Windows 2000 Server.
I have generated clients installations with all protections and installed them on clients computers. Clients are running but there is a strange think: some clients (4) have Network Threat Protection (firewall) and some (7) NOT. On clients where is no Network Threat Protection Windows security center says to me a problem with firewall. All client OS is Windows XP Professional.
Does anyone know what is wrong?
Thank you for your advice.
discussion Filed Under:
Comments
Did you restart those
Did you restart those PC's?
Regards,
Regards,
Giuseppe
The firewall driver can only
The firewall driver can only activated after a restart.
Aniket
I saw the same thing during
I saw the same thing during my migration from SAV. (no, it's not a restart issue in my situation.)
I used the same package to install to around 3000 machines. Out of this, about 15 machines said the firewall was not installed. (yes, they restarted after the install)
I was using SMS to install and the package was installed successfully, In fact AV and PTP were installed.
I had to reinstall SEP on these machines.
XP SP2, using the latest SEP version.
Hi I have seen this
Hi I have seen this before.
You can do one thing under the groups where your client are reporting to the SEPM you can add a client install package & uncheck the option for maintain existing feature set & select all features under it.
This should give you the solution.
You can check these documents
http://service1.symantec.com/support/ent-security.nsf/docid/2008031118335548
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008111808135348
If this resolves the problem mark it as the solution to this thread.
Restart fixed mine
I just freaked out when NTP didn't show up after i upgraded SEPM to MR4_MP2 but fortunately a restart fixed my one.
Did the above links sort out your issue?
Would you like to reply?
Login or Register to post your comment.