trim enabler volume not writable or low on space

Trim enabler volume not writable or low on space install#
Trim enabler volume not writable or low on space upgrade#

User logs in (2nd login), we see in vCenter that the writable volume and appstacks are being attached, but the VDI itself displays the message 'Please wait for the App Volumes Service' and the logon process does not finish.

User logs out, the appstacks and writable volume are being detached and the desktop is being refreshedĤ.

Trim enabler volume not writable or low on space install#

User logs in (1st login), the writable volume is created and the user can work and install his own applicationsģ. We create a writable volume (UIA only) for an AD user (or to an AD group where the AD user is member of)Ģ. There are no specific firewall settings in place.ġ. We did already install the MS 255978 hotfix you are mentioning. Now the appstacks are getting detached after logoff (but it takes still +/- 2 min to do this). We tried now with refreshing the desktop instead of deleting at logoff. I see in the vSphere client that a couple of seconds after the writable volume and the appstacks are being attached, the VMware tools stop running. I noticed in the log files that Appvolumes can not reach the VDI by it's IP address.

Log files from both App Volumes Managers are attached. I did however re-import the 2.9 templates for writables and appstacks

Trim enabler volume not writable or low on space upgrade#

The App Volumes environment is an upgrade from version 2.7. After this, the appstacks and writable volume are detached automatically when a usr logs out, but when the same user logs again in to Horizon View, he gets assigned a VDI from the linked clone pool, writable volume (UIA_ONLY) and other appstacks are being attached to the assigned VDI, but the VDI itself displays the message 'Please wait for the App Volumes Service' and the logon process does not finish. The View policy for 'Delete or refresh machine on logoff' is 'Delete Immediately'Īs a test, I chanegd the View policy for 'Automatically logoff after disconnect' to 'Immediately'. The View policy for 'Automatically logoff after disconnect' is 'after 120 minutes' The reason why I detach and delete the appstacks and writable volumes manually is because I do not have any other choice as the VDI just sits there and waits forever.

This situation only occurs when users are assigned a writable volume and does not occur when users are assigned only appstacks.Įnabling or disabling the option 'Prevent user login if writable is in use on another computer' does not have any effect on resolving the problem. When the same user logs again in to Horizon View, he gets assigned a VDI from the linked clone pool, writable volume (UIA_ONLY) and other appstacks are being attached to the assigned VDI, but the VDI itself displays the message 'Please wait for the App Volumes Service' and the logon process does not finish. I then detach the appstacks and writable volume manually (via the vSphere client) and delete the desktop.

When the user logs out of the VDI, the writable volume and appstack volumes are not being detached automatically. When I assign a writable volume to a user and the user logs in to Horizon View, the user gets assigned a VDI from the pool, the writable volume and other appstacks are being attached to the assigned VD, the logon occurs and the user can install applications. User profiles are being handled by Persona Management. Users can install applications through Appvolumes writable volumes ((UIA_ONLY) I have an environment with VMware View 6.1.1 linked clones and appvolumes 2.9.Īpplications are delivered through Appvolumes appstacks