application

In my previous blog I had posted about a simple registry tweak to publish packages globally/User by just right clicking and selecting the option. But in that method, it will not use the dynamic configuration file. And so I have covered how to do that in this blog. copy the below code in notepad and save it in .reg format. After saving, double click on it and register the keys. Windows Registry Editor Version 5.00 [ HKEY_CLASSES_ROOT \.appv] @ = "appvex" [ HKEY_CLASSES_ROOT \appvex] [ HKEY_CLASSES_ROOT \appvex\shell] [ HKEY_CLASSES_ROOT \appvex\shell\Publish Globally] @ = "&Publish Globally" [ HKEY_CLASSES_ROOT \appvex\shell\Publish Globally\command] @ = "cmd /c start /b /wait powershell.exe -nologo -ExecutionPolicy bypass -file \"c:\\Publish globally.ps1\" \"%1\"" [ HKEY_CLASSES_ROOT \appvex\shell\Publish to User] @ = "Publish to &User" [ HKEY_CLASSES_ROOT \appvex\shell\Publish to User\command] @ = "cmd /c start /...

I always wanted a simple trick to install the App-V virtual packages in a single click without any need to open powershell and type commands in a standalone machine. I have worked on many software's and  used to see some of them provide context menu shortcut (notepad++, winzip etc..) So I had an idea to create a simple registry tweak to publish the virtual packages either globally or to a user by just right clicking a .appv file using context menu option. Copy the below code and save it in a notepad with .reg extension. Double click and register it. Windows Registry Editor Version 5.00 [ HKEY_CLASSES_ROOT \.appv] @ = "appvex" [ HKEY_CLASSES_ROOT \appvex] [ HKEY_CLASSES_ROOT \appvex\shell] [ HKEY_CLASSES_ROOT \appvex\shell\Publish Globally] @ = "&Publish Globally" [ HKEY_CLASSES_ROOT \appvex\shell\Publish Globally\command] @ = "cmd /c start /b /wait powershell.exe -nologo -ExecutionPolicy bypass -command \"& {add-appvclientpackage '%1' ...

Earlier when trying to install the Advanced Installer created virtual package through MSI format in windows 10 anniversary update 1607, it failed to install with the below error. This issue is caused because of a launch condition in MSI which has been set to check for App-V client installed as a pre-requisite. Since App-V comes inbox with windows 10 v1607, the pre-req check fails with the above error. This was a known issue even with App-V created packages and it was reported back to Microsoft. Meantime I had a chance to talk with the Advanced Installer team about this issue. They quickly reported that they will look into this issue ASAP and come back with a fix. To my wonder they released an update within a short time period. You can have a look on their release note about this bug fix. http://www.advancedinstaller.com/release-13.3.html Now using Advanced Installer 13.3 when you create a virtual package and use the MSI to install in windows 10 1607, it installs fine witho...

If you want to change the Package Version or VersionID, you can do it by exporting the AppxManifest.xml file from App-v 5.1 sequencer and do the changes. But after importing it back and saving the package, those values changes to some other random values. The version also gets incremented. So how to set them to a predefined value? Advanced Installer has released a free tool called Tweakappv. It can be downloaded from the below link.It makes things so easy that you can also do a batch conversion for bulk packages. http://www.advancedinstaller.com/appv-automation.html Change Version: Follow the below command to change the version value to a predefined value. You can note that after publishing the version has been changed to the value 4.0.0.6 which we had set using Tweakappv. Change VersionID: Follow the below command to change the VersionID to a predefined value. Change PackageID: Follow the below command to change the PackageID to a predefined value. NOTE - The value you provide for...

Recently I came across an issue in TechNet which was quite interesting. Issue: I was able to publish two Mozilla Firefox (41.0, 49.0) to a client machine. I've added Desktop Icons with the respective version on it to differentiate one from the other. If I open them individually, not keeping both opened, I can confirm the version of the browser checking the Help otpion, however if I open one browser say 41.0, keep it opened, then open the second browser version 49.0 , the first browser version 41.0 will take precedensce on the second instance too.This can be checked by opening up help and checking the version. The second window showed 41.0 version even though it was 49.0 version firefox shortcut. https://social.technet.microsoft.com/Forums/en-US/c364b975-a2e4-425f-8d4c-88fdc7550599/having-two-mozilla-firefox-versions-from-appv-published-to-a-computer-if-i-open-both-versions-one?forum=mdopappv&prof=required Solution: Edit the dynamic config file and add the below -no-remote in th...

We see that the solution provided in the link from Microsoft for the msi (sequenced with App-V 5.1 or earlier) failure in windows 10 v1607 doesn't seem to fix the issue. https://technet.microsoft.com/en-us/itpro/windows/manage/appv-release-notes-for-appv-for-windows We see the below Msidb.exe not found error running the command as said in the link. When checked for Msidb.exe, it was found in c:\program files(x86)\windows kits\10\bin. Changed the -msidbpath to c:\program files(x86)\windows kits\10\bin and tested. It fails too. Changed it to c:\program files(x86)\windows kits\10\bin\msidb.exe. It fails too. The update-AppvMsiPackage.ps1 from C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\Sequencer seems to look for the location c:\program files(x86)\windows kits\10\bin\msidb.exe which is not located after installing the windows 10 sdk. The actual path where the msidb.exe is located after installing windows 10 sdk is c:\program files(x86)\windows kits\10\b...

When trying to install App-V 5.1 and earlier version of sequencer in windows 10 version 1607, it fails with the below error. Solution: You would need to download the latest SDK for windows 10 version 1607 which has sequencer along with it. Using this sequencer you can proceed virtualizing apps. https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit