shaker.umh.es menu
CSS Drop Down Menu by PureCSSMenu.com
Computing > Issues with ThinApp and Microsoft Office 2010

Symptoms

  • Microsoft Office 2010 fails to launch
  • Microsoft Outlook 2010 fails to launch after configuration
  • You see the errors:
    • Microsoft Office cannot verify the license for this application. A repair attempt failed or was canceled by the user. The Application will now shut down.
    • Cannot Start Microsoft Outlook.  Cannot open the Outlook window.
    • There are no help topics available that match your request

Purpose

This article describes known issues with ThinApp and Microsoft Office 2010, as well as the necessary requirements for it to function. Following this article aids in the deployment of Microsoft Office 2010.

Resolution

These are known issues with ThinApp and Office 2010 family products, including Office 2010, Project 2010, and Visio 2010. Unless otherwise noted, all issues that refer to Office 2010 refer to all products in the Office 2010 family.

Note: The workarounds below are offered as suggestions only. Individual results may vary. These workarounds are specific to capturing Microsoft Office 2010 with ThinApp 4.6.1 or higher.

General Issues

  • The use of ThinApp 4.6.0 is not recommended. Use ThinApp 4.6.1 or higher instead.
  • Microsoft Office 2010 can only be virtualized when captured on or deployed to Windows XP SP3, Windows Vista SP1, Windows 7, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, and higher patch levels.
  • Capturing Office 2010 on a 64-bit operating system is unsupported. When capturing Office 2010, use a 32-bit operating system.
  • Any deployment to Windows Vista, Windows 7, or Windows Server 2008 fails to launch if a retail license is used. Virtualizing Office 2010 to those operating systems requires a volume license. Volume licensing can utilize one of two licensing activation technologies: Key Management Server (KMS) or Multiple Activation Key (MAK).
  • ThinApp deployments cannot be used to bypass Microsoft Office 2010 activation behavior expected in a native environment.
  • ThinApp deployments may fail to activate if Microsoft Office 2010 with KMS licensing was activated prior to the postscan. When capturing Microsoft Office 2010 with KMS licensing, ensure that it is not activated by disconnecting the network card (NIC) from the capture machine during the installation process.
  • VMware recommends that you stop the Office Software Protection Platform service prior to the postscan.
  • A virtualized Office 2010 family product using KMS or MAK licensing activation will terminate with an error if launched on an operating system where another virtualized Office 2010 family product is already running. To address this, install ThinApp 4.7.1.
  • Office 2010 may terminate with a licensing error if deployed to an operating system that either has or had the Microsoft Office 2010 Deployment Kit for App-V installed.

    Note: Uninstalling this software may not be sufficient to prevent the licensing error.

Note: For further information, see posts 46 and 48 in this VMware Communities thread.

Deploying Office 2010 to an operating system with native Office 2010

Office 2010 may fail to launch, or terminate with an error, when deployed to an operating system that already has an Office 2010 component natively installed, unless these steps are performed:

  1. Install ThinApp 4.7.1.
  2. Add the text entries in the Office2010-Osppsvc-Keys.txt file (which is attached to this article) at the top of theHKEY_LOCAL_MACHINE.txt file in the project directory.

Capturing on Windows XP / 2003 and deploying to Windows Vista / 7 / 2008

When captured on Windows XP or Windows Server 2003, any deployment to Windows Vista, Windows 7, or Windows Server 2008 fails to launch unless these steps are performed:

  1. In the project directory, move the folder OfficeSoftwareProtectionPlatform from %Drive_C%\Documents and Settings\All Users\Microsoft to %Common AppData%\Microsoft.
  2. Add these lines to the bottom of the HKEY_CURRENT_USER.txt file in the project directory:

    isolation_writecopy HKEY_CURRENT_USER\Environment
    Value=ALLUSERSPROFILE
    REG_SZ~%Common AppData%

Outlook with Windows Search

The Outlook component of Microsoft Office 2010 fails to launch after account configuration when deployed to an operating system that has Windows Search installed.

To allow Outlook 2010 to launch, add these entries to the bottom of the HKEY_LOCAL_MACHINE.txt file in the project directory:
isolation_full HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Search\Preferences
Value=PreventIndexingOutlook
REG_DWORD=#01#00#00#00

MAK license activation without Administrator rights

Users without Administrator rights may be unable to activate Microsoft Office 2010 if it is using MAK license activation, unless these entries are added to the bottom of the HKEY_LOCAL_MACHINE.txt file in the project directory:
isolation_full HKEY_LOCAL_MACHINE\Software\Microsoft\OfficeSoftwareProtectionPlatform
Value=UserOperations
REG_DWORD=#01#00#00#00

Help in Word 2010 does not work on Windows 2008 64-bit operating systems

When accessing Help in Word 2010 on a Windows 2008 64-bit operating system, you may see the message There are no help topics available that match your request unless these steps are performed:

  1. Install ThinApp 4.7.1.
  2. When capturing Office 2010, select a custom installation and install it to C:\Office.
  3. After installing Office 2010, launch it and press F1 to activate Help before taking the postscan.


THE CONTENT OF THIS ARTICLE IS PROVIDED "AS-IS," AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, VMWARE DISCLAIMS ALL OTHER REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, REGARDING THIS CONTENT, INCLUDING THEIR FITNESS FOR A PARTICULAR PURPOSE, THEIR MERCHANTABILITY, OR THEIR NONINFRINGEMENT. VMWARE SHALL NOT BE LIABLE FOR ANY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF THIS CONTENT, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF VMWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Additional Information

 
To automate the Office 2010 activation on user machines, this can be done with the Volume Activation Management Tool (VAMT). For more information on the Volume Activation Management Tool, see the Microsoft download page.

Note: The preceding link was correct as of August 7, 2012. If you find the link is broken, please provide feedback and a VMware employee will update the link.

Volume Licensing

Note: These steps are offered as suggestions only. Individual results may vary.

  1. Copy or extract the Microsoft Office 2010 installation source to a location where the files can be edited.
  2. Locate config.xml. This is in a folder called suiteWW, where suite is replaced by the suite of Microsoft Office 2010 you are installing.
  3. Add these lines to the bottom of the file, immediately above the last line which reads </Configuration>:

    • For KMS licensing activation:

      <Setting Id="KMSSERVICENAME" Value="kmsserver.domain.com" />
      <Setting Id="AUTO_ACTIVATE" Value="1" />

      Note: Replace kmsserver.domain.com with the name of your KMS server.

    • For MAK licensing activation:

      <PIDKEY Value="AAAAA-BBBBB-CCCCC-DDDDD-EEEEE" />
      <Setting Id="AUTO_ACTIVATE" Value="1" />
      <Setting Id="USEROPERATIONS" Value="1" />

      Note: Replace AAAAA-BBBBB-CCCCC-DDDDD-EEEEE with your MAK information.

  4. Save the modified config.xml.
  5. Take a prescan, then double-click setup.exe from the modified installation source.

    Note: Refer to the rest of this article for other considerations.

Update History

07/31/2012 - Added reference to VMware Communities thread 09/08/2012 - Added link to Quick Start Guide for Deploying Office 2010 using ThinApp

Attachments