How to edit the Shortcut name in App-V 5.0

Ques: I have sequenced an application and have succesfully tested it. Now I need to change the shortcut name as there is already another package with the same shortcut name in the same start menu location that exists on the client machine.When I opened the .appv file for editing using the App-V sequencer, I am not able to see the Shortcuts and FTA tab visible in the package editor. How can I edit the shortcut name now. Do I need to re-sequence again?

Ans: No need to re-sequence the application again.Open the .appv file using Microsoft Virtualization Sequencer 5.0 SP3 and select the Update Application in Existing Package option instead of Edit package.In the select Installer phase, select perform a custom installation option.Do not install anything, Just select I am finished Installing and proceed by clicking next-next.Select modify package using package editor. Now you will be prompted with Shortcut and FTA tab where you can edit the shortcut name.


Another easy way is to edit the shortcut tag in the  _DeploymentConfig.xml file .


<Shortcuts Enabled="true">
          <Extension Category="AppV.Shortcut">
              <File>[{Common Programs}]\Mozilla Firefox 41.0.lnk</File>
              <Target>[{ProgramFilesX86}]\Mozilla Firefox\firefox.exe</Target>

NOTE: While testing using powershell, the deployment config file needs to be added using the -DynamicDeploymentConfiguration parameter.If not added then the change made to the shortcut name will not reflect.

Add-AppvClientPackage "path to .appv" -DynamicDeploymentConfiguration "path to deploymentcofig.xml" | Publish -AppvClientPackage -global

A simplified Microsoft App-V 5.1 Management Server upgrade procedure

Check this official Microsoft Technet Link to know more about how to upgrade App-V 5.1 Management Server

Comparision between Native connection group and SCCM 2012 virtual environment in App-V 5.0

      Native & Full Infrastructure
SCCM 2012
Ø       Setting dependency to other virtual applications is done through Connection group.

Connection group is achieved through creating virtual environments  in the SCCM console.

Ø       Connection groups can be published either globally or to user.

Virtual Environments are published globally to the system alone.

Ø       Connection groups can contain a mixture of both user and globally targeted packages.

It cannot contain a mixture of both user and globally targeted packages. SCCM 2012 will only deliver connection groups if all member packages are targeted to either user or machine exclusively.

Mixed member targeting is not supported with Virtual Environments in SCCM.

Ø  Connection groups targeted globally cannot contain any user targeted Packages.Connection groups targeted at the user alone can contain both user and computer targeted packages.
Mixed scope connection groups always need to be targeted at the user.

Ø       Packages in a connection group set to use any version or set as optional will always use the latest version in cache when initially delivered.

Use any version is not available with SCCM. However we can use the "OR" operator in the console.

Ø      Connection groups can be enabled or disabled to a specific user by an administrator using PowerShell.

Not available as virtual environments are enabled for system only.

Ø      There are two levels of priority with connection groups that can be set in full infrastructure & native.

      1. Packages within a connection group can have priority over each other. 
      2. It can have priority between connection groups.

Virtual Environments can only handle priority between members of a connection group.This is handled by ordering the members in the console.It doesn’t handle priority between connection groups themselves.SCCM currently does not give the ability to set the priority of a virtual environment.So if Package A is a member of two separate connection groups and a user launches Package A, it will fail to launch.

Ø       Packages will fail to unpublish if they are set as mandatory in a published connection group.

Packages that are mandatory can be uninstalled in a virtual environment successfully.SCCM client will create a new connection group which excludes the uninstall package.

User settings and Connection Group in App-V 5.0

User settings from a connection group member packages will not be transferred to its Connection Groups. Similarly, once the Connection Group is disabled, user settings from the Connection Group will not be transferred to its member packages.

1.     Sequence Google chrome application using App-V 5.0.

2.     Sequence Adobe shockwave Player using App-V 5.0.

3.     Add/Publish/mount Google chrome App-V Package.

4.     Launch Google chrome shortcut and set as homepage.This setting will be stored in user profile location.

5.     Add/Publish/mount Adobe shockwave player.

6.     Now create a connection group for Google chrome and Adobe shockwave Player packages.

7.     Open Google Chrome and now you can see is not seen as home page. This is because user settings will not be transferred to the connection group.

8.     Now set as the new homepage. Close the shortcut and open the Google chrome package again. You can see the been set as homepage.

