Henrique_Cicuto
Enthusiast
Enthusiast

Windows 10 User Profile Service and App Volumes Profile Writable Volume

Jump to solution

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.

0 Kudos
1 Solution

Accepted Solutions
alienjoker
Enthusiast
Enthusiast

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:-

VMware Knowledge Base

The table below shows the possible individual use cases for VMware App Volumes.

Assignment
Type
Volume TypeInstant CloneLinked cloneFullCloneRDSH
FloatingDedicatedApplicationDesktop
with Delete or refresh machine on logoffwith Refresh OS disk after logoffwith Delete machine on logoff
UserAppStackYesYesYesYesNoNo
WritableYesYesYesYesNoNo
ComputerAppStackYesYesYesYesYesYes
Writable    YesNoYesYesYesYes

Legend = Yes - Supported Scenario.

Persistent Disk with AppStacks and Writable Volumes (UIA Only template) is supported.

Hope that helps.

Thanks

Andrew

View solution in original post

0 Kudos
7 Replies
Henrique_Cicuto
Enthusiast
Enthusiast

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):

  1. Session ID: 1
  2. Manager: <appvolmgrfqdn>, Status: 200 Response (488 bytes): *1*#1#LOGIN <domain\user> MOUNTED-WRITE;vsanDatastore\appvolumes\writables\<domain>!5C!<user>.vmdk;{3b8eee5c-9d57-4463-af26-355fa89a59af} ASYNC WRITABLE-REBOOT;Volumes were not mounted due to an issue with your Writable Volume. Please try logging in again, or contact your administrator. SET-VAR;WRITABLE_FAILURE_ACTION;REBOOT SET-VAR;WRITABLE_FAILURE_MESSAGE;Volumes were not mounted due to an issue with your Writable Volume. Please try logging in again, or contact your administrator.
  3. Action: mounted Path: \Device\HarddiskVolume3 GUID: {471C5721-0000-0000-0000-100000000000} VolumeId: {3B8EEE5C-9D57-4463-AF26-355FA89A59AF}
  4. Manager: <appvolmgrfqdn>, Status: 200 Response (2 bytes): No
  5. Action: mounted Path: \Device\HarddiskVolume3 GUID: {471C5721-0000-0000-0000-100000000000} VolumeID: {3B8EEE5C-9D57-4463-AF26-355FA89A59AF}
  6. Event: [prestartup] Volume Path: [\SnapVolumesTemp\MountPoints\{471C5721-0000-0000-0000-100000000000}\]
  7. Path: C:\PROGRA~2\CLOUDV~1\Agent\Config\Default\UIA_PL~1\PRESTA~1.BAT WaitMilliseconds: -1
  8. Path: C:\PROGRA~2\CLOUDV~1\Agent\Config\Default\UIA_PL~1\PRESTA~1.BAT WaitStatus: 0, ExitCode: 0
  9. Event: [startup] Volume Path: [\SnapVolumesTemp\MountPoints\{471C5721-0000-0000-0000-100000000000}\]
  10. Path: C:\PROGRA~2\CLOUDV~1\Agent\Config\Default\UIA_PL~1\startup.bat WaitMilliseconds: -1
  11. Path: C:\PROGRA~2\CLOUDV~1\Agent\Config\Default\UIA_PL~1\startup.bat WaitStatus: 0, ExitCode: 0
  12. Path: \Device\HarddiskVolume3 GUID: {471C5721-0000-0000-0000-100000000000} SystemVolume: 0)
  13. Installing fonts Event: windows_install_fonts Path: \SnapVolumesTemp\MountPoints\{471C5721-0000-0000-0000-100000000000}\
  14. Refreshing desktop
  15. Session ID: 1
  16. Path: C:\Program Files (x86)\CloudVolumes\Agent\svservice.exe deskmon 1 WaitMilliseconds: 0
  17. Event: [shellstart] Volume Path: [\SnapVolumesTemp\MountPoints\{471C5721-0000-0000-0000-100000000000}\]
  18. Path: C:\PROGRA~2\CLOUDV~1\Agent\Config\Default\UIA_PL~1\SHELLS~1.BAT WaitMilliseconds: -1
  19. Path: C:\PROGRA~2\CLOUDV~1\Agent\Config\Default\UIA_PL~1\SHELLS~1.BAT WaitStatus: 0, ExitCode: 0
  20. Checking provisioning state Event: appcapture Path: \SnapVolumesTemp\MountPoints\{471C5721-0000-0000-0000-100000000000}\

