VMware Horizon Community
esnmb
Enthusiast
Enthusiast

Office 2010 License PopUp

I followed http://blogs.vmware.com/thinapp/2010/08/step-by-step-instructions-on-how-to-thinapp-office-2010.html but the first time I open one of the Office apps after a reboot I get a license error and the app closes.  I re-open it and everything is fine. 

I didn't add the registry setting from the article as I am running Office 2010 32bit on Windows 7 64bit.

Thoughts?

Reply
0 Kudos
5 Replies
idle-jam
Immortal
Immortal

If you're on windows 7, you need to perform the file/registry change as well as installation of App-V deployment package. Else it will just prompt your for license.

NOTE:  If you plan to deploy Office 2010 to Windows 7 (32 bit) users, you must alter the package as follows:

First, make a complete backup of your Office 2010 package.  You will need to deploy a separate package for Windows 7 (32 bit) users.  Next, be sure you have a text editor available that can handle very large files, such as Notepad++ or Notepad2.  Back up your HKEY_LOCAL_MACHINE.txt file, and then in one of those editors, open the file.  We will need to make four changes:

1. Update an Installer Key

Search for:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\CC427126E291CBE47960B02470798141

You will find this value:

isolation_full  HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\CC427126E291CBE47960B02470798141
   Value=00004109110000000000000000F01FEC
   REG_SZ=#00

Change it to this:

isolation_full  HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\CC427126E291CBE47960B02470798141
   Value=00004109110000000000000000F01FEC
   REG_SZ~02:\SOFTWARE\Microsoft\Windows Search\ProtocolHandlers\Mapi\0\ProgID#2300

2. Update another Installer Key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\1C142428AC6D17249BC6F1CEA00887F3

You will find this value:

isolation_full  HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\1C142428AC6D17249BC6F1CEA00887F3
   Value=00004109110000000000000000F01FEC
   REG_SZ=#00

Change it to this:

isolation_full  HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\1C142428AC6D17249BC6F1CEA00887F3
   Value=00004109110000000000000000F01FEC
   REG_SZ~02:\SOFTWARE\Microsoft\Windows\CurrentVersion\PreviewHandlers\{435fdba0-964c-43a7-8aff-cc94e21b2249}#2300

3. Update a Preview Handler Key:

Search for:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\PreviewHandlers

You will find:

isolation_full HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\PreviewHandlers
   Value={00020827-0000-0000-C000-000000000046}
   REG_SZ~Microsoft Excel previewer#2300
   Value={65235197-874B-4A07-BDC5-E65EA825B718}
   REG_SZ~Microsoft PowerPoint previewer#2300
   Value={84F66100-FF7C-4fb4-B0C0-02CD7FB668FE}
   REG_SZ~Microsoft Word previewer#2300
   Value={21E17C2F-AD3A-4b89-841F-09CFE02D16B7}
   REG_SZ~Microsoft Visio previewer#2300

Change it to:

isolation_full HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\PreviewHandlers
   Value={00020827-0000-0000-C000-000000000046}
   REG_SZ~Microsoft Excel previewer#2300
   Value={65235197-874B-4A07-BDC5-E65EA825B718}
   REG_SZ~Microsoft PowerPoint previewer#2300
   Value={84F66100-FF7C-4fb4-B0C0-02CD7FB668FE}
   REG_SZ~Microsoft Word previewer#2300
   Value={21E17C2F-AD3A-4b89-841F-09CFE02D16B7}
   REG_SZ~Microsoft Visio previewer#2300
   Value={435fdba0-964c-43a7-8aff-cc94e21b2249}
   REG_SZ~Microsoft Office Outlook MAPI Preview Handler#2300

4. Finally, insert two new Protocol Handler keys:

isolation_full HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search\ProtocolHandlers\Mapi

isolation_full HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search\ProtocolHandlers\Mapi\0
   Value=ProgID
   REG_SZ~Outlook.Search.MAPIHandler.1#2300

Make sure to maintain proper spacing by adding an empty line between keys.

Save the file and build the package.

Preparing your target machines

Now that the package is created, it is time to prepare your target machines for running a virtual copy of Office 2010.  To do this, install the Office 2010 Deployment pack from Microsoft.  This install when extracted contains a windows installer file, which must be configured with the following command line:

Msiexec /I OffVirt.MSI PROPLUS=1

(Add USEROPERATIONS=1 to the command line if you want to allow Non-administrators to activate Office.)

This can be deployed silently to your target machines using any traditional software delivery platform.  Once the pack is deployed, you can now use your virtual copy of Office 2010.

Without the Office deployment pack installed, you may encounter a Windows Installer Repair when running Office.  Be sure that users running Windows 7 (32 bit) have the Deployment pack pre-installed prior to running your ThinApp package.

Reply
0 Kudos
esnmb
Enthusiast
Enthusiast

Is there any way to update an existing thinapp msi package that is deployed via View for this registry change? 

Reply
0 Kudos
esnmb
Enthusiast
Enthusiast

I made the changes and have have re-run the build.bat.  I need to create and msi package.  Will this happen or so I need to run with some switches?

Reply
0 Kudos
esnmb
Enthusiast
Enthusiast

I made the registry changes and now there are all kinds of licensing errors.

Reply
0 Kudos
smccarthy01
Contributor
Contributor

Set the  "Office Software Protection Platform" Service to automatic startup on the target workstations and you will prevent the licence error messages after a reboot.

Reply
0 Kudos