Microsoft Windows Enterprise State Roaming - First Thoughts

Microsoft just announced a new service called Enterprise State Roaming. The broader goal seems to be to replace roaming user profiles. That, however, is not going to happen any time soon.

What We Know

Here is the link to the announcement.

Requirements

An Azure Active Directory Premium subscription is required.

In addition to that Enterprise State Roaming only works with Windows 10 build 1511 (or newer) when joined to an Azure AD.

Caveats

  • Enterprise State Roaming is designed to store app settings (not data!) in Azure
  • Enterprise State Roaming only syncs settings from “modern” and “universal” apps, not Win32 apps. This means that settings from 99.99% of all applications are not roamed.
  • Enterprise State Roaming operates asynchronously, ie. settings become available locally some time after the user has logged on.

Comments

Related Posts

Error Message Explained: User Profile Service Failed the Logon

Error Message Explained: User Profile Service Failed the Logon
This article is part of Helge’s Profile Toolkit, a set of posts explaining the knowledge and tools required to tame Windows user profiles. Many errors related to user profiles result in the user getting a temporary profile instead of the regular local or roaming profile. I have written about possible causes for that here. In addition to that, there is an entirely different category of errors that occur when even a temporary profile cannot be created. This article describes likely causes.
User Profiles