Welcome to my VMware App Volumes series. As it has been quite some time since I captured my InternetBrowsers Appstack, I will in this session update this Appstack. When I captured this, it was with Google Chrome 74.0.3729.121 and Firefox 66.0.3. These version will be upgraded and I will add another browser, Opera.
The first I do is to start my capture machine. I don’t login in at this point.
Next, I log into VMware App Volumes Manager, click Update on the AppStack I’m going to update, InternetBrowsers
I provide a name for the updated AppStack and make any needed changes to the storage or path location. Create…
Now that my new AppStack is ready for provisioning, I click Provision…
I search for my capture machine, W10APPCAPTURE, and click Provision…
The AppStack’s status is now changed to Provisioning
In vSphere I can verify that the AppStack is attached to my capture machine
When I log in to the capture vm, I will see the familiar provisioning prompt.
Now that I’m in provisioning mode, I upgrade Google Chrome, Mozilla Firefox and install the Opera browser. I launch all my browsers to verify functionality and reboot the capture vm. Once more I launch the browsers before I click OK in the capture prompt.
I revert to my latest snapshot and head over to the App Volumes Manager to proceed. My new AppStack is now ready for use, but before I assign it, I will update the description with version info. I click Edit and update the description.
At this time, I can delete the ParentAppstack, but before that, I have to unassign the current assignments.
As I chose to unassign at logout or reboot, I will have to reboot the desktops before I proceed
Now that there are zero Assignments and Attachments, I click Delete to remove the AppStack
This concludes my session about updating AppStacks. I have seen in some environments with 2.17, that the capture process doesn’t launch, if I log into the capture vm before I start the provisioning in App Volumes Manager. Although I can see that the vmdk is attached to the VM, the capture prompt doesn’t launch in Windows 10. If I log off and log in again, the capture prompt does launch…weird. I suspect that this is a little bug in 2.17 but haven’t found any other workaround except the one i mentioned above.
Disclaimer: Every tips/tricks/posting I have published here, is tried and tested in different it-solutions. It is not guaranteed to work everywhere, but is meant as a tip for other users out there. Remember, Google is your friend and don’t be afraid to steal with pride! Feel free to comment below as needed.