App Volumes 2.11 Known Issues

App Volumes 2.11 Known Issues

  • 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 virtual machine.
  • Some machines appear offline in the App Volumes Manager after performing the Push Image operation on a large pool of instant clone desktops.
    Workaround: Restart the machines that appear offline, or restart the App Volumes service on these machines.
  • Windows Home Editions are not supported in this release.
    Workaround: None.
  • An Outlook search might generate a configuration popup when search indexing is enabled. 
    Workaround: Disable the Windows Search service and searching will work without search indexing.
  • Apple iTunes contained in an AppStack must be assigned prior to user login. Dynamic “real-time” assignment for this application is not supported.
    Workaround: None.
  • Use of Novell products with App Volumes can cause unexpected behavior. Novell products are not supported by VMware App Volumes.
    Workaround: None.
  • If a user logs in to a virtual desktop with a Writable Volume and a user later logs in without a Writable Volume, a pop-up appears. 
    Workaround: Refresh or reboot after

Leave a Reply

Your email address will not be published. Required fields are marked *