Application Deployment & Virtualization

Microsoft AppV 5 have been around the block for a long time and is still widely used by us and many organizations as the preferred virtual application delivery format, while we are waiting for MSIX to mature enough for us and developers to fully adapt to it. Our AppV strategy also applies to the way we deploy MS Office plug-ins in our company, we always strive to deliver them virtually if possible. Most of the time Office Add-ins work right out of the box by creating the AppV package with the “Add-on or Plug-in” choice in the Sequencer, as a pre requirement our main Office version must also first be installed locally on the Sequencing VM image. We standardize on the volume licensed version of Office 2019, but some users also have Microsoft 365 (formerly known as Office 365), both versions use C2R technology, and it seem to be much the same in terms of deployment to machines and Add-in integrations.     AppV and Office Add-ins have been working well si...

There's so many creative ways to make sure your Sequenced App-V applications always have a perfect launch when it starts up. This can often be done by loading the correct config data, and without having to do manual configurations and so avoiding error messages. Most of the time this can be put in the registry or a config file for the package, or scripted into the machine during the add or publishing phase with a run once event script. But sometimes this will not work, maybe because another process has to be started first, maybe because the application have a poorly designed license registration. We may first need to check if other processes are stopped or running fine before the virtual application starts up and can be licensed. One way is to create an “On process start” script for your applications .EXE file(s), this will be started before your main executable file is started. First thing you do in the Sequencer, check your “Shortcuts and FTAs” tab...