application

Recently I came across the App-V technical document stating that "The App-V 5.x Sequencer cannot sequence applications with filenames matching "CO_<x>" where x is any numeral. Error 0x8007139F will be generated." https://docs.microsoft.com/en-us/microsoft-desktop-optimization-pack/appv-v5/creating-and-managing-app-v-51-virtualized-applications https://github.com/Microsoft/windows-itpro-docs/blob/master/windows/application-management/app-v/appv-release-notes-for-appv-for-windows.md So I ran a quick test to confirm on the same.I used App-V 5.1 sequencer and App-V 5.1.86 client for testing. During monitoring phase, I created a New folder in desktop for convenience.I then created 3 new files with different extensions (CO_123, CO_456.txt, CO_897.dll) and then proceeded stopping the monitoring phase. I was expecting that sequencer will throw an error or fail as mentioned in the Microsoft technical document. To my surprise sequencer completed without any issues. I ...

Earlier when we unpublish App-V packages it used to stay in the App-V cache location  and used to occupy unwanted storage space on the client machines. If we want to remove them to free up space we need to  do manual removal or using powershell command Remove-AppVClientpackage I had blogged earlier a simple powershell script to remove all unpublished packages that are either published globally or to a user.   With the release of the new windows 10 creators update v1703 App-V client provides options to automatically cleanup the unpublished packages.It requires restart. This option can be enabled either by PowerShell or group policy or Registry. PowerShell: Open PowerShell as administrator and run the below code. Set-AppvClientConfiguration -AutoCleanupEnabled 1   Run the below code to get the status. Get-AppvClientConfiguration Group Policy: Go to Administrative Templates-System-App-V-PackageManagement-Enable automatic cleanup of unused appv packages and select ena...

Often I see queries related to clearing leftover package files after unpublishing them. And so here is a sample powershell code to remove all unpublished packages from the system to clear the space they were occupying in the package store. $allpackages = Get-AppvClientPackage -all| Where-Object { $_ .IsPublishedToUser -like "False" -and $_ .IsPublishedGlobally -like "False" } | select Name $unpublished = $allpackages .name ForEach ( $package in $unpublished ) { Write-Host "$package" Remove-AppvClientPackage "$package" Write-Host "$package" removed. } NOTE: Test the code in a lab environment, as it doesn't support any error handling.

Recently I have been seeing many queries regarding shortcut Icon not displayed after publishing an virtualized App-V 5.x package. The answer would be quite simple. But I would like to demonstrate it with a simple example so that it can shed some light. Let us assume a person X has sequenced an application say example Adobe Reader application. He is doing some manual clean up in the package editor. He removed some junk entries to keep the package clean. He also removed the Installer folder that has the installer cache (.msi, .mst, .msp)captured from the installer package as he felt it is also unnecessary junk entries like all others do. After completing sequencing, he published the package to the machine in a standalone environment and saw that the shortcut icon is missing. He was wondering why the Icon is missing. He came back with a query as why the Icon is missing even after successful sequencing. Now lets troubleshoot for him. First let's edit the s...

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...