application

In the Package editor under advanced tab, you can see the Manifest file tab which has been introduced in App-V 5.1. This doesn't exist in earlier versions of App-V. Using this tab, you can export or import the AppxManifest.xml file. Earlier if we want to do any custom changes we have to edit the deploymentconfig or userconfig.xml file(for adding scripts, editing FTA's etc). App-V 5.1 provides advanced way to edit those changes within the AppxManifest.xml. To do so, click on export as highlighted below in the Manifest file tab. This will export the AppxManifest.xml file to the local machine. choose the destination and click on save. Open the exported AppxManifest.xml using AppVManifestEditor. You can download the tool from here AVME AVME is a simple yet powerful tool to edit the AppxManifest file.My recommendation is not to edit the AppxManifest file manually. After opening the file using AVME,you can select the checkbox on left hand side to enable the type of script you want(Ma...

Recently I came across a question in TechNet about App-V 5.0 Sequencer getting crashed when saving a package and its possible reasons. In this blog I am listing out the possible reasons for sequencer crash and its solutions provided from other App-V techies. First and foremost it's always  a good start to check in the event log when ever there is an issue. Check the screenshot as where to look for sequencer log entries. Always enable show analytic and debug logs from view menu. 1. rels files: The App-V 5.0 sequencer fails to sequence if there is any .rels files present in the package. You can identify a relationship part by the presence of a file with a ".rels" file extension in a folder named "_rels". To know more check the link from Microsoft. https://support.microsoft.com/en-us/kb/2843030 2. Invalid manifest detected: Missing or invalid ProgId entries might also cause sequencer to crash with Invalid manifest detected error log. Check the link from Dan Gough. ...

When you try to send a file through mail by right clicking a file - sendto- mail recipient, the below error occurs. Solution: 1. Open registry by typing regedit in run. 2. Search for the office productguid in HKEY_CLASSES_ROOT\Installer\Components\ 3. Give read access to the Everyone. Now when you try to send a file through mail, MS outlook will launch as the default mail recipient.

There are some methods through which we can suppress UAC prompts when virtualizing using App-V 5.0. You can try the below methods which ever suits your need. 1. SET __COMPAT_LAYER: Edit the sequenced shortcut and add the below command. cmd.exe /c “SET __COMPAT_LAYER=RunAsInvoker & START Appname.exe” Note: There is a space in between SET and __COMPAT_LAYER. If you didn't leave any space it will throw an error. "SET' is not recognized as an internal or external command. 2. Registry Method: Right click on the shortcut and select properties-compatibility-privilege level- run as admin-apply. This will create a registry entry in the HKCU\HKLM based upon User/Machine selection. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\AppCompatFlags\Layers (or) HKEY_Current_User\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\AppCompatFlags\Layers Export the registry key and add it in the deployment config file and register it in the local machine. NOTE: Enable script exec...

Hot fix 1 has been released for App-v 5.1 and it has some new advantages over the earlier version. Check out the official release notes in the below link. https://support.microsoft.com/en-us/kb/3115834

Option 1 - Reinstall the App-V Client in the machine to resolve the wmi namespace issue. Option 2 - If you want to avoid reinstalling the App-V client, then try to reinitialize the wmi namespace. This can be done by using the below commands and running it in an elevated CMD. mofcomp "C:\Program Files\Microsoft Application Virtualization\Client\AppvClientWmiProvider\Remove.Microsoft.Appv.AppvClientWmi.mof" mofcomp "C:\Program Files\Microsoft Application Virtualization\Client\AppvClientWmiProvider\Microsoft.Appv.AppvClientWmi.mof" Option 3 - Alternatively check in wmimgmt.msc and restore appv wmi namespace.The below link is pretty old but should work. Link -  http://eskonr.com/2012/07/failed-to-open-wmi-namespace-virtualapp-log

Question : What happens when we unpublish an application that is in use in App-V 5.1? We see that the unpublish is getting failed, but when we launch the shortcut, it doesn't work.What is the issue? Answer : Lets take an example by publishing the Mozilla Firefox App-V 5.0 package in a standalone machine using Powershell. Launched the shortcut and everything works fine. Now tried to unpublish by keeping mozilla firefox open(in-use).We are seeing the below "Currently in use" error. We can see that the unpublishing has failed. Nothing has changed to the mozilla application. Shortcuts are seen in the Start menu etc. But when we try to launch the shortcut, we see this error. When analyzed more by checking in event viewer, we see the below entry. The package has been scheduled to be unpublished during restart/reboot. How this works? The App-V client creates an entry in pendingtasks registry for the particular application with its ProductGUID_VersionGUID. REASON:  With App-V 5...