Problem You’ve completed an upgrade of VMware App Volumes Manager from 2.6.0.1226 to 2.12.0.70: … by uninstalling the old version then reinstalling the new version using the same database but notice that launching the Apps Volume Manager now display the following HTTP 500 Internal Server
I recently had to assist a client with licensing their VMware App Volumes software as the trial period was coming to an end and I noticed that the process was a bit confusing so I thought I’d write this short blog post in case someone
This post serves as a continuation of my previous post: Creating and AppStack with VMware App Volumes https://blog.terenceluk.com/2015/11/creating-and-appstack-with-vmware-app.html … mainly to demonstrate the process of updating an AppStack that has already been created. Step #1 – Select the AppStack that needs to be updated Begin
This post serves as a continuation of my previous post: Installing and performing initial configuration of VMware App Volumes Manager https://blog.terenceluk.com/2015/11/installing-and-performing-initial.html … to demonstrate how to create an AppStack once you have VMware App Volumes deployed in your environment. Prerequisites In order to create an
I’ve been fortunate enough to have a few clients interested in adopting VMware’s new App Volumes earlier this year and while I’ve had numerous issues with Microsoft Office or related applications, I’ve found it extremely for most other applications that have no dependency on Microsoft
Problem You have installed Office 2010 directly onto your base virtual machine master image then continue to create two separate AppStacks in VMware App Volumes. With the AppStacks created, you proceed with assigning Microsoft Project 2010 to a VMware Horizon View VDI but notice that
One of the most exciting products I’ve been working with recently has been VMware App Volumes as most of the clients I work with that currently use VMware Horizon View have a need for customizing their virtual desktops but do not want to additional overhead
