Browsed by
Category: App Volumes

Assigning Drive Letter to AppStacks and Writable Volumes Doesn’t Work

Assigning Drive Letter to AppStacks and Writable Volumes Doesn’t Work

Comments 1 comment

Assigning drive letter to the AppStack/s or Writable volume fix few of the known issues. As example, assiging drive letter to Writable Volume fix the issue for Chrome extension. It also fix the issue with Microsoft OneDrive Syncing folder creation issue. The registry tweak VMware provided for the drive letter is not just assiging letters but also for hide those. The registry setting in HKLM\SYSTEM\CurrentControlSet\services\svdriver\Parameters, the parameter is called “DriveLetterSettings”. It’s a REG_DWORD key. By default this parameter is not…

Read More Read More

“Your OneDrive folder can’t be created in the location you selected” with VMware App Volumes Writable Volume

“Your OneDrive folder can’t be created in the location you selected” with VMware App Volumes Writable Volume

Comments 1 comment

In non-persistent environment with VMware App Volumes Writable Volume (or similar product), OneDrive fails to get configure Sync folder and through an error says “Your OneDrive folder can’t be created in the location you selected”. There are few ways to fix the issue. The first one is to assign a drive letter to the Writable Volume to fix it. But this is not the solution that everybody prefers due to security reasons. The end user can explore the drive, even…

Read More Read More

VMware App Volumes – Redirect HTTP to HTTPS

VMware App Volumes – Redirect HTTP to HTTPS

Comments 0 Comment

VMware App Volumes communicate throughhttp and https protocol. Since, http sends data in clear text, people like to use https protocol. There are number of VMware KB those describe about how to configure systems for https communication. One of the VMware KBs number 2095972 mentioned how to disable port 80 (http) from manager. But disabling http port give a nasty error 403 /404, while user try to access using http protocol. To make it look better to users, it is…

Read More Read More

App Volumes 2.10 “NTLM Authentication failed for: Domain\user. Virtualization is disabled” (error code 401)

App Volumes 2.10 “NTLM Authentication failed for: Domain\user. Virtualization is disabled” (error code 401)

Comments 2 comments

VMware introduce NTLM authentication on App Volumes v2.10. It is used to verify the user, computer, and the domain of the agent when it makes HTTP requests to the App Volumes Manager. Unfortunately, this NTLM authentication method causing random Authentication failure when App Volumes Agent trying to communicate to Manager. It generally shows the error message – Error: App Volumes Message Error from Manager <dns name> (error code 401): NTLM Authentication failed for: <Domain\user> Virtualization is disabled Solution: Disabling NTLM…

Read More Read More

App Volumes 2.11 Known Issues

App Volumes 2.11 Known Issues

Comments 0 Comment

AppStacks and Writable Volumes fail to attach on instant clone agents if the Data center name and virtual machine folder locations have non-English characters.Workaround: Change the Data center name and the virtual machine folder name to English. The Windows Search menu fails to launch with AppStacks on Windows 10 machines. BSOD occurs on 1 desktop during logon in a pool of 2000 desktops when AppStacks and a Writable Volume are attached.Workaround: Restart the machine or perform a delete operation to reprovision the…

Read More Read More