Client not picking up boundary change until service restart

Hi All,

          SCCM 2012 R2 CU4 environment.

We have a number of surface pro 3 devices that regularly move between internet connected (where they use DA), not network connected and connected to the internal network.

The docs using these devices also rarely seem to reboot the devices.

The SCCM client seems to sometimes struggle updating its current location in locationservices.log.... resulting in content being marked as unavailable in the cas.log, when ofcourse it is available.

A restart of ccexec "fixes" it.... as the location is correctly updated.... but this isn't a viable fix for every machine every time it happens.

Are there any settings that I am unaware of where we can force a client to re-evaluate its location every x ? or what is the state-change trigger which causes this?

May 18th, 2015 12:33am

How exactly are they moving between networks?

No there is no switch or setting to have it eval network location.

Free Windows Admin Tool Kit Click here and download it now
May 18th, 2015 6:25am

When they move between being on the internet on a 4G device (for example) - then come back into one of the offices and swap over to internal wifi

or they will not be connected, put their device to sleep, come back into the office and connect via wifi.

May 18th, 2015 7:12am

Content location requests are sent every time a client needs content. The client itself, never really knows what boundary it is in. The request along with the client's IP are sent to the MP which in turn returns the DPs (with the content) available to the client.

Thus, there's something else slightly different going on here.

I', assuming that you have IBCM set up. Are the client's properly reflecting a switch from Internet to Intranet in the control panel when they switch networks?

Free Windows Admin Tool Kit Click here and download it now
May 18th, 2015 9:57am

Hey Jason,

              I don't believe so. That's what I was trying to say in my clumsy way.... I saw it in locationservices.log, as I couldn't get onto the machine directly.

Tomorrow I will try and get a session on the machine with the issue so I can verify it through control panel.

May 18th, 2015 10:10am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics