Just out of curiosity, is there anyone using it already? Or tested it thouroughly? Just interested in some real life out in the open test results.
Unfortenately I didn't have time to test it yet...
Started playing with Appvol 4
But using the appvolumes migration utility to migrate appvol 2.x to 4 is not working for us.
Clearly doing something wrong.
pdf link below
The New/updated userinterface is really cool and much faster loading times in my lab. Packaging also works like a charm.
Question for you did you convert your 2.x packages to 4.0 ??
also a big one you package up Visio etc that seems to be the pains
no, did a clean install of AV4.
Can you explain a bit more what is going wrong ?
Do you see error messages, if so can you please share them with me ?
Will this be supported, or will it be another 3.0?
Do not talk about version 3.0....
Sorry for the late reply
below error this is also posted to VMware flings
We have 133 app stacks and none convert to 4.0
Application Capture Command Line Program
8:33:47 Computer: Computer name
8:33:47 Date-Time: Tuesday, 28 January 2020 8:33:47
8:33:47 Commandline: C:\Program Files (x86)\vmware\appcapture\appcapture.exe
8:33:47 Arguments: /Migrate "Application name" /sourcepath "c:\Program Files (x86)\vmware\appcapture\Volumemount\Application name" /o C:\Appstack
8:33:47 INFO : Processing Commandline Options
8:33:47 INFO : application name: Name of application
8:33:47 INFO : Migration(Source) path: C:\Program Files (x86)\vmware\AppCapture\VolumeMount\Application-Name_appstacks
8:33:47 INFO : Output vhd folder: C:\Appstack
8:33:47 INFO : Source vhd: C:\Program Files (x86)\vmware\AppCapture\templates\wemcapture.vhd
8:33:47 INFO : source disk file attributes: 0x00000020
8:33:47 INFO : output vhd folder attributes: 0x00000010
8:33:47 INFO : output vhd file: C:\Appstack\Application.vhd
8:33:47 INFO : copying C:Program Files (x86)Vmware\Appcapture\templates\wemcapture.vhd to C:\Appstack]Application.vhd
8:33:47 INFO : Going to add Full Access for Authenticated users [icacls.exe “c:\Appstack\Application.vhd” /grant *S-1-5-11:(F)].
8:33:47 INFO : preparing output virtual disk for capture
8:33:47 INFO : attaching the migration disk
8:33:47 INFO : waiting for disk attachment
8:33:47 INFO : disk attachment complete in 0 secs
8:33:47 ERROR: failed to set volumelabel for virtual disk (error: 0x13)
8:33:47 ERROR: virtual disk attachment and mount failed [Error: 0x13]
8:33:47 ERROR: program failed in install mode CmdNew (Error: 0x13)
First off I haven't tried to convert appstacks from 2.18 to packages in 4.0.
We have some appstacks that have multiple applications in it, it seems to not be the best of ideas to migrate those.
Creating packages and applications in 4.0 is really straightforward and works qite nice.
Login times seems to be good with multiple packages attched so no issues there.
We do see an issue with packaging Java applications (in this case SPSS) as it seems to not be able to load jar files after sequencing is done. Also tested with 2.18 but it worked there.
Anyone else seen these issues with applications being packaged?
You logs mentioned vhd, are you using vhd by any chance? if so, apparently is it not supported according to the documentation.
"AppStack Migration Utility: App Volumes Migration Utility helps to migrate appstacks that are provisioned in 2.x environments to be deployed in 4.x App Volumes. This should be installed on a VM having access to the datastore having the appstacks to be migrated. Currently migration of VMDK based appstacks is only supported."
Believe it or not that was using only VMDK
the application does give you the ability to convert VHD tho
1 person found this helpful
We have been working wityh Appvolumes 4.0 for a few weeks now, all and all I am quite positive about the results.
Yes, we did package Visio en Project as a seperate appstack, even attached both as seperate appstacks and they all seem to work well.
Only application for us that doesn't work at the moment is SPSS, engineering is aware of it, my guess is that the next version will also fix this.
An update to App Volumes 4 has just been released to resolve a few critical issues:
- Chrome fails with the "Aw,Snap!" error occurs due to compatibility issues with Chrome version or 78 and later. 
- Silent installation or upgrade of App Volumes Agent requires the EnforceSSLCertificateValidation parameter be set to 0 or 1. 
- In some cases, the login process spans a few minutes until the user is able to utilize the desktop. 
See the VMware App Volumes 4 Update 1 Release Notes for details.