Sophos updating policy allow location roaming
Microsoft touts Windows 10 as the mobile and cloud platform of the future.However, it is interesting to see how the operating system performs in traditional environments – that is, environments that you choose to deploy and manage using time-honored technologies most of us have been relying on for years. Microsoft was the first entrant into the market that grew up around user mobility, allowing network-based profiles to persist across multiple desktop sessions.At first logon, most users customize this to their own preferences.However, the data for these Tiles is stored in the %LOCALAPPDATA% folder, meaning that it simply does not exist within a roaming profile.
Typically this is done by defining the “Delete cached copies of roaming profiles” GPO and setting it to Enabled.
Windows 10 and roaming user profiles don’t harmonize well.
In this post, you will learn about the various traps you might fall into if you’re working with roaming profiles in Windows 10 in your network.
In fact, there is a tool already in beta, called , which appears to do precisely that, saving the user state into an Azure Active Directory (AD).
Is this the wider play and the reason that Windows 10 appears to be incompatible with traditional forms of roaming? Already enterprises are holding back in some areas because of concerns about how their traditional management and deployment methods will function on Windows 10 and how much adaptation is required.
In Windows 10, though, a hook from a process (called the State Repository Service) will more often than not prevent the profile from being unloaded.