Application Deployment & Virtualization

Backstory: If you work with APPV you probably used the ability to connect several APPV packages with a Connection Group (CG). We all know it’s time consuming when there is conflicting advanced COM and isolation settings between packages already produced since they all need the same settings to work in a CG. First you have to open all packages, and then you have to see what’s different before you can make the same adjustment to all the needed packages, it takes time and it easy to forget something. What we wanted to do: So I have been working on an idea of developing a small  in-house PowerShell tool based on the fine work and ideas of Advanced Installers “ tweakappv ”with a colleague.   Tweakappv works basically like a small APPV api, so if you can crack the commands and syntax you can basically edit everything in one or more packages without doing manual editing. What we managed to do: Using a lot of time on trial and error we did manage to ch...

Backstory: If you work with a company that have several different locations/divisions and sub company’s, but they all use the same programs and versions but with different configurations, how do you manage to make only one APPV package for that scenario? The answer is dynamic package scripting, there may be other and maybe better ways to do this, but I will share my own method so you can compare and maybe get some new ideas. Prerequirements : For the concept of my method to work your first pre-requirement for this scenario is to tag all your computers with at least one unique location environment variable. Today we use a script that looks into the computer OU in AD for this but you can also make this from your pcname   if it reflects location. Unique pc-names can be set during imaging. Naming convention on our computers consist of the company short name and a location short name, and a unique running number (company-location-12345). Our Location and co...