Home > Blogs > VMware ThinApp Blog


Quick-start guide for deploying Office 2010 using ThinApp 4.6.1

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, make sure to read this blog entry first.

image

Before starting, note Office 2010’s system requirements:
http://technet.microsoft.com/en-us/library/ee624351.aspx#section1

Capturing Office 2010

Capturing on Windows XP SP3 with Volume Activation (KMS) installer
  1. Copy Microsoft .NET 3.5 and Office installation files to the capture machine.
  2. Install ThinApp on capture machine (or run Setup Capture from a network share)
  3. Run the Setup Capture wizard until you complete the prescan operation.
  4. On the Install Application page of the Setup Capture wizard, minimize the wizard and install Microsoft .NET 3.5
  5. 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:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe executequeueditems"
  6. Start the Microsoft Office 2010 setup wizard.
  7. Accept the terms of agreement
  8. On the Choose the installation you want dialog box, click the Customize button.
  9. Select Microsoft Office > Run all from My Computer.
  10. Click Install Now to install Microsoft Office 2010.
  11. Run postscan
  12. Change the Inventory name to something appropriate for your use.
  13. Before building project, move the OfficeSoftwareProtectionPlatform folder from %drive_C%\Documents and Settings\All Users\Microsoft to %Common AppData%\Microsoft
  14. Put the following in HKEY_CURRENT_USER.txt: "isolation_writecopy HKEY_CURRENT_USER\Environment
                                                                             Value=ALLUSERSPROFILE
                                                                             REG_SZ~%Common AppData%"
  15. Put the following in HKEY_LOCAL_MACHINE.txt: "isolation_full HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Search\Preferences
                                                                             Value=PreventIndexingOutlook
                                                                             REG_DWORD=#01#00#00#00"
Capturing on Windows XP SP3 with Retail installer
  1. Copy Microsoft .NET 3.5 and Office installation files to the capture machine.
  2. Make sure you have access to the internet
  3. Install ThinApp on capture machine (or run Setup Capture from a network share)
  4. Run the Setup Capture wizard until you complete the prescan operation.
  5. On the Install Application page of the Setup Capture wizard, minimize the wizard and install Microsoft .NET 3.5
  6. 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:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe executequeueditems"
  7. Start the Microsoft Office 2010 setup wizard.
  8. 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
  9. Accept the terms of agreement.
  10. On the Choose the installation you want dialog box, click the Customize button.
  11. Select Microsoft Office > Run all from My Computer.
  12. Click Install Now to install Microsoft Office 2010.
  13. Run postscan
  14. Change the Inventory name to something appropriate for your use.
  15. Before building the projec,t ove the OfficeSoftwareProtectionPlatform folder from %drive_C%\Documents and Settings\All Users\Microsoft to %Common AppData%\Microsoft
  16. Put the following in HKEY_CURRENT_USER.txt: "isolation_writecopy HKEY_CURRENT_USER\Environment
                                                                             Value=ALLUSERSPROFILE
                                                                             REG_SZ~%Common AppData%"
  17. Put the following in HKEY_LOCAL_MACHINE.txt: "isolation_full HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Search\Preferences
                                                                             Value=PreventIndexingOutlook
                                                                             REG_DWORD=#01#00#00#00"
