application

Microsoft has released a windows Installer MSI for Microsoft Teams for deployment through SCCM.You can download it here As per Microsoft Statement: "The Teams MSI will place an installer in Program Files. Whenever a user signs into a new Windows User Profile, the installer will be launched and a copy of Teams application will be installed in that user's appdata folder. If a user already has the Teams app installed in the appdata folder, the MSI installer will skip the process for that user." NOTE: Don't change the install location as it will break the process. In this blog, I will explain how this happens by opening MSI using Installshield. 1. To Install Microsoft Teams, it first requires .net 4.5 or later to be installed in the machine. This check happens using Launch condition which also does a system search for .net registry to be present in the machine. 2. The MSI has only one file which is Teams.exe that gets installed to [ProgramFilesFolder]Teams Installer locat...

Earlier back in 2016 when Microsoft released Project centennail, I have blogged about it which you can find here To know more about Desktop bridge and UWP conversion have a look here Recently Advanced Installer has released a free express edition which is a GUI based tool to simplify the process of converting legacy exe/msi to appx format.They have also stated to support the new MSIX format in their upcoming release. You can download the free  Advanced Installer express version here . Pre-Req: Install windows sdk from here  After downloading install the windows sdk first and then install  the Advanced Installer express edition in a clean virtual machine.After Installing you will be prompted to register using your mail ID to get the free license .After validating click on new and select the Convert Desktop App as shown below and click next. Provide the setup path (msi/exe) and add any parameters if you wish to add.In this example I have used google chrome msi package to...

After publishing the App-V sequenced TortoiseSVN, all the context menu shortcuts are visible and it works fine. Only the background context menu option is not visible. In this blog, I will demonstrate and provide a solution for it. First download the TortoiseSVN software from the below link. https://tortoisesvn.net/downloads.html Download the Latest windows ADK so that we can use the latest App-V Sequencer from the below link. https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install Sequence the TortoiseSVN application using default steps. Even if you use PVAD when sequencing, we can see the same issue that the background context menu is not visible after publishing. After Publishing the sequenced package, we can see that when we right click file\folder\drive the context menu option is visible as App-V will install those respective registry entries in the local machine and they will be used by the explorer due to dynamic virtualization concept. FILE: FOLD...

When launching sequenced Adobe illustrator shortcut we see the below issue in the App-V client machine. Reason: This is due to UAC and the application requires to be run as administrator. Solution: To test manually Click Start > All Programs. Right click on the Adobe Illustrator shortcut  and click Run As Administrator. The shortcut will launch without any error. So how to resolve this in the App-V 5.x package? We need to suppress the UAC prompt when run as administrator using RunAsInvoker or other shims. Check my another blog for more information to solve this issue  here

Many packages that completely worked in inbox App-V in windows 10 1607 failed after upgrading to windows 10 1703. The reason for failure is due to Microsoft changed the way to load registries in containers CREG instead of usual virtual registry VREG. There was a temporary fix which was available and Roy Essers posted it in twitter a long back. It was adding the below registry entry manually in the 1703/1709 machines. [ HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\AppV\Client\Compatibility] "RegistryCompatibilityMode" = dword : 00000001 This issue is fixed in windows 10 1703 with the new hotfix released. https://support.microsoft.com/en-us/help/4077528 We can clearly see that they have made use of the temporary fix to change the registry virtualization to use the VREG instead of the modern CREG that was mentioned earlier to permanently fix this issue. Apart from the registry fix, this update also fixes many other App-V issues which can bee seen below. This update will be downloaded ...