CVApps uses a temporary drive letter?

buijspa · ‎06-10-2017

Hi All,

We use the drive letter for our home drive (defined in AD under the user account properties).

We noticed that often (not always), only when we use the appvolumes disk, our drive is not mounted at logon.

I saw that the CVApps disk uses the drive letter (the first free letter during logon process) and, when the mounting process is finished, CVApps does not use this drive letter anymore :

It seems that there is a collision between the Appvolumes service using the drive (first available drive letter) temporarly and our Home Drive mounted during the logon process.

This is very annoying because our homedrive is not mounted when the logon process is finished ( ex : no folder redirection etc...).

Could you confirm this behaviour?

Is it a way to avoid this "collision"?

Thank you for your help!

buijspa

Ray_handels · ‎06-12-2017

It is a known issue with the appstack created by older version of the agent.

Apparently when logging in if not all appstacks are attached it seems as if Windows claims the disks and provides it with a drive letter.

eventually (if you are using 2.12.1) after 180 seconds Windows releaes the driveletter and Appvolumes agent processes the appstack.

There is a quie simple though pretty cumbersome solution to it.

You need to make sure that the appstacks (and yes, you need to update them all) have the NoDefaultDriveLetter setting enabled.

Following link is a how to.

Network drive letters are not mapped to VMware App Volumes AppStacks (2139351) | VMware KB