App-V Application in AppVolumes

[Natestack]

Hi guys,

My department has invested alot of time and effort into App-V applications, we're slowly introducing AppVolumes VDI.

But cant justify in the short term repackaging all the applications from App-V to Thinapp/appvolumes.

So question is, can i still retain my current App-V applications untill we update them to Thinapp/AppVolumes ?

I would like to have them deployed via appVolumes if possible.

Thank you in advance

[Natestack]

Ok done some testing and seems snapvol.cfg already has the #exclusion for the App-V Root directory

C:\Programdata\App-V

Issue seems to be when you do an app stack it doesn’t save the contents that is deployed in the root directory.

Eg application root install contents are saved in c:\programdata\App-V. when you complete the app stack.

It seems when you attach the app stack the c:\programdata\App-V folder gets created but within App-V nothing and this is required for the application to run.

So really what I want is to save data to a location and have it saved in an app stack.

  I really don’t want to repackage 100+apps I would rather use what we have and gradually move across to thinapp

[Ray_handels]

What version of Appvolumes are you using? When using 4.6 you would need to create shared cache for Appvolumes. I believe that it is possible to use APPV withing Appvolumes but I would still suggest repackaging to save yourself the trouble of getting this to work. Also, going to ThinApp is a also a loss of time because my guess is that it will be replaced by Appvolumes. You cannot get support for office 2013 and 2016 with Thin app already.

As to the issue with the folder. Did you create it in the golden image, the folder? Exclusion from the Appvolumes agent as in the snapvol.cfg only makes sure the Appvolumes filter driver doesn't touch the info which makes it quicker but also doesn't register the info into a writable if you have one.

[Natestack]

We using appvolumes 2.13.1

Also App-V 5.1 seems this is not working at all so will be implementing App-V into the VDI solution till Appvolumes takes over.

i manually installed App-v application using power shell which places the application root in %programdata%\App-V there is creates in the folder and contents for some reason Appvolumes not Thinapp saves this. Sucks but short term pain for long term gain touchwood.

[Natestack · Accepted solution]

Got this sorted.

so the appv packages that gets installed copy the contents from the first guid.

create a folder direct in C:\ or in C:\program files or C:\program files (x86)

while doing a capture and this methord seems to work.

Remember to change the shortcuts from the current appv file path to the new location and all works well.