App-V 5.0 and shortcuts

Question

Hello, 
There are a couple of things around App-V 5.0 and shortcuts I'm still a little confused about. 
I once created a package of Project and Visio 2013 with the click-to-run\deployment tool. The package worked great until someone said they needed Project but don't have a license to visio. To avoid this I made a shortcut to the executable in %localappdata%
and set restrictions to the shortcut with AD groups. However when I double clicked on a visio document, the user would still be able to run Visio. I tried to avoid this by creating two packages, one with Visio and one with Project. The problem here is that
I can add one package to the management console but not the other because it says a package with that name and version already exist although the name is indeed different, the version is the same.
SO, (TL;DR): How am I supposed to separate Visio and Project if it is in the same pacakge when creating two separate packages is not supported?

Answer 1

You need to modify the deployment configuration XML file to disable shortcuts. Maybe create multiple DeploymentConfig.xml files? DeploymentConfig_VisioOnly.xml, DeploymentConfig_ProjectOnly.xml .. ?
How to disable an Office 2013 application:
Open a Deployment Configuration File with a text editor such as Notepad and search for "Applications."
Search for the Office application you would like to disable, for example "Access 2013."
Change the value of "Enabled" from "true" to "false."
Save the Deployment Configuration File.
Add Office 2013 App-V Package with new Deployment Configuration File.
How to disable shortcuts for Office 2013 applications:
Open a Deployment Configuration File in Notepad and search for “Shortcuts”.
To disable certain shortcuts, delete or comment out the specific shortcuts you don’t want. You must keep the subsystem present and enabled. For example, in the example below delete the Microsoft Access shortcuts, while keeping the subsystems <shortcut>
</shortcut> intact to disable the Microsoft Access shortcut.
Save the Deployment Configuration File.
Re-publish Office 2013 App-V Package with new Deployment Configuration File.
http://technet.microsoft.com/library/dn481351.aspx