Capturing on Windows XP SP3 with MAK installer
  1. Copy Microsoft .NET 3.5 and Office installation files to the capture machine.
  2. Make sure you have access to the internet
  3. Install ThinApp on capture machine (or run Setup Capture from a network share)
  4. Run the Setup Capture wizard until you complete the prescan operation.
  5. On the Install Application page of the Setup Capture wizard, minimize the wizard and install Microsoft .NET 3.5
  6. 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:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe executequeueditems"
  7. 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)
  8. Add the following line to the Config.xml file and save it to your local drive:
    <PIDKEY Value="AAAAABBBBBCCCCCDDDDDEEEEE" />
    Where AAAAABBBBBCCCCCDDDDDEEEEE is the 25-character product key.
  9. 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 <path of Config.xml file>
  10. Accept the terms of agreement.
  11. On the Choose the installation you want dialog box, click the Customize button.
  12. Select Microsoft Office > Run all from My Computer.
  13. Click Install Now to install Microsoft Office 2010.
  14. Run postscan
  15. Change the Inventory name to something appropriate for your use.
  16. Before building the project , move the OfficeSoftwareProtectionPlatform folder from %drive_C%\Documents and Settings\All Users\Microsoft to %Common AppData%\Microsoft
  17. Put the following in HKEY_CURRENT_USER.txt:
    isolation_writecopy HKEY_CURRENT_USER\Environment
    Value=ALLUSERSPROFILE
    REG_SZ~%Common AppData%
  18. Put the following in HKEY_LOCAL_MACHINE.txt:
    isolation_full HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Search\Preferences
    Value=PreventIndexingOutlook
    REG_DWORD=#01#00#00#00

Deploying Office 2010

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.
  1. If deploying on a W2K3 install MSXML 6.0
  2. Register the executables or install the MSI.
  3. Run Office 2010 applications

Advanced Capturing

.NET 3.5

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.

Questions / Comments / Problems?   Join us in the community forum

