Roaming profiles not updating server 2016
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.
The use of profiles across different versions of OS is not supported by Microsoft and may cause undesirable behaviour.
It is therefore recommended that profiles covering different Operating Systems are maintained separately and not used across versions.
Also, I am not sure if it would affect profiles from already logged-on users.
I believe the only method to achieve what you want would be through scripting.
For workarounds, enable a delay before deleting the profile which may help to give whichever process is using NTUSER. Setting a value higher than 40 seconds is highly recommended.
Alternatively you could disable the deletion of cached profiles on logoff if you did not need it.
Or to put it differently: How can we ensure a specific user will receive a new, clean profile when he logs himself in the regkey, it is a per-machine configuration setting valid for all users logging on to your terminal servers, and thus probably undesirable.
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: Windows 10 v1709 (Fall Creators Update) did infact NOT present a V7 Windows Profile version. 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.
Links may also expire or change so if you find broken links, please again let me know.
For each issue, known product versions affected are recorded however that does not mean product versions that aren’t listed are not affected.
For example, machines running an OS that expect a v4 profile should not receive a v2 profile from Citrix Profile Management and so on.