Good afternoon,
I'm facing an issue when using App Volumes User Profile Writable Volumes.
First some info on the environment
App Volumes 4 2006 (4.1.0.59)
Windows 10 Version 1909 (Build 18363.836)
Writable volume template: template_uia_plus_profile.vmdk
The issue:
User's first login on the machine works just fine.
From the second login onwards login fails with the following message: The User Profile Service service failed the sign-in. User profile cannot be loaded.
If the machine is rebooted the scenario repeats itself (first login ok, second and onwards fails).
Deleting/Disabling the Writable Volume makes the problem disappear.
Login fails either directly (RDP or VM console) or via Horizon Client.
Anyone has any hints on where to search for further info?
Thank you very much.
Hi,
Writeable Volumes are supported with persistent VMs but using the UIA template only. It would appear you are trying to use UIA + Profile as per your first post. This and the Profile Only templates are NOT supported with persistent virtual machines.
The following table is from:-
The table below shows the possible individual use cases for VMware App Volumes.
Assignment Type | Volume Type | Instant Clone | Linked clone | FullClone | RDSH | ||
Floating | Dedicated | Application | Desktop | ||||
with Delete or refresh machine on logoff | with Refresh OS disk after logoff | with Delete machine on logoff | |||||
User | AppStack | Yes | Yes | Yes | Yes | No | No |
Writable | Yes | Yes | Yes | Yes | No | No | |
Computer | AppStack | Yes | Yes | Yes | Yes | Yes | Yes |
Writable | Yes | No | Yes | Yes | Yes | Yes |
Legend = Yes - Supported Scenario.
Persistent Disk with AppStacks and Writable Volumes (UIA Only template) is supported.
Hope that helps.
Thanks
Andrew
I compared the successful login and the failed login event messages and I think I found the cause of the issue:
Successfull login (all below are svservice events):
Failed login (all below are svservice events):
And then it follows (User Profile Service events):
Therefore I came to the conclusion that the writable volume content is unaccesible due to wrong permissions.
Now to figure it out why and how to solve it.
I've done some further digging and noticed weird behaviours by comparing:
I compiled them in an Excel table (I attached it if anyone is willing to check it).
Therefore I'd like to ask something: Is App Volumes Writable Volumes (Profile) supposed to work on PERSISTENT desktops? Or only on non-persistent?
Thank you very much.
Hi,
Writeable Volumes are supported with persistent VMs but using the UIA template only. It would appear you are trying to use UIA + Profile as per your first post. This and the Profile Only templates are NOT supported with persistent virtual machines.
The following table is from:-
The table below shows the possible individual use cases for VMware App Volumes.
Assignment Type | Volume Type | Instant Clone | Linked clone | FullClone | RDSH | ||
Floating | Dedicated | Application | Desktop | ||||
with Delete or refresh machine on logoff | with Refresh OS disk after logoff | with Delete machine on logoff | |||||
User | AppStack | Yes | Yes | Yes | Yes | No | No |
Writable | Yes | Yes | Yes | Yes | No | No | |
Computer | AppStack | Yes | Yes | Yes | Yes | Yes | Yes |
Writable | Yes | No | Yes | Yes | Yes | Yes |
Legend = Yes - Supported Scenario.
Persistent Disk with AppStacks and Writable Volumes (UIA Only template) is supported.
Hope that helps.
Thanks
Andrew
I'd say that kind of explains it although the KB is not update for App Volumes 4.
It seems that whatever causes the issues on persistent desktops (no refresh) is solved by either refreshing it or just rebooting it.
Now to check what would be better to workaround it.
Thanks a lot Andrew for pointing that out.
No problem.
I imagine the Profile UIA template does not issue a "clean" dismount or registry release of NTUser.dat thus freeing up the OS for a successful logon for subsequent uses without a reboot hence the error messages you are seeing. I would imagine this could be fixed by VMware as other competitor products such as FSLogix and Liquidware ProfileDisk are able to handle these scenarios without issue.
Thanks
Andrew
Reread that KB
"Persistent Disk with AppStacks and Writable Volumes (UIA Only template) is supported.
this isn't saying persistent desktops are supported, its saying the persistent disk which is a feature.
Horizon Composer Persistent Disks
Persistent vms aren't supported with normal or any writeable template, The issue is with persistent vms you get stuff leftover, and you'll get conflicts.
Apologies, this was the reference I should have included:-
"You can understand how Writable Volumes can be used with VMware Dynamic Environment Manager, behavior of Writable Volumes in a non-persistent virtual desktop, how Writable Volumes are used in a shared datastore, and how to exclude specific locations of Writable Volumes from being overwritten."
There is no mention of persistent machines as they are indeed unsupported.