Topic Name : Upgrading App Volumes Components
Publication Name : VMware App Volumes Installation Guide
Product/Version : VMware App Volumes/2.13
Does the AppVolumes Manager and Agent Version have to match? Can the AppVolumes Manager be upgraded without upgrading the client?
Yes it can. I believe that I read somewhere that versions are backwards compatible but I's say use a bit of common scense on that one.
I would always suggest to keep the version in sync and only use different version between upgrade paths but we are now running manager 2.14.2 and agent 2.13 so it is also proven within production environments ..
I would also not suggest using an agent version 2.6 (or something in that order) and manager 2.14. Try to keep the gap between agent an manager as close as possible.
Thank You Ray,
We are currently on Manager 2.14 with Agent 220.127.116.11, I have just been looking for some documentation to confirm before I updated. We are experiencing some of the known issues that seem to be resolved in 2.14.2 and I would like to make sure of this prior to updating as we have a limited schedule for outages.
AFAIK that is just fully supported because you are in the same version of the product, just another patch level.
Trying to find a definitive answer on that one is quite hard. If you do want to have written confirmation I would suggest just raising a ticket with support. Normally they do respond pretty quick and than you at least have confirmation for management ..
Hi Ray, we installed a new manager 18.104.22.168 (import all existing appstacks) and have issues using AV2.14 client in Windows 10 (1803) with a set of four appstacks after login all appstack driveletter are showing in explorer and after a while a messagebox appairs 'time out blabla'. Any suggestions?
What version is the template you are using?
There used to be an issue with the older version of the appstacks that they had a drive letter assigned in the template, you can edit the template appstack by attaching it to a machine without Appvolumes agent and do the following.
Run diskpart and select the appstack volume then run the following command
attributes volume set nodefaultdriveletter
You can check it it worked by typing in the command attribte volume.
The value for No Default Drive Letter should be Yes.
Also, you could try looking at this registry setting, it will force hide the appstack driveletter for you (does not always seem to work 100% though).
The AV machine manager config 'Mount Queue' seems the issue. After deselect the default values appstacks successfullly attached without the time-out delay message (180 sec delay in client log).
Yes, that is indeed an issue, but still. If an appstack takes too long to be attached and the logon process is already executed (this is mostly an issue with W7 because login times in W10 are.. How do I say this, not very quick ) you will still see a driveletter being attached to your appstack.
Normally you will receive a message stating that Appvolumes virtualization is disabled but it still works. Just use the HidePopup registry key.
Also, to remove that driveletter option I would still suggest setting the nodefaultdriveletter setting with your appstack template disk.