Endpoint Protection

I just created a package using the console and used SMS 2003 to send it out to a machine (upgraded from SAV 10.1.5.500). It installed fine, I can see the machine is getting policies and definitions and all, but in the tray there is only a green dot, and no shield. Everything works as expected when I click on the green dot.

Anyone seen this strangeness?

Question about upgrade:

Is it necessary to delete scheduled scans, remove tamper protection etc.. when doing an upgrade from SAV?
When creating the package, If you choose the option to "remove all previous logs and policies, and reset the client-server communication settings" shouldn't this be sufficient?

What version are you at?

This was reported quite some time back:

https://www-secure.symantec.com/connect/forums/green-dot-no-shield-systray

For the upgrade process to be smooth the options disable scheduled scans, modify Quarantine purge options, delete histories, disable LiveUpdate, disable roaming, unlock server groups, and disable Tamper Protection( http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007071909500548 )
should be done. Not to be confused with the "remove all previous...." setting which wipes out the old settings but in no way can it prevent untoward incident for a broked or rollback install if the liveupdate or scheduled scan is running at the time of migration.

Thanks for the forum link, i did a search, but obviously did'nt use the correct terms, plus search on this site sucks sometimes :)

I'm on the latest version, 11.0.4014.26
This particular machine is on Windows XP SP2, if that makes any difference.

I just disconnected the network and I see that the shield is back, just like in the post. Reconnected and the shield is gone.

This particular machine is a Dell D600, Mobility Radeon 9000.

Do you have the latest video card drivers for your machine? If not install them and see if the shield appears again. Thanks.

Grant-

I don't the machine with me right now, will try tomorrow.
I'm quite sure that I have the latest drivers, since according to Dell's website, the latest and only drivers listed are dated 12/5/2005.

http://support.dell.com/support/downloads/driverslist.aspx?c=us&l=en&s=gen&ServiceTag=&SystemID=LAT_PNT_PM_D600&os=WW1&osl=en&catid=&impid=

Ok post back and let us know. I will keep looking at other options. There were a couple reasons why this used to happen, but have since been fixed in recent updates so those should not be affecting you.

Grant-

The newer driver seems to have resolved the shield issue.

I do have another issue on this machine...
on startup I get "firewall driver failed to open network adapter" in the client management - system log.

Did this "firewall driver failed to open network adapter" happen after the upgrade of the video card driver? I searched our database and we have only seen this error once, and it was on a SEP 11 machine. I will post what the solution to that problem was, and maybe we can work through how to get it to work on your machine. First a quick question though, does the network adapter still work although it is delivering this message? Regardless here was the solution to that other problem. Obviously you will your own driver name and files ect ect. Let me know if this helps, glad you are getting your shield back.

We have seen this error on broadcom NIC driver, eg Netlink 440X. The root cause is that the correct driver name is not added to the Network template properly. Check the driver name by clicking Modify, under NDIS2 driver tab, make sure the driver name is same as the name listed in protocol.ini, sometimes it would come up with just $ as the name, please add the full name to the field, like B44$.

Cheers,
Grant

I am using the same Dell Latitude D600 as you, and the chipset fot the particular on board NIC is indeed a Broadcom 570x Gigabit...
I dont have the firewal component installed in my machine currently, so I can't tell you what the name would be listed or the correct would be supposed to be listed as.

If however, the case is for you as mentionned above, let us know, I will install the component and post in "what it should say".  Unless of course, I get the same error message...

Yes, the error was there before the driver upgrade.
Yes, the network adapter works fine.

Will look at the network template on Monday.

I'm not clear on the template statement above, I have the statement "Firewall driver failed to open network adapter" in the system log. I don't see any network activity on the monitor. I see the sheild and all green on status. I'm wireless. any ideas, It must be my laptop, my desk top is fine.

I think it might be good to get a little more information on your system. What Symantec product are you using? and what is the version number of that product? How are you connecting to the SEPM since you are wireless (probably through VPN but if so what VPN client do you use)? Are you able to ping the SEPM and also does this client appear in the clients list on the SEPM? Most importantly you should probably post the system log so we can get a better idea of what is going on, and if it is not too much trouble please start a new thread for this issue so are not infriging on bjohns posts seeing as it is not solved yet.

Thanks
Grant

any new feedback on this resolution...
I was following this e-mail trail for info..
thanks..