Concern around the latest Windows 10 Anniversary update 1607, has brought about numerous questions that James Rankin, the AppSense Bigot, seeks to answer in his blog series, "Everything you wanted to know about virtualizing, optimizing and managing Windows 10...but were afraid to ask."
In his recent edition, which focuses primarily on roaming, James states, "For the record, most Windows 10 settings roam fine, but the main one that we've all been struggling with is the Start Menu. And this is really annoying, because the Start Menu is the first thing that the user generally interacts with when they use a Windows 10 desktop, and possibly the most "in your face" part of the new OS features."
Since roaming profiles have incremental version numbers due to incompatibility, take a look at our Windows Profile Versions matrix in the docs section to see the breakdown of roaming profile versions per Windows OS (update patch and registry setting inclusive).
James lays out a decisive plan based upon the finicky nature of the Start Menu and defines clear metrics for testing and assigning grades of PASS or FAIL: "We will log on, customize the Start Menu by pinning a desktop application, a Modern App, a folder, a website, an RDP connection and changing the name of the groups. If these changes successfully persist when we log on to another device, then we will consider that the method in use is compatible with the latest version of Windows 10."
Below is a table of James' findings regarding user profile solutions on Windows 10 update 1607
|Profile Type||Windows 10 Update 1607|
|FSLogix Profile Container||PASS|
|AppSense Environment Manager||PASS|