ThinApp 4.7.3-Office 2010

[RS_2042]

I have read in KB article 1022287 that Office 2010 that is nativly installed will work with a Thinapp (TA) version of office.  That does not seem the case.  I have Office 2010 standard installed nativly on Windows 7.  KMS activates this with no issues.  I then TA Access 2010 and test that application.  The TA access runs fine.  When  I combine the two I get the license error when I run a TA access with native office.

Has anyone been able to get Office to work with another Office product without the licensing error and repiar warning.  VMware states they fixed it but I sill am unable to get it to work.  I have tried all the steps in the KB article as well as some others but nothing seems to work.

[oliAH]

Did you really follow this KB?

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102228...

I think you forgot to add the lines of the "Office2010-Osppsvc-Keys.txt" file. That should be why you are getting the repair assistant.

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 or higher.
2. Add the text entries in the Office2010-Osppsvc-Keys.txt file (which is attached to this article) at the top of the HKEY_LOCAL_MACHINE.txt file in the project directory.

Add the lines of this file, rebuild your app and you should be good.

[Schraeger]

I have done that and that did not work.

[Lakshman]

Hi,

Office 2010 capturing process has changed from 4.7.3. Have you followed the below steps in the KB article:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102228...

From 4.7.3 onwards, the following steps need to be performed:

1. In the project directory, copy the folder OfficeSoftwareProtectionPlatform from %Drive_C%\Documents and Settings\All Users\Microsoft to %Drive_C%\ProgramData
2. If present, delete the following lines from HKEY_CURRENT_USER.txt file in the project directory:

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

[Schraeger]

Yes I have followed that article to a tee.

[oliAH]

At least one event should be logged in Event Viewer, one who tells you what triggered the MSI self-repair.

This blog post may help you:

http://blogs.vmware.com/thinapp/2012/04/solving-msi-self-repair-issues-in-thinapp.html

[JMac201110141]

Hi,

When you captured Access 2010 did you do it on a clean machine?

From memory it only worked for me when I installed the rest of the Office 2010 suite on the capture machine before starting the capture, then captured the changes after adding Access.

I also followed the steps in the documentation pointed to by the previous posters.

I found it really frustrating getting the Office 2010 apps working with ThinApp, but I was able to get Access, Project, and Visio working eventually.

-Johnny

[virtualester]

Its been a while, but i think I ran into exact same problem. I run win7 32 and 64. I got it working by installing the Office 2010 Deployment Kit for App-V.   .on the guest vm. 

I also used this procedure to run individual thinapped office apps on other systems that did not have native office installed.  after installing the appv kit, I had to set the office platform protection service to automatic start,    Hope it helps.

http://support.microsoft.com/kb/983462

follow step 3