Default Behavior for AppVolumes Drive Letter Assignments

AppVolumes Drive Letter Assignments

Question

What is the default behavior for AppVolumes drive letter assignments?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

A.

https://docs.vmware.com/en/VMware-App-Volumes/2.10/com.vmware.appvolumes.user.doc/GUID-1FBE80C8-37D2-4074-92C5-DE111FD2E2B3.html

In VMware Horizon 8.x, AppVolumes is a feature that allows for the management of applications and user profiles. AppVolumes uses a virtual disk (VMDK) format to store application files and configurations, which are then mounted on virtual desktops and presented to users as if they were installed locally.

When assigning drive letters to AppVolumes, there are different options that can be configured depending on the type of volume.

The correct answer to the question is C: for writable volumes the driver letter is not assigned, and for AppStack volumes the drive letter is hidden.

This means that writable volumes, which are used to store user-specific data and configurations, do not get a drive letter assigned by default. This is because writable volumes are designed to be transparent to the user and not visible in the file explorer. Instead, they are mounted at runtime and can be accessed through environment variables and folder redirection.

On the other hand, AppStack volumes, which contain application files and configurations, are assigned a drive letter by default. However, this drive letter is hidden from the user and not visible in the file explorer. This is because AppStack volumes are designed to be transparent to the user as well, and the applications they contain are presented as if they were installed locally on the virtual desktop.

It is also worth noting that the default behavior for AppVolumes drive letter assignments can be modified through the use of AppVolumes Manager, where administrators can configure settings such as drive letter assignments and visibility.