Search the VMware Knowledge Base (KB)
View by Article ID

Packaging guide for ThinApp 5.x and Microsoft Office 2010 (2062694)

  • 29 Ratings


This article describes the process to be followed while packaging Microsoft Office 2010 family products, including Office 2010, Project 2010, and Visio 2010, with ThinApp 5.x.

For ThinApp 4.x and Office, see Issues with ThinApp 4.x and Microsoft Office 2010 (1022287).


To capture Microsoft Office 2010 follow these steps

Note: 64-bit Microsoft Office 2010 is only supported when captured on Windows 7.

  1. Extract the Microsoft Office 2010 installation files.
  2. Edit the config.xml file located in the suite.WW directory where suite is the suite of Office you are installing.
  3. Add these lines to the bottom of the file above </ Configuration>

    • For KMS licensing activation:

      <Setting Id="KMSSERVICENAME" Value=""/>
      <Setting Id="AUTO_ACTIVATE" Value="1"/>

      Note: Replace with your KMS server name.

    • For MAK licensing activation:

      <Setting Id="AUTO_ACTIVATE" Value="1"/>
      <Setting Id="USEROPERATIONS" Value="1"/>

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

  4. Run the Setup Capture wizard and take a prescan.
  5. Unless the capture machine and all deployment operating systems have the same version of .NET installed, capture .NET. For more information, see Packaging guide for .NET (2069188).
  6. Start the Microsoft Office 2010 setup wizard.
  7. Click Customize for the type of installation.
  8. Click Microsoft Office > Run all from My Computer.
  9. Click Install Now.
  10. Launch an Office component. Disable auto updates, confirm that it is activated, and exit the Office component.
  11. In services.msc, stop the Office Software Protection Platform Service.
  12. Take a Postscan.
  13. If required, modify the Inventory name.
  14. Edit HKEY_LOCAL_MACHINE.txt and add this entry to the bottom:

    isolation_full HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Search\Preferences

  15. Build the project.
  16. If you are deploying to a system that has Office installed natively and encounter a licensing issue, see Resolving licensing errors when deploying virtual Office to a system with Office installed natively (2107369).
Note: When using MAK licensing it is not possible to avoid having each end-user activate their Office software on first launch. Only KMS licensing works without any activation on the end-user side.

Additional Information

For translated versions of this article, see:

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 29 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 29 Ratings