Clients using the settings shown above tend to change the location every few seconds or minutes.Īfter some troubleshooting, I discovered, how to circumvent that issue: In the first condition of location “Internal” I replaced the subnet entries by IP ranges and the “location flipping” ended. Unfortunately, there seems to be a bug in SEP 14.2. The location “External has no conditions at all, so it is active, whenever the conditions of location “Internal” are not met. So you don't have to worry about restarting the SEPM.

Note: the second condition does not verify, whether the SEPM is available. If all IP addresses of the client are listed below:.The location “Internal” checks, whether the client has only private IP addresses configured and performs a NSLOOKUP to check, whether the DNS server is able to translate the SEP managers FQDN into a given IP address, which will most likely confirm, the client is in its own company’s environment: I usually configure two locations in order to detect, whether the client is onsite (internal) of offsite (external). In most cases, this is used to raise the client’s firewall, when the machine leaves the company’s protected network and connects to the internet via any kind of public hotspot. Symantec Agent for Mac version (SEPM) Mac versions prior to 14.

Over the last years, SEP location awareness has been admin’s friend: It enables security admins to configure different security policies that are automatically applied to computers depending on their environment. This is because the installer stub is a script that downloads the latest version of the agent from the public repository, which may be more up to date than the SEPM version.

Sepm 14.2