Warning:  This post is a straight copy from the ThinApp team at VMware on how to package Microsoft Office 2010 on VMWare ThinApp 4.6.1.  Many thanks to the hard work by the VMware ThinApp Team!

Link to original post:  <a href="http://blogs.vmware.com/thinapp/2011/02/quick-start-guide-for-deploying-office-2010-using-thinapp-461.html">http://blogs.vmware.com/thinapp/2011/02/quick-start-guide-for-deploying-office-2010-using-thinapp-461.html</a>
<h5>Anxious to create your own Office 2010 packages using ThinApp 4.6.1?   The following quick-start guide will help lead you through the process.   If you haven't captured an application using ThinApp before, <a href="http://blogs.vmware.com/thinapp/2010/12/thinapp-poc-in-a-blog.html" target="_self">make sure to read this blog entry first</a>.</h5>
<h3><a href="http://blogs.vmware.com/.a/6a00d8341c328153ef0147e2ce6983970b-pi"><img src="http://blogs.vmware.com/.a/6a00d8341c328153ef0147e2ce698e970b-pi" border="0" alt="image" width="240" height="60" /></a></h3>
<h4>Before starting, note Office 2010’s system requirements:
<a href="http://technet.microsoft.com/en-us/library/ee624351.aspx#section1">http://technet.microsoft.com/en-us/library/ee624351.aspx#section1</a></h4>
<h4>Capturing Office 2010</h4>
<h5>Capturing on Windows XP SP3 with Volume Activation (KMS) installer</h5>
<ul>
	<li>Copy Microsoft .NET 3.5 and Office installation files to the capture machine.</li>
	<li>Install ThinApp on capture machine (or run Setup Capture from a network share)</li>
	<li>Run the Setup Capture wizard until you complete the prescan operation.</li>
	<li>On the Install Application page of the Setup Capture wizard, minimize the wizard and install Microsoft .NET 3.5</li>
	<li>The Microsoft .NET installation generates the mscorsvw.exe process that continues for an extended period, stop the process with the ngen.exe tool. By typing this in a cmd window: "C:WINDOWSMicrosoft.NETFrameworkv2.0.50727ngen.exe executequeueditems"</li>
	<li>Start the Microsoft Office 2010 setup wizard.</li>
	<li>Accept the terms of agreement</li>
	<li>On the Choose the installation you want dialog box, click the Customize button.</li>
	<li>Select Microsoft Office &gt; Run all from My Computer.</li>
	<li>Click Install Now to install Microsoft Office 2010.</li>
	<li>Run postscan</li>
	<li>Change the Inventory name to something appropriate for your use.</li>
	<li>Before building project, move the OfficeSoftwareProtectionPlatform folder from %drive_C%Documents and SettingsAll UsersMicrosoft to %Common AppData%Microsoft</li>
	<li>Put the following in HKEY_CURRENT_USER.txt: "isolation_writecopy HKEY_CURRENT_USEREnvironment
                                                                         Value=ALLUSERSPROFILE
                                                                         REG_SZ~%Common AppData%"</li>
	<li>Put the following in HKEY_LOCAL_MACHINE.txt: "isolation_full HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsWindows SearchPreferences
                                                                         Value=PreventIndexingOutlook
                                                                         REG_DWORD=#01#00#00#00"</li>
</ul>
<h5>Capturing on Windows XP SP3 with Retail installer</h5>
<ul>
	<li>Copy Microsoft .NET 3.5 and Office installation files to the capture machine.</li>
	<li>Make sure you have access to the internet</li>
	<li>Install ThinApp on capture machine (or run Setup Capture from a network share)</li>
	<li>Run the Setup Capture wizard until you complete the prescan operation.</li>
	<li>On the Install Application page of the Setup Capture wizard, minimize the wizard and install Microsoft .NET 3.5</li>
	<li>The Microsoft .NET installation generates the mscorsvw.exe process that continues for an extended period, stop the process with the ngen.exe tool. By typing this in a cmd window: "C:WINDOWSMicrosoft.NETFrameworkv2.0.50727ngen.exe executequeueditems"</li>
	<li>Start the Microsoft Office 2010 setup wizard.</li>
	<li>Type in your product key and make sure to check the box in the bottom that says "Attempt to automatically activated my product online" then click Continue</li>
	<li>Accept the terms of agreement.</li>
	<li>On the Choose the installation you want dialog box, click the Customize button.</li>
	<li>Select Microsoft Office &gt; Run all from My Computer.</li>
	<li>Click Install Now to install Microsoft Office 2010.</li>
	<li>Run postscan</li>
	<li>Change the Inventory name to something appropriate for your use.</li>
	<li>Before building the projec,t ove the OfficeSoftwareProtectionPlatform folder from %drive_C%Documents and SettingsAll UsersMicrosoft to %Common AppData%Microsoft</li>
	<li>Put the following in HKEY_CURRENT_USER.txt: "isolation_writecopy HKEY_CURRENT_USEREnvironment
                                                                         Value=ALLUSERSPROFILE
                                                                         REG_SZ~%Common AppData%"</li>
	<li>Put the following in HKEY_LOCAL_MACHINE.txt: "isolation_full HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsWindows SearchPreferences
                                                                         Value=PreventIndexingOutlook
                                                                         REG_DWORD=#01#00#00#00"</li>