9.     Now disable the connection group and re-launch the Google chrome shortcut, you can see the home page will be set to and not This is because since we have closed the connection group, the user settings that was set inside the connection group will be broken and not reflected back to its member package.

App-V Knowledge Base (KB) Articles (UPDATED)

This article covers the list of Application Virtualization (App-V)  knowledge base articles.

3074456 - Hotfix Package 4 for Microsoft Application Virtualization 4.6 Service Pack 3

3070370 - App-V 4.x apps don't set Windows 8 deployment requirements in System Center 2012 Configuration Manager SP1

3065017 - Hotfix package 6 for Microsoft Application Virtualization 5.0 SP2

3060458 - Hotfix Package 2 for Microsoft Application Virtualization 5.0 Service Pack 3

3039022 - Hotfix Package 1 for Microsoft Application Virtualization 5.0 Service Pack 3

3031340 - SQL scripts to install or upgrade the App-V 5.0 SP3 Management Server database fail

2987845 - Mouse may become unresponsive after you launch an App-V application

2971989 - Hotfix Package 5 for Microsoft Application Virtualization 4.6 Service Pack 2

2915745 - How to deploy and manage Office 2013 on App-V 5.0

2873465 - Hotfix Package 1 for Microsoft Application Virtualization 5.0 Server Service Pack 1

2876368 - Applications that are sequenced through the App-V 5.0 SP1 Sequencer may not be installed correctly

2828619 - Known issues when creating or using an App-V 5.0 Office 2010 Package

2850582 - How to Use Microsoft User Experience Virualization with App-V applications

2843030 - Packaging error when using App-V 5.0 to sequence applications with RELS files

2848278 - How to launch processes inside the App-V 5.0 virtualized enviroment

2830069 - How to sequence Microsoft Office 2010 in Microsoft Application virtualization 5.0

2800730 - HTTP error 500.19 - Internal Server Error when Launching the App-V Management console 

2802399 - Memory leaks when you use an App-V package that contains icons in System Center Configuration Manager 2007 SP2

2804622 - Description of Microsoft Application Virtualisation 5.0 Service Pack 1

2792121 - Virtualized applications fail to launch and generate 00-000000C3 errors in sftlog.txt

2790852 - The Server App-V sequencing process failed with "The Sequencer could not stop the MSIServer service"

2797968 - Error granting access to an App-V package: Invalid input was passed.

2783096 - Launching a virtual application fails with error code 0x3E500D05-00090001

2780309 - How to provide fault tolerance and load balancing in Microsoft App-V v5

2780177 - How to Adjust the App-V v5 Publishing Server refresh schedule

2780313 - Domain Trust requirements for deploying App-V v5 across multiple domains using the Full Infrastructure model 

2783104 - Launching a virtual application fails with error code 0x4C40660C-80070005

2780810 - Supported Configuartion Manager and Microsoft Application Virtualization scenarios

2783120 - Launching a virtual application fails with error code 0x41E04304-00000028

2760974 - Deleting a package in Microsoft Application Virtualization fails with error code 0000B005

2780304 - Adding a package version in Microsoft Application Virtualization returns error 0x8007012F

2780807 - Five common App-v v5 implementation scenarios

2780808 - Publishing Servers get Automaticlly removed from App-V v5 client

2780809 - How to use PowerShell to find Packages in App-V v5 client connection groups

2768945 - How to remove a cached copy of an unpublished package in Microsoft App-V v5

2768954 - A Microsoft Application Virtualization MSI run from a mapped drive fails to install the virtual package

2772509 - Supported scenarios for deploying Microsoft Office as a sequenced App-V Package  (note: also see KB2780810) 

2774436 - Known issues when using App-V v5 Package Converter 

2777003 - An App-V v5 virtualized application fails to start with error 0xc0000142 

2777777 - Important changes in the App-V v5 Sequencer

2778019 - Adding a large application package via the Management Server console on App-V v5 fails with "Timeout expired"

2778168 - How to troubleshoot publishing server refresh failures in App-V v5 

2778283 - PowerShell cmdlets are not available after installing an App-V v5 component 

2778945 - Importing a deployment configuration file on App-V v5 fails with "The configuration file does not contain well formed AppV configuration XML" 

2778957 - Virtual applications deployed by .MSI on App-V v5 are not uninstalled correctly when using PowerShell

NOTE: This post was originally posted in Microsoft Technet WIKI. I have used it and have added some new missed out KB articles.Whenever any new KB is released, I will make sure this post will be updated.