19 thoughts on “Quick-start guide for deploying Office 2010 using ThinApp 4.6.1

  1. J. Klein Kromhof

    He,
    Having trouble activating the Office 2010 with ThinApp 4.6.1.
    – Do we still need to use a script or not?
    – If yes, is it office2010 (from microsoft) or office2010-1 (from vmware)?
    – When i start, for example, Word 2010, it’s telling me it’s not activated.
    – When closing any program of the virtualized Office 2010, the .exe and .dat stay active in Task Manager, do I need to use a KillScript?

  2. Tim J

    Hi guys,
    How does this solve the reactivation that takes place when there is a significant hardware change which invalidates the Activation ID generated for that specific computer? This seems like something that can occur immediately when running the virtual package on a computer which has different hardware (more specifically, motherboard) from the packaging computer? Sure, for a virtual desktop there is less of an issue, but AFAIK there are still more physical than virtual desktops out there :).
    This is an issue both for MAK and KMS since this immediately drops the product in a Out of Tolerance grace period, which is only 30 days (compared to the 180 day period which is in place for KMS reactivation).
    Furthermore, why are you putting the location of the SoftwareProtectionPlatform in a write_copy mode? This means that when the product activation takes place on the client side, the activation code is written to the sandbox; it would make more sense to write this to the OS since the activation is specific to that OS/hardware anyway?
    There is a reason why Microsoft App-V users have to go through the Office 2010 deployment toolkit for App-V, and in fact why it is mandatory to use that kit when virtualizing Office 2010… I don’t see any of these reasons tackled in the recipe above…
    Thanks for any information & feedback,
    Tim

  3. Jeff

    I am getting an activation / licensing error when attempting to use the entry points as shortcuts from a Win7 VM other than on the system where the capture was done.
    I used the MKS method above to capture the 32bit ProPlus package on a WinXP 32bit VMware Workstation (v7.1.3) vVM. I was able to run the resulting thinapp entry points from the Win7 bare metal OS on the same system as the vmware workstation install used for the capture. However, I am prompted to Activate the software when I launch it.
    I get the error “An unspecified error has occurred. Your request cannot be processed at this time. Please try again later. (0x80070190)”
    I then copied the .dat file and all the entry point .exe files to a file server.
    Launch it again from my bare metal Win7 system, get the activation window, attempt to activate and get the same error as above.
    Then powered up my Win7 image used for View (running on a ESXi v4.0 host). From that desktop I logged in and attempted to run the Word .exe entry point by connecting to the file server by UNC path and launching the .exe.
    Word starts but then launches a first run setup installer.
    The installer fails with the following error:
    “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.”
    I assume this is due to the activation issue noted by Tim.

  4. Barry

    I have tried the above too, but does not seem to work?
    On XPSP3 Office tries to re-configure itself then fails.

  5. a_catalin

    I have tried but I get the activation window every time I open ThinApped Office…
    So it doesn’t seem to be working 100%.
    Thanks anyway.

  6. Paul Weir

    I’m just wondering if I could ThinApp .NET and then AppLink that package from the regular Office install.
    – Paul Weir

  7. Ramon

    Hello together
    The Office2010-Package works very goog but ther’s still one problem:
    The start of the application ist very slowly.
    Have anyone an idea how to makte the performance better than now.

  8. David Bradford

    Hi guys, I have successfully Thinapp’d Office Pro Plus 2010 (installing only Access) except for one thing – I cannot get Help files to load.
    I made sure before post-scanning to load the Help files but when I try to load them from the Thinapp’d Access, it tries to repair and then fails with error 1719.
    Any ideas?

  9. B4Z

    Hi, I have managed to successfully produce an Office 2010 ThinApp with no activation issues and all Office applications, including Outlook 2010, work correctly. I have created a guide that can be found on my blog at:
    http://www.b4z.co.uk/vmware-thinapp-microsoft-office-2010-setup-guide.html
    The guide details how to get the Office 2010 ThinApp working on both Windows XP and Windows 7 operating systems. It also details how to overcome activation issues when logged in as a standard windows user.

  10. Andrew Hennessy

    Has anyone been able to get the help file system in Office 2010 to work with above or any other procedure on XP SP3 using Thinapp client 4.6.1?
    I can successfully get it to go on W7 32bit and 64bit platforms however XP SP3 it fails every time. Has anyone got a workaround or can confirm it is also an issue for them?
    License activation is not an issue only the Help system.
    Thanks in advance,
    Andrew.

  11. Don

    Hi All
    Has anyone tried getting an image working thats able to run both versions (STD and Pro) ? Obviously not simultaneously but i have a situation where someone would be using STD and then need to “upgrade” (switch to using the PRO version) or vice versa. The problem is once either one of them has been activated(KMS) the other does not work. When i swap apps, the new one tries to repair itself and fails with error 1336: Cannot create temporary folder.
    Any ideas or suggestions would be greatly appreciated.

  12. Frustrated packager

    don’t waste your time with this guide, it doesn’t actually work. I’ve tried every thinapp virtualisation recipe on the net, they all fail.
    It may occasionally seem to work but it will break soon enough.
    If you want virtual Office 2010 get App-V

  13. Jason Coleman

    I’ve managed to get Office 2010 ThinApp’ed using a KMS server for licensing. I captured on a 32 bit Windows XP machine and have been able to run my packages on 32 bit XP and on 64 bit Windows 7 (the two desktop OSes in this environment). I’ve been doing a fairly aggressive cleanup of my packages prior to building – I delete the Fonts (installed natively on the desktops), Internet Cache and History folders outright, as well as the MSOCache (I forget where that one is buried but a file search will find it) and all of the non variable folders/files under %systemRoot%\Installer). I actually received feedback from one user that the ThinApp 2010 loads faster than his native Office 2007. I’m using ThinApp 4.6.2.

  14. Mitja

    I used this guide to capture Office 2010 using ThinApp 4.6.2. I use KMS licensing. I had the network adapter detached during the whole capture process and I stopped the OfficeSoftwareProtectionPlatform service before postscan. ThinApp works great on both Win XP and Win 7!
    I am also able to run multiple Office thinapps concurrently but there is a catch. When you want to do this, before prescan you have to stop&disable the Office Software Protection Platform service. After prescan remove the OfficeSoftwareProtectionPlatform folder from the thinapp build project. On the VMs office app-v kit needs to be installed using the kms client keys, e.g. if you want to run office 2010 std and visio 2010 std concurrently, run this on your VMs:
    msiexec /i OffVirt.msi STANDARD=1 VISIOSTD=1

  15. DDH

    Either I’m missing it, or has no one thin app’d Office 2010 Pro on a Win7 VM? All references seem to point to doing it with XP, which we’re moving away from. Yes, I see it ‘supposedly’ works on both XP and Win7 even tho thin app’d on XP, but I’d like to hear the issues of doing it on an actual Win7 VM.

Comments are closed.