</ul>
<h5>Capturing on Windows XP SP3 with MAK installer</h5>
<ul>
	<li>Copy Microsoft .NET 3.5 and Office installation files to the capture machine.</li>
	<li>Make sure you have access to the internet</li>
	<li>Install ThinApp on capture machine (or run Setup Capture from a network share)</li>
	<li>Run the Setup Capture wizard until you complete the prescan operation.</li>
	<li>On the Install Application page of the Setup Capture wizard, minimize the wizard and install Microsoft .NET 3.5</li>
	<li>The Microsoft .NET installation generates the mscorsvw.exe process that continues for an extended period, stop the process with the ngen.exe tool. By typing this in a cmd window: "C:WINDOWSMicrosoft.NETFrameworkv2.0.50727ngen.exe executequeueditems"</li>
	<li>Edit Office 2010 installation Config.xml file to enter your MAK key:
By default, the Config.xml file is stored in the core product folders in the Microsoft Office 2010 ISO (core_product_folder_name.WW folder, for example, ProPlus.WW)</li>
	<li>Add the following line to the Config.xml file and save it to your local drive:
&lt;PIDKEY Value="AAAAABBBBBCCCCCDDDDDEEEEE" /&gt;
Where AAAAABBBBBCCCCCDDDDDEEEEE is the 25-character product key.</li>
	<li>To start the Microsoft Office 2010 setup wizard and apply the settings in Config.xml, at a command prompt, type the following command, and then press ENTER:
Setup.exe /config &lt;path of Config.xml file&gt;</li>
	<li>Accept the terms of agreement.</li>
	<li>On the Choose the installation you want dialog box, click the Customize button.</li>
	<li>Select Microsoft Office &gt; Run all from My Computer.</li>
	<li>Click Install Now to install Microsoft Office 2010.</li>
	<li>Run postscan</li>
	<li>Change the Inventory name to something appropriate for your use.</li>
	<li>Before building the project , move the OfficeSoftwareProtectionPlatform folder from %drive_C%Documents and SettingsAll UsersMicrosoft to %Common AppData%Microsoft</li>
	<li>Put the following in HKEY_CURRENT_USER.txt:
isolation_writecopy HKEY_CURRENT_USEREnvironment
Value=ALLUSERSPROFILE
REG_SZ~%Common AppData%</li>
	<li>Put the following in HKEY_LOCAL_MACHINE.txt:
isolation_full HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsWindows SearchPreferences
Value=PreventIndexingOutlook
REG_DWORD=#01#00#00#00</li>
</ul>
<h4>Deploying Office 2010</h4>
<h5>Deploying on WXP SP3 32, W2K3 R2 32, W2K3 R2 64, W2K8 32, W2K8 SP2 32, Vista SP1 32, Vista SP2 32, Win7 32, Win7 64 Vista SP1 64, Vista SP2 64.  Machines should have a minimum of 512MB of RAM available.</h5>
<ul>
	<li>If deploying on a W2K3 install MSXML 6.0</li>
	<li>Register the executables or install the MSI.</li>
	<li>Run Office 2010 applications</li>
</ul>
<h4>Advanced Capturing</h4>
<h5>.NET 3.5</h5>
If the machines that you plan on deploying to already have .NET 3.5 installed then it is not necessary to capture .NET 3.5. This though will also cause a second issue in that the .NET Programmability Support features in Office 2010 and the Business Connectivity Services features might not install, depending on the OS you are capturing on. If these side affects are tolerable then you can save a couple of hundred megabytes in the size of your project.