Application Deployment & Virtualization

Most of us that work with App-V will eventually need to put some of them inside a Connectiongroup (CG). That’s a pretty straightforward operation, until you deploy it for test, and it fails to install, giving you errors like: “The connection group {xxx} version {xxx} could not be published because the virtual COM settings of the individual packages conflict. Verify that the virtual COM settings are the same for all member packages and try again. Finally I had the time to put up our free tool from my previous article up on  github. Our powershell procjectfiles may not contain the latest changes, and some errors since my translation to English was done in a hurry using replace with in notepad++. But you will most likely get the drift, and the compiled working program is included in the msi . This tool is free, and based around the excellent work of the Tweakappv tool by Caphyon and 7 zip to extract files form the appv files. They are included in the msi file. So please r...

When we change registry information in an existing APPV package we usually do so manually in the Sequencer, Ave or TMEdit then save the new version. Afterwards we try to document that changed registry information and often forget some crucial information, making resequencing of the application later on harder than it should be. During the development of an internal APPV workflow application we have created around Tweakappv , TMEdit and AVE, we also wanted to document what has been done in each applications REGISTRY.DAT after the APPV file is saved in a new version automatically. The new and the old Registry.DAT file could be extracted automatically by 7zip command line version with this command: 7-Zip> 7z.exe x " filaname.appv " "registry.dat" –y (just ignore archive errors, the registryfile will work non the less=) But understanding the DAT files is not very easy. By coincidence I found a tool a clever guy have made in C# and pub...

Normally Ibm Spss have been   considered an easy application to sequence in the past. But after we Sequenced version 26 on 1809 I had a rundown with the following error message when I lunched the application on the client: App-V Subsystem 'Virtual Filesystem ' could not be initialized. {error: 0x74300E0A-0x20006}   Googling this got me down a rabbit hole of a lot of old App-V treads, but nothing could help me. The solution was actually pretty easy, throw away the 1809 sequencer and use the old 1709 sequencer. How to Sequence: The following cmd file will install your program. Just change LSHOST to your license server, and do the same to COMPANYNAME. Regsvr could be removed, it was a thing from the past, but it won’t do anything. echo Installing (1/3): Ibm Spss 26.x64 msiexec.exe / i "%~dp0IBM SPSS Statistics 26.msi" LICENSETYPE="Network" LSHOST="license.server.com" INSTALLPYTHON="1...