This document contains a list of known issues with Microsoft Application Virtualization 5.0 (App-V 5.0) Office 2010 packages that are built by using the method for sequencing an integrated Office 2010 package that's described in http://support.microsoft.com/kb/2830069. Some of the listed issues also include workarounds.
Known issuesThe Microsoft Office Deployment Kit supports only MAK, KMS or Volume License product keys
The Office 2010 App-V Deployment Kit is the tool used to manage the licenses for an Office 2010 package. This kit installs the Office Software Protection Platform (OSPP) service and requests a KMS license from a KMS server, or uses the MAK keys provided during the installation. The only licenses that can be used with the deployment kit are the ones with MAK, KMS or Volume License (VA) in their name. Although there are multiple activation keys, if they are not labeled as MAK, KMS or Volume License they will not work with the deployment kit.
For example, the following key type does not work with the deployment kit:
AA Lab Key - This lab use key is for Academic Alliance programs and allows multiple activations. Though it is labeled for multiple activations, it is not labeled as MAK and if this key is used, OSPP will consider the key a retail key instead of for multiple activations.
The following does work with the deployment kit:
AA MAK Key - This is a multiple activation key for Academic Alliance program customers. This one will work, as it's labeled MAK.
AA VA 1.0 - This volume license key (VA 1.0) is for Academic Alliance programs and allows multiple installations.
When using the deployment kit and specifying several license modes for Visio 2010, the highest license mode is used
If you are deploying a virtualized version of Visio 2010 and specify several license modes for Visio, the highest mode is selected. Below is an example:
msiexec /i OffVirt.msi PROPLUS=1 VISIOPREM=1 VISIOSTD=1 VISIOPRO=1
When you use this command, the VISIOPREM license will be applied. This behavior is discussed in the following blog post:
http://blogs.technet.com/b/odsupport/archive/2010/12/03/volume-license-editions-of-visio-2010-install-premium-edition-by-default.aspxTo work around this issue, you must deploy the Offvirt.msi with only the license mode that is required on the computer. An example is provided below:
msiexec /i OffVirt.msi PROPLUS=1 VISIOSTD=1
NOTE The Office Deployment Kit is a per computer application. If the installation is performed on a Remote Desktop Services (RDS) server, the switches used in the last installation will apply.
Another running MSI causes package deployment failure
The Office 2010 package deployment installs the Office Licensing Service on the App-V 5.0 client. The license installation will fail if another MSI (such as a Windows update) is already running on the system. This will cause the package deployment to fail. If this happens, try the package deployment after the other MSI has stopped running.
When an Office application is launched for the first time after the Office 2010 package is deployed, the Office application will prompt for an upgrade. Please cancel out of the upgrade prompt as the upgrade for virtual applications cannot be done that way.
Office co-existence: Natively installed Outlook 2007 does not work after you have deployed the App-V 5.0 package
Outlook 2010 upgrades the profile and mailbox information. Therefore, Outlook 2007 may not function correctly after these upgrades have been made by Outlook 2010.
Cannot insert Office 2010 objects into native applications such as WordPad
From WordPad, you cannot insert an Office 2010 object such as an Excel spreadsheet by using the “Create New” option.
Workaround: Use the “Create from File” option or use the Dynamic Deployment Configuration file while deploying the Office 2010 package.
Office Licensing Service (OSPP) gets uninstalled
If you remove one version (v) of the Office 2010 package, after upgrading the Office package (version v+1), the OSPP service will get uninstalled as part of the removal process. This will cause Office applications to generate licensing failures. As a workaround, please keep all previous versions of Office packages deployed to the machine even if you have deployed new versions of the Office 2010 package.
"Send to" Outlook feature in Office 2010
The "Send to" Outlook feature is not currently supported from an Office 2010 application. For example, in Word, you cannot send the file to Outlook as an attachment, nor can you right-click a Word document and send it to a mail recipient through the Send to option.
Article ID: 2828619 - Last Review: Oct 29, 2013 - Revision: 1
Microsoft Application Virtualization 5.0 for Remote Desktop Services, Microsoft Application Virtualization 5.0 for Windows Desktops