application

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

As all would have heard about the inbuilt App-V and Ue-V available with Windows 10 Anniversary update 1607 which has been released on August 2nd 2016.It is available only with the Windows Enterprise and Education editions. They will also be included in-box in Windows Server 2016 Standard and Datacenter. If you are using Windows 10 Professional or earlier and plan to upgrade to the Windows 10 Anniversary release, you will need to deploy the Enterprise edition to use App-V and UE-V on those devices. I have already blogged about this in my previous post when I tested App-V and Ue-V in windows 10 build 14316 and some common issues found. You can have a look here in the below link. http://app2pack.blogspot.com/2016/04/app-v-ue-v-available-by-default-in-new.html http://app2pack.blogspot.com/2016/04/windows-10-build-14327-enabling-or.html By default App-V and Ue-V are disabled in the OS. You need to enable it to use them. It can be done by enabling in services,GPO or using Powershell comm...

Recently I read an article from David Falkus as how to use WMI to list App-V applications published to the machine.You can use this method if not able to access Powershell and also this method can help in basic troubleshooting. I experimented this and it seems to be very useful. Below are the steps as how to use WMI to list published applications and connection groups. 1. Open Run and type wbemtest. 2. Select Connect button. 3. Enter root\appv and click connect. 4. Click Enum Instances. 5. Enter AppvClientPackage and click ok. Also you can use AppvClientConnectionGroup to list the published Connection Groups. 6. This will list the packages that are published to the machine. 7. When you double click the package it will list the properties of the package like InUse, PackageID, VersionID etc. 8. This method is similar to that of using Get-AppvClientPackage in Powershell.

Earlier in my previous blog I have mentioned that Enable-AppV, Disable-AppV, Enable-UeV, Disable-UeV commands in powershell doesn't show any success or failure result. http://app2pack.blogspot.in/2016/04/app-v-ue-v-available-by-default-in-new.html Recently Microsoft has released its windows 10 build 14327 insider preview release. So had a chance to test this case. when tested it shows the result that the App-V/Ue-V was successfully enabled/disabled. Finally there won't be any confusion whether the service is actually enabled or not. NOTE: Reboot will be required when enabling/disabling.

There was a huge expectation about the Project Centennial also famously known as Project C. I promise it will not disappoint any of you. I was very eager to have my hands on it and experiment it more and so here I am explaining the conversion steps in detail with a test desktop app. Prior to conversion one should know the advantages of converting desktop apps to UWP. To know more check the below link. https://msdn.microsoft.com/windows/uwp/porting/desktop-to-uwp-root Microsoft has released its pre-release version of Desktop App Converter tool which can be used to convert all the existing desktop apps written for .NET 4.6.1 or Win32 to the Universal Windows Platform (UWP). Desktop App Converter tool converts a desktop Windows installer such as MSI or EXE to an AppX package that can be deployed to a Windows 10 desktop. Requirements: 1. Windows 10 Build 10.0.14316.0 or higher(Should be installed physically. Converter will fail in a VM image) 2. Desktop App Converter ( Download - Her...