During the last couple of years I have seen that managing user profiles in a Citrix environment can be a major PITA. However before going any further, let’s take a few steps back in time.
In the good old days in the world of Citrix, with Windows Server 2008 R2 and Windows 7, everything was nice and quite in the user profile area. We were happily rolling along with Citrix User Profile Manager, telling ourselves that the old, dusty and rather unstable Windows Roaming Profile was a thing of the past and no one would ever be using that again. We were managing User Profiles like a boss, with fine tuned configurations preventing profile bloating, roaming of Internet Explorer cookies and passwords and perhaps roaming different files and folders outside the APPDATA\Roaming folder.
Fast forward to today, or a couple of years ago, Microsoft released Windows 10 and Windows Server 2016 and with them new Windows Profile versions.
Let’s have a quick look at the different Windows Profile versions dating back to Windows XP and Windows Server 2003:
UPDATE – 04/11-17: I have updated the table below to reflect the current Windows 10 versions.
|Client Operating System||Server Operating System||Operating System Version||Profile Version/extension|
|Windows XP||Windows Server 2003/2003 R2||None|
|Windows Vista||Windows Server 2008||V2|
|Windows 7||Windows Server 2008 R2||V2|
|Windows 8||Windows Server 2012||V3|
|Windows 8.1||Windows Server 2012 R2||V4|
|Windows 10||V1511 (November Update)||V5|
|Windows 10||Windows Server 2016||V1607 (Anniversary Update)||V6|
|Windows 10||V1703 (Creators Update||V6|
|Windows 10||V1709 (Fall Creators Update)||V6|
You may have noticed that Windows 10 is currently offering 2 different Windows Profile versions, V5 and V6,
and rumors are that the Windows 10 Fall Creators Update may present a V7 Windows Profile. This is where the struggle begins!
UPDATE – 04/11-17: Windows 10 v1709 (Fall Creators Update) did infact NOT present a V7 Windows Profile version. V1709 is still on V6, like v1703 and v1607.
As per this “Windows as a service” guide Windows 10 will receive 2 feature updates per year, a feature update is like the Anniversary Update or the Creators Update and even though Microsoft is boasting of an “outstanding app compatibility”, this isn’t really of much use to us, if they change the profile version. A profile version change will initially trigger a new profile to be created at login which means that we need to do some kind of profile migration between the old profile and the new profile, unless we really like to receive a lot of support calls about missing application settings or that no default printer is set, because something went wrong during the profile version upgrade.
If we are using Citrix Profile Manager this profile version upgrade is handled automatically, however do wo really want to do that? If we shortly revisit the good old times, we didn’t upgrade the user profiles when we migrated from Windows XP to Windows 7 or from Windows 7 to Windows 8 or Windows 10, did we? I sure didn’t and when is comes to traditional profile management I always recommend to do a profile migration NOT an upgrade!
In the good old times, a profile upgrade was always associated with a operating system upgrade. So when we are offered, at the moment, 2 different windows profile versions i Windows 10, in my mind that is the equivalent of an operating system upgrade, which means that the profile needs to be migrated as the functionality and stability of the profile cannot be guaranteed, if it’s upgraded.
In a Windows 10 VDI scenario this presents us with a couple of things to keep in mind. As per above guide, each feature update is maintained with so called quality updates every 18 months, so at least once every 18 months we need to upgrade our Windows 10 VDIs with a feature update. Let’s just assume, and I am NOT saying that this will be the case, but let’s just assume that Microsoft will upgrade the windows profile version every 18 months, this may not be a desirable scenario, as we need to maintain some kind of profile migration feature/script to be able to migrate the settings from the old profile to the new profile with the new version.
Some Citrix setups offer hundreds of different applications where all kinds of settings are saved in all kinds of places eg. files/folders/registry, this means that a potential migration feature/script needs to cover whether the settings of one or more applications needs to be migrated or not in case of a profile version upgrade. As applications come and go or gets upgraded these different places where applications might save their settings, will have to be maintained in what ever migration feature used, which then again means that we need to have a great deal of knowledge of our applications, not just how to install them, but also how and where their settings are saved.
Let’s take a look at how Citrix User Profile Manager can help us, some of the way, when upgrading Windows 10.
This is how a Citrix UPM share looks like, when a user has logged on from a Windows 10 v1511, Windows 10 v1607 and Windows 10 v1703:
This is achieved with the “Path to user store” in a Citrix UPM GPO configured like this:
The !CTX_OSNAME! and the !CTX_OSBITNESS! are both variables that can be used as a part of the profile share path. When these variables are combined you get a very flexible profile share path where a folder is created that corresponds to the operating system and the bitness of the operating system. This means that you would usually never need more than one profile share, when using Citrix User Profile Manager.
This configuration makes sure that a new profile is created when logging on to an upgraded Windows 10 computer with a new windows profile version.
You can omit the !CTX_OSNAME! and the !CTX_OSBITNESS! and point directly at the #SAMAccountName# variable, however this will create a profile folder for the user in the root of the share, which means that you will no longer have a folder named “Win10RS2x64”. If this is the case you now have a profile share that is “locked” to this specific version of Windows 10, that’s not wrong but it may present some issue at some point, as we essentially don’t want Windows or Citrix UPM to do profile upgrades.
One way or another we are in need of some way to transfer and/or migrate settings between different profile versions. You can of course bring out the big guns and go with RES or AppSense as they are perfectly capable of migrating profile and applications settings between different profile versions with their User Environment Management (UEM) solutions.
Liquidware is, compared to RES and AppSense, a smaller player in this area, however they have in their ProfileUnity product a way to migrate profile and application settings between different Windows versions and that of course includes Windows 10 as well. They also have disk based profiles, which really boosts the login performance.
You can of course also create your own profile and applications migration script, I have seen a few so I know they are out there.
To conclude – With Windows 10 we are, in my opinion, entering a new ara where we are basically doing operating system upgrades once every 12-18 months, this adds a bunch of additional tasks to our already long list of Citrix and Citrix related tasks. I think now would be a great time to implement some kind of UEM feature, to be able to manage and maintain the profile and applications settings in different user profile on different operating systems. Citrix User Profile Manager is, in my opinion, now considered the “old solution” together with the traditionel Windows Roaming Profile.