In my article ‘Multiple shortcuts with different access permissions‘ I explained how it is possible to manage an application with different shortcuts with different access permissions with the Application Virtualization web interface. Now I will explain how this is done with SCCM 2012 R2 with CU2.
The basic information can be found in the document ‘Managing AppV5 with Configuration Manager 2012SP1‘. In short: for each application you will have one appv file, one deployment config xml file and one user deployment config xml file.
For example: for the TEST environment you will have the following files on your SCCM Packages share:
- Demo_MoreShortcuts_1.0_ENG.appv
- Demo_MoreShortcuts_1.0_ENG_DeploymentConfig.xml
- Demo_MoreShortcuts_1.0_ENG_UserConfig – TEST.xml
For example: for the PROD environment you will have the following files on your SCCM Packages share:
- Demo_MoreShortcuts_1.0_ENG.appv
- Demo_MoreShortcuts_1.0_ENG_DeploymentConfig.xml
- Demo_MoreShortcuts_1.0_ENG_UserConfig – PROD.xml
In this article I will describe the steps for the PROD environment.
Create the collection
Update collection membership
Create the application

You see all the files that are used. Please mention the name of the user config xml file. That will be used later on.
Distribute the content
Create the deployment
Test on the client
Before performing these steps log in with a userid that is member of the group ‘APPL – Demo_PRD’.

In the AppEnforce.log you see what commands are executed to install the application.
As the collection is user based, the application is deployed on a per user basis. And thus the user config xml is used.

If you enter the powershell command ‘Get-AppVClientApplication -Name *environment*’ you see the settings as mentioned in the appv file.