Sophos updating policy allow location roaming

02-Mar-2020 00:55

Potential issue: The field for Azure Ad Settings Url is empty and the device does not sync.

The user may have last logged in to the device before Enterprise State Roaming was enabled in the Azure Active Directory Portal. Optionally, in the portal, try having the IT Admin disable and re-enable Users May Sync Settings and Enterprise App Data.

You’ll have to remember to enable this option yourself though – create a Setup customisation with the Office Customization Tool and enable the following option: Nice and simple with no need for additional work in your user environment management tool of choice to roam those settings – happy users.

If you have already deployed Office 2010 and need to change this setting, there are a couple of ways that this can be done: 1.

If it is showing this, the device may need to wait for policy to be applied or the authentication for the device failed when connecting to Azure AD.

Recommended action Connect the device to a corporate network so that sync can resume. User Name instead of username) and the user is on an Azure AD Joined device which has upgraded from Windows 10 Build 10586 to 14393, the user's device may fail to sync.

In Event Viewer under the Setting Sync-Azure logs, the Event ID 6013 with error 80070259 is frequently seen.

Recommended action Make sure the Windows 10 v1607 client has the August 23, 2016 Cumulative Update (KB3176934 OS Build 14393.82). Devices that are domain-joined will not experience sync for the setting Date, Time, and Region: automatic time.

In this case, running “” in an elevated command prompt window, rebooting, and trying registration again may help with this issue.

Under certain conditions, Enterprise State Roaming can fail to sync data if Azure Multi-Factor Authentication is configured.

Recommended action Connect the device to a corporate network so that sync can resume. User Name instead of username) and the user is on an Azure AD Joined device which has upgraded from Windows 10 Build 10586 to 14393, the user's device may fail to sync.In Event Viewer under the Setting Sync-Azure logs, the Event ID 6013 with error 80070259 is frequently seen.Recommended action Make sure the Windows 10 v1607 client has the August 23, 2016 Cumulative Update (KB3176934 OS Build 14393.82). Devices that are domain-joined will not experience sync for the setting Date, Time, and Region: automatic time.In this case, running “” in an elevated command prompt window, rebooting, and trying registration again may help with this issue.Under certain conditions, Enterprise State Roaming can fail to sync data if Azure Multi-Factor Authentication is configured.Although not specific to Enterprise State Roaming, following the instructions below can help confirm that the Windows 10 Client is registered, and confirm thumbprint, Azure AD settings URL, NGC status, and other information.