Failed login (all below are svservice events):

  1. Session ID: 2
  2. Manager: <appvolmgrfqdn>, Status: 200 Response (488 bytes): *1*#1#LOGIN <domain\user> MOUNTED-WRITE;vsanDatastore\appvolumes\writables\<domain>!5C!<user>.vmdk;{3b8eee5c-9d57-4463-af26-355fa89a59af} ASYNC WRITABLE-REBOOT;Volumes were not mounted due to an issue with your Writable Volume. Please try logging in again, or contact your administrator. SET-VAR;WRITABLE_FAILURE_ACTION;REBOOT SET-VAR;WRITABLE_FAILURE_MESSAGE;Volumes were not mounted due to an issue with your Writable Volume. Please try logging in again, or contact your administrator.
  3. Action: mounted Path: \Device\HarddiskVolume4 GUID: {471C5721-0000-0000-0000-100000000000} VolumeId: {3B8EEE5C-9D57-4463-AF26-355FA89A59AF}
  4. Action: mounted Path: \Device\HarddiskVolume4 GUID: {471C5721-0000-0000-0000-100000000000} VolumeId: {3B8EEE5C-9D57-4463-AF26-355FA89A59AF}
  5. Event: [prestartup] Volume Path: [\SnapVolumesTemp\MountPoints\{471C5721-0000-0000-0000-100000000000}\]
  6. Path: C:\PROGRA~2\CLOUDV~1\Agent\Config\Default\UIA_PL~1\PRESTA~1.BAT WaitMilliseconds: -1
  7. Path: C:\PROGRA~2\CLOUDV~1\Agent\Config\Default\UIA_PL~1\PRESTA~1.BAT WaitStatus: 0, ExitCode: 0
  8. Event: [startup] Volume Path: [\SnapVolumesTemp\MountPoints\{471C5721-0000-0000-0000-100000000000}\]
  9. Path: C:\PROGRA~2\CLOUDV~1\Agent\Config\Default\UIA_PL~1\startup.bat WaitMilliseconds: -1
  10. Path: C:\PROGRA~2\CLOUDV~1\Agent\Config\Default\UIA_PL~1\startup.bat WaitStatus: 0, ExitCode: 0
  11. Path: \Device\HarddiskVolume4 GUID: {471C5721-0000-0000-0000-100000000000} SystemVolume: 0)
  12. Installing fonts Event: windows_install_fonts Path: \SnapVolumesTemp\MountPoints\{471C5721-0000-0000-0000-100000000000}\
  13. Refreshing desktop

And then it follows (User Profile Service events):

  1. Access is denied. C:\Users\<user>\ntuser.dat
  2. Access is denied
  3. The system cannot find the file specified

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.

0 Kudos
Henrique_Cicuto
Enthusiast
Enthusiast

I've done some further digging and noticed weird behaviours by comparing:

  • Event viewer entries when login successful VS Event viewer entries when login fails;
  • App Volumes log when login successful VS App Volumes log when login fails.

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.

0 Kudos
alienjoker
Enthusiast
Enthusiast

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:-

VMware Knowledge Base

The table below shows the possible individual use cases for VMware App Volumes.

Assignment
Type
Volume TypeInstant CloneLinked cloneFullCloneRDSH
FloatingDedicatedApplicationDesktop
with Delete or refresh machine on logoffwith Refresh OS disk after logoffwith Delete machine on logoff
UserAppStackYesYesYesYesNoNo
WritableYesYesYesYesNoNo
ComputerAppStackYesYesYesYesYesYes
Writable    YesNoYesYesYesYes

Legend = Yes - Supported Scenario.

Persistent Disk with AppStacks and Writable Volumes (UIA Only template) is supported.

Hope that helps.

Thanks

Andrew

0 Kudos
Henrique_Cicuto
Enthusiast
Enthusiast

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.

0 Kudos
alienjoker
Enthusiast
Enthusiast

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

0 Kudos
sjesse
Leadership
Leadership

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.

0 Kudos
alienjoker
Enthusiast
Enthusiast

Apologies, this was the reference I should have included:-

Features of Writable Volumes

"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.

0 Kudos