
On A SEP12 machine the current Virus Definition Version property evaluates correctly: q: if (exists key "HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\CurrentVersion\SharedDefs" whose (exists value "NAVCORP_70" of it) of registry) then ((if (exists "\" of it AND following text of last "\" of it contains ".") then (preceding text of last "." of following text of last "\" of it & ", rev. The Symantec registry keys have changed location for the virus definition version and both keys may exist if the machine was upgraded from SEP12 to SEP14. For more information check the link here.We have begun rolling out SEP14 and have noticed that the Virus Definition Version does not display the correct information for SEP14 clients. The benefit of this is that if you have road warriors or people who rarely if ever, come into the office you can still see the full health of their SEP client and computer and still manage the client with policies.

It also requires that you add the public IP of SEPM to the Management Server List and then sending out the new SYLINK file. This requires opening one port on your firewall and NATing it from a public IP to the private IP of the SEPM server. The second method I use to manage mobile workers is to publish my Symantec Management server onto the internet. The benefit here is that the definitions are only downloaded from the internet once. My outside the office LiveUpdate policy tells the EndPoint clients to go directly to the internet for definitions.


One example is that my inside the office LiveUpdate policy only uses the Management Server to obtain definition updates. One for inside the office and one for outside the office. I apply these locations to the client group where my mobile workers reside.

Typically when I set up location awareness I set up two locations. Location awareness allows you to set one set of policies when users are in one location and a separate set of policies when they are in a different location. There are a couple of ways to manage mobile workers with regard to Symantec EndPoint Protection.
