Endpoint Protection

Hello,

I am having an issue when my SEP client changes locations, it does not change automatically to the new policy created in SEPM. I have enabled location awareness in the policy general settings, and I have also enabled to Display the notification area icon. However, I am able to change locations manually by launching the SEP client and going into Change Settings > Configure Settings next to client management and change the location options, this picks up on the location policy instantly. The SEP client is running version12.1.4112.4156 and SEPM is running version 12.1.2015.2015. Assistance would be greatly appreciated.

What condition are you using to determine what location the client should switch to?

You can enable debugging for auto-location switching which may help here:

http://www.symantec.com/business/support/index?page=content&id=TECH102412&actp=search&viewlocale=en_US&searchid=1426779922863#AutoLocation

Hello,

I have enabled DHCP address does not match any of the addresses below where I then entered our DHCP Scope or if the following hosts cannot be pinged where I entered the IP address of our SEPM Server. I have also tried setting a condition if the client is unable to connect to the Management Server. I will look into the debugging for auto-location switching.

Thanks,

can you try with 12.1.5

Client takes longer to switch locations on Windows 7

Fix ID: 3256174

Symptom: The Symantec Endpoint Protection client takes longer to switch locations on the Windows 7 operating system.

Solution: Optimized the performance of location switching by using a different Windows API.

http://www.symantec.com/business/support/index?page=content&id=TECH224706

The SEP client never moves automatically, I waited 30 minutes for the client to change locations.

Brian, what am I supposed to look for in the debugger log, the page you directed me to shows logs regarding AL and I don't see anything in my logs representing that.

Should see info like so:

05/07 16:31:33 [916:828]  ***** AL begin get wins ip *****
05/07 16:31:33 [916:828] ***** AL begin get DNS ip
05/07 16:31:33 [916:828] ***** AL DNS Ip : 192.168.147.1
05/07 16:31:33 [916:828] ***** AL begin get gateway ip
05/07 16:31:33 [916:828] ***** AL begin get local ip and dhcp ip
05/07 16:31:33 [916:828] ***** AL local ip : 192.168.147.129
05/07 16:31:33 [916:828] ***** AL DHCP ip : 192.168.147.254
05/07 16:31:33 [916:828] ***** AL Dhcp ip :192.168.147.254 Mac :00-00-00-00-00-00
05/07 16:31:33 [916:828]  ***** AL begin get dns name *****

Unfortunately, I am not seeing any information similar to this. I went through the process of setting up debugging on my client but do not see this information.

Update on the issue...

I made adjustments to the Registry for debugging AutoLocation. It seems my location settings are not being applied at all because I am able to change from our out of office policy to our in office policy even when the conditions I have meet the out of office policy requirements. 

Does the client policy serial number match what shows on the SEPM?

Hello,

The Policy serial number does match to what shows in SEPM? I am now faced with two issues. Our out of office policy has LiveUpdate pulling updates from the default Symantec LiveUpdate server, over the weekend I checked system logs and no new policies were being applied to my client machine which makes me believe the client is not pulling updates.