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?