Home > Blogs > VMware ThinApp Blog


Step by Step Instructions on How to ThinApp Microsoft Office 2007

Here are step-by-step instructions on how to install, configure, and capture Microsoft Office 2007 as a ThinApp Package. These instructions are provided "as is" but can be used to configure and deploy any version of Microsoft Office 2007.

Requirements

The following items and knowledge is required for use of this procedure:

  • A clean built VM with no other installations.
  • Familiarization with instructions on how to virtualize a software product via ThinApp (see, "How to Make a ThinApp Application" on http://blogs.vmware.com/thinapp).
  • A legal, licensed copy of Microsoft Office 2007.
  • A legal and valid Microsoft Office 2007 Volume License Key (VLK).
  • Have Microsoft .NET Framework

Warning!

Setup and configuration of any version of Microsoft Office 2007 as a ThinApp package should be done with a Microsoft Volume License Key (VLK) as a Retail License Key (RLK) must be activated on each new machine it runs on.

Building a ThinApp package in no way modifies the licensing of the software product you are attempting to virtualize with ThinApp! Ensure you are in compliance with product licenses for ANY software package you wish to virtualize and deploy using ThinApp. Consult your software product's End User License Agreement (EULA) for reference and questions.

Instructions on How to ThinApp Microsoft Office 2007

These are the basic instruction you will need on How to ThinApp Microsoft Office 2007

   

  1. Start with a cleanly built Windows XP VM.

    NOTE: Use the "How to make a ThinApp Application" as a reference.

  2. Run a ThinApp Pre-installation Setup Capture.
  3. Close the ThinApp Pre-installation Setup Capture using the red "X" in the upper-right corner.
  4. Launch the Microsoft Office 2007 Setup.
  5. Input the valid Microsoft Office 2007 Volume License Key.
  6. Accept the EULA.
  7. At the "Choose the installation you want" screen, select the CUSTOMIZE button.
  8. On the INSTALLATION OPTIONS tab, click the top level drop down to the left of MICROSOFT OFFICE and select RUN ALL FROM MY COMPUTER.
  9. All boxes should now be white. Click the INSTALL NOW button to continue.
  10. At this point you can package your ThinApp version of Office 2007 if you do not wish to install any updates which may be missing.
  11. After the installation is complete, click the GO TO OFFICE ONLINE button.

    NOTE: DO NOT go to the Microsoft Updates or Windows Updates sites as the update sites will also include Windows Operating System updates. Inadvertently installing a Windows OS update into your package may cause some issues.

  12. On the Microsoft Office site, click the DOWNLOADS link.
  13. On the Microsoft Office Download page, click the "Office Update" link.
  14. On the Microsoft Office Update page, click the CONTINUE button if you get the Genuine Microsoft Office checker.
  15. Click the CONTINUE button once you get the Genuine Microsoft Office banner.
  16. For any updates, click the box or boxes to select them, then select the AGREE AND INSTALL button on the web site.
    NOTE: You may need to return to the Office Updates selection site multiple times to get all the updates. If, after an update installs AND you need to reboot (such as a Service Pack), you can return to the Microsoft Office updates site by going to http://office.microsoft.com and following the directions in steps 12 and 13.
  17. After all updates are completed, reboot the VM to ensure proper updates occur.
  18. Open each application in the Office Suite to ensure settings are correct.
    NOTE: DO NOT click OK on the prompt for Name and Initials. Click the red "X" to close this. This will keep user information agnostic and allow the end user to set this as desired.
  19. Once done with configuring and updating Microsoft Office you need to run the ThinApp Post-Setup Capture.

    NOTE: Use the "How to make a ThinApp Application" as a reference.

    1. Run the ThinApp post installation scan.
      1. If you did not close the Setup Capture window, then you can NOW click NEXT to continue.
      2. If you closed the Setup Capture window, re-launch Setup Capture, select CONTINUE INSTALLATION PROCESS and click NEXT.
      3. Click NEXT again to run the post scan process.
      4. After the post installation scan is complete, you will be asked to select entry points for your application, assign a data container and set an Inventory name.
        1. Select the appropriate entry point or entry points.
        2. You can also select a primary data container – remember that large installations will need to use DAT files as a data container.
        3. Set your Inventory Name.

        Click NEXT when ready.

      5. The next screen will allow you to select which Active Directory User Groups you wish to assign permission to use this packaged application, including an Access Denied message, and where you would like the Sandbox location to be by default.
        NOTE: To use Active Directory groups, the VM which you are running this process on must be part of the domain to read in the A.D. Group SIDs.
        1. Click ADD to add in any groups desired.
          1. Set your Access Denied message if using groups.
        2. Select the default sandbox location

        Click NEXT when ready.

      6. Now you need to select the default Isolation Mode for the packaged application. Typically, most applications will be using MERGED for an isolation mode.
      7. You should now be asked to define a Project Location, whether you wish to build an MSI file (including the name of the MSI file), and what level of compression to use on the package.

        Typically, for testing, no compression is used. However, for finalized packages it may be desired to compress them depending upon their size.

        NOTE: Typical compression ratios are roughly 2:1 but can sometimes be as much as 3:1 depending upon the files in the package.

        Click NEXT when ready.

      8. At this point, your package will be created based upon the differences between the pre-installation scan and post-installation scan.
      9. Finally, you will be presented with an option to build your project. This essentially runs the BUILD.BAT file.

        You can select BROWSE PROJECT, BUILD NOW, or FINISH.
        1. If you select BROWSE PROJECT, you will be presented with a Windows Explorer window showing your project files. From there, if you wish, you can also run BUILD.BAT.
        2. If you select BUILD NOW, your project will be packaged into an executable or executables (depending upon the number of entry points selected).
        3. If you select FINISH, the Setup Capture window will be closed.
      10. Click FINISH when done.
  20. The following are suggested post-capture customizations.
    1. Delete the following folders as they should not be needed for anything.
      1. %COOKIES%
      2. %DRIVE_C%
      3. %HISTORY%
      4. %INTERNET CACHE%
      5. %PROFILE%
      6. %COMMON APPDATA%\VMware
    2. If you do not want any customizations inserted into your Office 2007 package, delete the contents of the %APPDATA% except the ##ATTRIBUTES.INI file. This will enforce the user get a cleanly configured office.
    3. Outlook Modifications:

      NOTE: Of the many areas where Outlook stores User Account data, this registry is one of them. When Outlook is started for the first time, it checks if this registry entry to see if it exists and, if not, prompts the user to create a new account. While this works fine when running the ThinApp package of Office Outlook 2007 on a system that DOES NOT have Office Outlook installed, it fails to work correctly when running the ThinApp package of Office Outlook on a Windows system that DOES have Office Outlook installed. Therefore, Full Isolation Mode is required for the registry keys and files of the ThinApp version of Office Outlook so that it can store its settings correctly in order to not interfere with the locally installed version of Office Outlook.

      1. HKEY_CURRENT_USER.TXT file isolation modifications:
        1. isolation_full HKEY_CURRENT_USER\Identities
        2. isolation_full HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles
      2. Create/Modify the ##Attributes.INI file with DirectoryIsolationMode set to FULL in the following folders:
        1. %AppData%\Microsoft\AddIns
        2. %AppData%\Microsoft\Office
        3. %AppData%\Microsoft\Outlook
        4. %Local AppData%\Microsoft\FORMS
        5. %Local AppData%\Microsoft\Outlook
      3. HKEY_CURRENT_USER.TXT Outlook Secure Temp folder modifications:
        1. Look for "isolation_full HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security" (add it if it does not exist) and add the following entries below it.
          1. Value=OutlookSecureTempFolder
          2. REG_SZ~%Profile%\Local Settings\OutlookTemp#2300
            ADDITIONAL NOTE: If you wish for the OutlookTemp folder to be more secure, you can modify the folder path to be whatever you like.
    4. Office 2007 Modifications:
      1. If you are running Office 2007 on a system which Office 2003 has already been installed, an issue exists where Office 2007 applications detect the "Handwriting" feature of Office 2003 but the Office 2007 applications cannot see all of the files and registry settings in order for the handwriting feature to work, subsequently causing a repair install of Office 2007.

        To repair this, make the following changes:

        1. Change the isolation settings in the ##Attributes.INI file to WriteCopy in the following folders:
          1. %ProgramFilesDir%\Common Files\Microsoft Shared\INK
          2. %ProgramFilesDir%\Common Files\Microsoft Shared\Office11
          3. %ProgramFilesDir%\Common Files\Microsoft Shared\Office11\1033
          4. %ProgramFilesDir%\Microsoft Office

          NOTE: Depending on your language version, you may need to modify the language folder as well

          1. %ProgramFilesDir%\Common Files\Microsoft Shared\Office11\1033
            English Language Version Code = 1033
      2. After capturing an Office 2007 install, the isolation mode on a couple of registry entries should modified as well in order for some standard functions to work properly. To do so, edit the HKEY_LOCAL_MACHINE.txt file and search for these keys and modify the from isolationmode_full to isolationmode_writecopy.
        1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\379E92CC2CB71D119A12000A9CE1A22A
        2. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\1650EACF3C291D11A92C0006794C4E25
      3. There currently is a known issue when packaging Office 2007 with both AppSync settings enabled and compression enabled – specifically around the "%Program Files Common%\Microsoft Shared\OFFICE12\ODSERV.EXE" file. To work around this, modify (or create) the ##ATTRIBUTES.INI file in the %Program Files Common%\Microsoft Shared\OFFICE12\ folder of your Office 2007 package and set the compression settings to none.

        [Compression]

        CompressionType=None

  21. Run the BUILD.BAT in the package.
  22. You have finished building the ThinApp package.
This entry was posted in Applications, Office, Tips and tagged on by .
Dean Flaming

About Dean Flaming

Dean is currently an EUC Architect and member of the VMware End User Computing Enablement and Lighthouse Support teams, working to develop communications and IP around VMware End User Computing products and solutions as well as support many various Lighthouse accounts with their own EUC practices. Prior to this, from 2008 through 2012 Dean was one of VMware's End User Computing Specialists. Throughout his time at VMware, Dean has also written and published various articles, videos, and podcasts regarding VMware's EUC Solutions.

77 thoughts on “Step by Step Instructions on How to ThinApp Microsoft Office 2007

  1. Olivier

    Hi,
    How to proceed with future patches released by MS?
    Is there a way to link the package with Microsoft update?
    Regards

  2. Dean Flaming

    Patching is generally dependent upon the application – specifically if the patch can be applied “through” the application or not (i.e. Installing a plugin to Firefox or IE is essentially “patching” the browser to view something).
    You have, essentially, two options:
    1. Patch within the application and use SBMERGE.EXE to import the sandbox to the capture
    2. Completely recapture the office installation with the patches installed.
    Now, you should ask yourself if it would be better to do option 1 or option 2.
    Generally, if it’s a service pack or major update, I’d say go with option 2. Otherwise, if it’s a simple patch or group of patches, I’d say go with option 1.
    For Office (any recent version), here’s where enabling the IEXPLORE.EXE entry point in the PACKAGE.INI comes in handy. If you’ve enabled that in your original package, you can open it and browse to http://office.microsoft.com and follow the above procedure from step 12 on. Once your updates are applied to your sandbox, use SBMERGE.EXE to dump your sandbox back to your package.
    IMPORTANT!: It is highly recommended that you make COPIES of your original Office captures, name it accordingly, and then apply the SBMERGE to that copy.
    Additionally, it is also recommended prior to applying the patches this way that you start with a fresh sandbox (watch out that you don’t accidentally apply any user settings either like name and initials).
    Hope this helps!
    -Dean F.

  3. Lucas

    I wish office 2007 can run on the oldest xp system and thus make a package of SP2, .net framwork and office 2007, but it won’t work.
    any suggestion?

  4. Lucas

    After tring, an office 2007 package made on xp sp2 looks work on xp without sp2.
    Another big problem is that a packaged BCM 2007 does not work. BCM 2007, business contact manager for outlook 2007, is included in office 2007 ultimate. I need it on my computers and smartphone.

  5. Dean Flaming

    Lucas, you should be able to run Office 2007 packaged on virtually any other version of Windows.
    If you need it linked to .Net, you can package the .NET Framework separately and link the Office package by use of OptionalAppLinks= or RequireAppLinks= in the Package.INI file of the Office package.

  6. Kris

    Hi Dean,
    It’s great to see all of this info posted, it’s very helpful. Regarding .NET, is it really needed? I see it listed in the requirements, but I didn’t see it mentioned in the step by step instructions. I’ve been packaging Office 2007 without installing .Net first. It seems OK, but I wonder if it would work better if I did (either packaging .net or app-linking to .net)
    Cheers!
    -Kris

  7. Dean Flaming

    Kris-
    Yes and No…
    To answer your question, Office 2007 does not “need” .NET Framework for most functionality. There are, however, some functions that will not work as Microsoft Office 2007 has the ability to utilize .NET Framework if it is installed.
    Specifically, the addition of .NET Framework allows access to all of the interop assemblies that allow Office 2007 apps “programmability with .NET Framework version 1.1 or greater” as Microsoft puts it. :-)
    So, if you don’t install any of these .NET Framework features into your office package, you do not need .NET Framework attached to or installed into your Office 2007 package.

  8. Paolo

    Hi,
    May I ask if, before BUILD the package, it’s possible to:
    1) delete the folder %SystemRoot%\Installer\$PatchCache$\Managed ?
    and
    2) delete the *.msi *.msp files int the folder %SystemRoot%\Installer?

  9. Dean Flaming

    Paolo-
    You should be able to delete those…I don’t see why you couldn’t. But you should test this as it may disable any “auto-repair” functions in Office as well as other features.
    Test, Test, Test!
    -Dean

  10. Chris

    Is it safe to say that in your point #20 we can delete all of those folders for any application we thinapp?

  11. Dean Flaming

    Well, yes… and no. This is really dependent upon what application you are packaging and what your desired results are.
    There may be reasons for not dumping these folders even if you are packaging Internet Explorer or an Internet Explorer based application – for example, you want settings retained in those folders kept and packaged into the ThinApp.
    I’d say, in general, if the application you are packaging IS NOT Internet Explorer or uses Internet Explorer as part of its base code (i.e. like the Microsoft CRM Client), then yes, you can probably dump those folders. :-)

  12. Alex Gomes

    Office 2007 keeps a copy of the install files so it’s also a good idea to remove the MSOCACHE folder from the C:\ drive (it’s a hidden folder) before performing the second scan. If you missed this step you can still remove it beofre building your package by removing MSOCACHE from the Package’s %drive_C% location.

  13. Dean Flaming

    Alex-
    Thanks for the submission!
    You are right…the MSOCACHE could be removed in the final Office package.
    There are cases where you might want to leave this in the package for testing/etc. but I’d suggest deleting it for the final package.
    -Dean

  14. DaveW

    Dean,
    Can you checkup on your OneNote 2007 installation (as part of Office 2007)? I am unable to select the color pen palette in OneNote 2007. It would be available at first, but once I selected a pen color, the whole palette would then become greyed out. Is this a bug with Thinapp? I have tested it with 4.0 and 4.0.1.

  15. Jonathan Hemming

    ThinApp 4.0.1 resolves some of the isolation mode issues so you don’t have to manually specify them in ##attributes

  16. Dean Flaming

    For Office 2007, ThinApp 4.0.1 alleviates the need to complete step 20.3 (Outlook Modifications) – except for the Outlook Secure Temp folder (admins should check to make sure this is set as desired) – and 20.4 (Office 2007 Modifications).
    We’ve not modified the blog entries pertaining to procedures that may relate to fixes in 4.0.1 as many customers still use ThinApp 4.0.0 and need the backwards compatibility.
    When using ThinApp 4.0.1 to capture Office 2007, admins will note the areas in the above procedure which no longer require manual modifications as ThinApp 4.0.1 will have automatically made the necessary changes.

  17. Phil Helmling

    Something to remember on removing the MSOCache and %SystemRoot%\Installer directories from the package, and that is some icons are derived from files within these locations. For example, most of the Office icons come from the %SystemRoot%\Installer\{90120000-0030-0000-0000-0000000FF1CE} folder. So if you remove this folder and then build your package, your icons will not look right and will also affect the icons for files associated with those applications. My suggestion with office2k7 is to remove the following:
    1) MSOCache as these .exe files are not entry points
    2) everything in the %SystemRoot%\Installer folder except the {90120000-0030-0000-0000-0000000FF1CE}, and {90120000-006E-0409-0000-0000000FF1CE} folders.

  18. DaveW

    Hi, Dean. Did you get a chance to look into the OneNote 2007 thinapp problem? Looking forward to seeing a fix here.

  19. Anthony

    I’m having trouble thinapping Office 2007 with ThinApp 4.0.1-2866 on a completely clean and up to date XP VM. I followed the directions listed above carefully (several times to make sure). The programs launch and seem to work fine until I try to insert clip art. I get the following error and the app crashes:
    ‘The operating system is not presently configured to run this application.’
    Followed by:
    ‘Clip Organizer cannot complete the operation.
    Application was launched but it didn’t register a class factory
    Error Code 0x800401FE’
    This error is logged in the system log isn’t much help. It says the description cannot be found.
    Before taking the second snap shot, I’ve tried running each program and inserting clip art and it works fine.
    Has anyone else had this problem or have any ideas what could cause it?

  20. Erik Jongebloed

    Hmmz, I’m trying to create it on 64 bit windows server 2008. When i want to run for example word i get an out of memory message. Anyone already tried that combination?

  21. James

    We are experiencing several issues with the thinapp’d Office.
    We see that OneNote issue with the color pen greying out after you first select one.
    We are also unable to print out of Outlook, it says that there are no printers installed, even though we can print out of Word and other apps in Office.
    any help would be appreciated.

  22. dietmarm

    Hello,
    I have created a portable version of Office 2007.
    I have performed all the steps described above.
    Unfortunately the following things do not work:
    1. If I call the help function with F1, then starts the Windows installer
    2. If i click on Visual Basic Button then i see the following error message:
    The function you are attempting to run contains macros or content that requires macro language support. When this software was installed, you (or your
    administrator) chose not to install support for macros or controls.
    What should I do?

  23. Dean Flaming

    Apologies for the delayed response.
    Currently the OneNote Pen is not supported as it is related to a driver issue. Support and Engineering are aware of this issue but if you would like for it to receive higher priority, please do open a support incident.

  24. Dean Flaming

    James-
    With regards to your printing issues, I tested this and my ThinApp Package of OneNote does print fine.
    Please check to see the “Spool” folder (located within the “%SystemSystem%” folder) is not missing or not set to MERGED isolation. The “Spool” folder (and all subfolders within it) should be in all ThinApp packaged apps where you wish the user to be able to print.

  25. Dean Flaming

    Please check to see the “Spool” folder (located within the “%SystemSystem%” folder) is not missing or not set to MERGED isolation. The “Spool” folder (and all subfolders within it) should be in all ThinApp packaged apps where you wish the user to be able to print.

  26. Dean Flaming

    Jason-
    Thanks for letting us know the forum tip from “dexter0” helped. I have copied them here as well – Thanks “dexter0” for the tip.
    We had this same issue for Office 2003 except that all Office programs would not print. To fix it I removed the following entries from the Current Users registry hive in my build directory.
    isolation_writecopy HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Devices
    Value=Microsoft Office Document Image Writer
    REG_SZ~winspool,Ne00:#2300
    isolation_writecopy HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\PrinterPorts
    Value=Microsoft Office Document Image Writer
    REG_SZ~winspool,Ne00:,15,45#2300
    isolation_writecopy HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows
    Value=Device
    REG_SZ~Microsoft Office Document Image Writer,winspool,Ne00:#2300

  27. Dean Flaming

    dietmarm-
    I don’t think I answered your specific issues.
    It sounds to me like you may have not selected customize and then selected “RUN ALL FROM MY COMPUTER” as shown in step 8.
    In what application are you pressing the F1 key and clicking the “Visual Basic” button?
    I tested the F1 feature in multiple apps within my ThinApp Office package and it worked every time.

  28. Dean Flaming

    Larry-
    First and foremost, you can contact VMware Support by phone (http://www.vmware.com/support/phone_support.html) or visit the VMware support site at http://support.vmware.com (see here – http://support.vmware.com/selfsupport/ – to create a web request).
    Provided your ThinApp maintenance is up to date (if you purchased ThinApp or View Premier within the last 12 months, it probably is), you can get support.
    I would also suggest checking to see the “Spool” folder (located within the “%SystemSystem%” folder) is not missing or not set to MERGED isolation. The “Spool” folder (and all subfolders within it) should be in all ThinApp packaged apps where you wish the user to be able to print.

  29. Jonathan Storey

    Hi, run into an interesting one – all to do with office help. Office was packaged on a winxp 32 bit machine & all aspects of the package work as intended on 32 bit based clients. If you run the app on a 64 bit client, majority of functions work as expected, however, f1 help fails with a CLView based error box & message along lines of CLView can’t display help. CLView cannot install the necessary files due to windows installer error 1619. Anyone else tried office 2007 captured on 32 bit, running on 64 bit & hit f1 help ?

  30. Mike

    This fixed it for me:
    http://communities.vmware.com/thread/175521
    We had this same issue for Office 2003 except that all Office programs would not print. To fix it I removed the following entries from the Current Users registry hive in my build directory.
    isolation_writecopy HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Devices
    Value=Microsoft Office Document Image Writer
    REG_SZ~winspool,Ne00:#2300
    isolation_writecopy HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\PrinterPorts
    Value=Microsoft Office Document Image Writer
    REG_SZ~winspool,Ne00:,15,45#2300
    isolation_writecopy HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows
    Value=Device
    REG_SZ~Microsoft Office Document Image Writer,winspool,Ne00:#2300

  31. james McEwen

    I’ve repackaged Office with 4.0.3 and I’m still getting the printing issue with Outlook, it says “No printers installed” I get the same issue with PowerPoint and Visio.
    I’m also having issues with using templates in Visio, where it crashes the program, and Publisher seems to error out as well.

  32. Stephan Neumeister

    We also have the printing issue. With the exeption of Word and OneNote all Office Application are refusing to use installed printers.
    Does anyone know a solution in the meantime for that?
    Is it a problem coming from any decribe modification and if yes, which one is causing this problem?

  33. Dean Flaming

    Mike posted this originally…
    http://communities.vmware.com/thread/175521
    We had this same issue for Office 2003 except that all Office programs would not print. To fix it I removed the following entries from the Current Users registry hive in my build directory.
    isolation_writecopy HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Devices
    Value=Microsoft Office Document Image Writer
    REG_SZ~winspool,Ne00:#2300
    isolation_writecopy HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\PrinterPorts
    Value=Microsoft Office Document Image Writer
    REG_SZ~winspool,Ne00:,15,45#2300
    isolation_writecopy HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows
    Value=Device
    REG_SZ~Microsoft Office Document Image Writer,winspool,Ne00:#2300
    -Dean

  34. Stephan Neumeister

    Guess I have a solution for the printer problem:
    Just install the Office or Office applkation during the snapshot process on a OS with at least one installed printer and open the application once.
    For now I don’t know, if both actions are necessary.

  35. Stephan Neumeister

    Printer Problems:
    Just install a printer before installing Office 2007 for the snapahot should solve the problem.

  36. universe

    what about thinapp office 2007 and mathtype 6.5c? after successfull thinapp,
    when clicking in mathtype inline tab it gives the following msg “mathtype preferences problem- there was a problem sending your equation preferences for this document to mathtype. this equation will use mathtype’s “new equation” preferences” and after that while trying to close office it just hangs, and also it cannot associate .docx files with “open with…..”

  37. universe

    what about thinapp office 2007 and mathtype 6.5c? after successfull thinapp,
    when clicking in mathtype inline tab it gives the following msg “mathtype preferences problem- there was a problem sending your equation preferences for this document to mathtype. this equation will use mathtype’s “new equation” preferences” and after that while trying to close program it just hangs, and also it cannot associate .docx files with “open with…..” “microsoft word 2007”

  38. universe

    After successful thinapp table curve 2d v5.01 it clearly runs on a clean vm winxp installed snapshot,
    but while trying to run on host winxp os it gives msg “no license dll found” “the DLL validatedll.dll or sacwd32.dll is missing or corrupted”.

  39. James Mikelis

    1. Send To Mail Recepient Command line option fails
    2. Can’t open Excel, PPT, Word apps from within an email msg by double clicking on it even though i have those apps installed.
    3. URL links in a mail msg work on a system where i already have outlook 2003 installed but fails on a system with only the Outlook 2007 thinapp running.

  40. A Dovi

    For the OneNote problem this is because you have removed WISPTIS.exe
    you should have
    %SystemSystem%\INKED.DLL
    %SystemSystem%\WISPTIS.EXE
    and a few others to have OneNote running smoothly, otherwise it will start looking for installer files and you will experience bugs.

  41. Gary Porritt

    Hi first, thanks for this information it has been really useful.
    I am having trouble with a fully installed version of office 2003 once I have installed the thinapp 2007.
    When I try and run a any of the office 2003 programs after the install, it requires me to insert the 2003 office disk so it can reinstall files from pa561401.cab. Any advice on why this might be happening would be much appreciated.

  42. Dean Flaming

    Is this before or after you register the ThinApp’ed Office ’07? I suspect it’s after…and if true, it means you are potentially re-registering something that Office 2003 needs to see in order to work properly.
    Remember, ThinApp packages can register the following:
    Shortcuts
    File Type Associations
    COM Objects
    All of the above items which the ThinApp package in question is registering can be seen within the PACKAGE.INI underneath the respective entry points.
    As an example, I’ve posted the Word 2007 Entry Point from my Office 2007 ThinApp Project below:
    [Microsoft Office Word 2007.exe]
    Shortcut=Microsoft Office Enterprise 2007.dat
    Source=%ProgramFilesDir%\Microsoft Office\Office12\WINWORD.EXE
    ;Icon=%SystemRoot%\Installer\{90120000-0030-0000-0000-0000000FF1CE}\wordicon.exe
    FileTypes=.doc.dochtml.docm.docx.dot.dothtml.dotm.dotx.rtf.wbk
    Shortcuts=%Programs%\Microsoft Office
    ObjectTypes=Word.Application;Word.Application.12;Word.Application.8;Word.Backup.8;Word.Basic;Word.Basic.8;Word.Basic.9;Word.Document;Word.Document.12;Word.Document.6;Word.Document.8;Word.DocumentMacroEnabled;Word.DocumentMacroEnabled.12;Word.Picture;Word.Picture.6;Word.Picture.8;Word.RTF.8;Word.Template;Word.Template.12;Word.Template.8;Word.TemplateMacroEnabled;Word.TemplateMacroEnabled.12;Word.Wizard.8;WordDocument;wordhtmlfile;wordhtmltemplate;wordxmlfile

  43. Arnaud D

    For the OneNote problem mentionned 2 posts above, you SHOULDN’T remove %SystemSystem%\WISPTIS.exe and all other files near, OneNote will need them
    The cleaner way to disable WISPTIS.exe without breaking OneNote is to go in Control Panel > Regional Settings > Languages Tab > click “Details” button > Delete All new “Ink” values added up your keyboard > Advanced Tab > CHECK “Turn off advanced text services”
    WISPTIS.exe will be disabled safely, it will be then configured as a Manual service, OneNote will find and use it when required and it won’t spawn as a useless daemon when you don’t need it.

  44. Arnaud D

    For the OneNote problem mentionned 2 posts above, you SHOULDN’T remove %SystemSystem%\WISPTIS.exe and all other files near, OneNote will need them
    The cleaner way to disable WISPTIS.exe without breaking OneNote is to go in Control Panel > Regional Settings > Languages Tab > click “Details” button > Delete All new “Ink” values added up your keyboard > Advanced Tab > CHECK “Turn off advanced text services”
    WISPTIS.exe will be disabled safely, it will be then configured as a Manual service, OneNote will find and use it when required and it won’t spawn as a useless daemon when you don’t need it.

  45. Dennis

    I have created a new Vm workstation for xp. I would like to load office 2007. Do I have join the vm to my domain prior to doing this image creation?

  46. Franck

    Hi,
    great post.
    Is Office 2007 in ThinApps aware of any Office 2007 GPOs that I assign on e.g. Domain our Computer OU level?
    Thanks,
    Franck

  47. Dean Flaming

    Any ThinApp packaged app can be made to honor GPO settings. The way to make this work is by removing the GPO effected registry entries and setting the parent registry keys to either WRITECOPY or MERGED so the ThinApp packaged app will inherit the settings from native registry – which is getting its settings from the GPO.

  48. SkH

    Hello, I’m having problems with the ThinApp’d Office 2007.
    Wherever I open it in my school’s computer, when I try to copy the selected text, the Windows Installer thing comes up… why? How to fix this?
    I have already done everything described…

  49. SkH

    Hello, I have a problem with the ThinApp’d Office 2007 in my school only. When I open it, and copy the selected text, Windows Installer comes up.
    Why? How to fix this?
    I couldn’t reproduce the problem in my PC.

  50. Dean Flaming

    @SkH Sounds like the systems you receive the issue on don’t have all the appropriate things your ThinApp’ed Office packaged needs.
    For testing purposes, I’d take an image of the system where the issue occurs and stick it into VMware Workstation.
    Also, I’d suggest building a clean VM of your baseline OS without any additional updates and test within it.
    Bottom line, remember ThinApp uses that Tried and True Delta Snapshot technology so if something already existed on the system you captured Office on, then that same something must exist on all other systems for the ThinApp’ed Office to work properly. An example is your own system where the package doesn’t have the issue.
    Hope this helps….also, don’t forget you can always contact VMware Support for assistance. See http://support.vmware.com for assistance in contacting VMware Support.

  51. Alex Gomes

    Hey guys – has anyone been able to successfully ThinApp MS Office Access 2007? on its own or as part of MS Office? We are running into an issue where after running the packaged Access 2007, it prompts for the MSI (ProPlusWW.msi) – I have even tried leaving all the files untouched before building i.e the MSOCache folder is still there with all the MSI files.

  52. Dean Flaming

    This sounds similar to an issue another customer (we’ll call the customer “Stephanie”) found in packaging Access 2003.
    They were getting “Error 1719: The Windows Installer Service could not be accessed. …” when attempting to run Access 2003 after capturing it.
    The resolution was to modify the HKEY_LOCAL_MACHINE.TXT file and add the following:
    isolation_full HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer
    Value=ImagePath
    REG_EXPAND_SZ~”%SystemSystem%\msiexec.exe” /V
    I’ve not tested this but your posting and the email containing this info came in right around the same time so I figured I’d pass this along.

  53. Dean Flaming

    A customer recently responded via email about an issue found in packaging Access 2003.
    They were getting “Error 1719: The Windows Installer Service could not be accessed. …” when attempting to run Access 2003 after capturing it.
    The resolution was to modify the HKEY_LOCAL_MACHINE.TXT file and add the following:
    isolation_full HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer Value=ImagePath REG_EXPAND_SZ~”%SystemSystem%\msiexec.exe” /V
    I’ve not tested this so please take appropriate steps prior to implementing in your environment. 😉

  54. Brett

    I found that if delete the MSOCACHE files before launching each application the package will throw an error stating files are missing.

  55. John

    Using ThinApp 4.5, we are experiencing the HELP issue. We packaged on 32bi XP. Running on 32 bit XP works fine. Running on 64 bit Win7 fails with the CLview error – same as Jonathan above. Is there a known fix for this?

  56. Dean Flaming

    @John
    Interesting, I’m not seeing “Jonathan’s” comment.
    Either way, as this issue sounds specific to differences with XP and Win 7, please open a support ticket so our engineers may properly track this issue and potentially provide any guidance and/or resolutions.
    To open a Support Ticket, contact VMware support on the web at http://www.vmware.com/support or by phone at 1-877-4-VMWARE (1-877-486-9273) or 1-650-475-5345.
    Thanks!

  57. Xed

    This is slightly off-topic but, but how does one go about this for Office 2010?
    I successfully created a package but when I try to run it, Office 2010 is no longer activated and requires the original setup files. (Located in MSOCache)

  58. Thomas J

    I’m having trouble with the Japanese IME when running a thinapped English Office 2007 (captured with ThinApp 4.6 in an English XP SP3 VM) on Windows 7. The IME works fine when I run the package on XP, but I input only gibberish instead of Japanese when I use the Windows 7 IME. Everything else seems OK on both XP and Windows 7, even the Japanese MUI.
    Any ideas about this?

  59. Dean Flaming

    @Thomas J – This sounds as if it could be any number of things from isolation settings to potentially a glitch with double-byte characters. Please contact VMware support on the web at http://www.vmware.com/support or by phone at 1-877-4-VMWARE (1-877-486-9273) or 1-650-475-5345 and open a support ticket on this issue. If you have troubles doing so or are evaluating ThinApp (and don’t have a support agreement), please contact your VMware Account Rep or SE. If all else fails, please direct message me by clicking on my name and sending me an email so we can get you in contact with the proper person. Thanks!

  60. Calvin Woods

    Hi there,
    Great document. I have run into a problem with Outlook 2007. If I log into one computer as User1 Outlook works fine, if I log into the same computer as User2 I cannot open Outlook. The issue is because the Sandbox is computer based and not user based. How would one get around this?? Please help!

  61. Dean Flaming

    @Calvin Woods
    Apologies on the delay… To answer your question you can place the sandbox in virtually any location (so long as the location is accessible and the user has complete permissions to that location) using a number of different means.
    Rather than typing them all out here, I would suggest the following reading in the online help manual as it fully discusses how the ThinApp Sandbox is located and – through this discussion – how you can configure the location of the sandbox for the specific application, all applications per user/per system/per environment variable/etc. to be wherever you need them to be.
    http://pubs.vmware.com/thinapp4/help/wwhelp/wwhimpl/js/html/wwhelp.htm?href=sandbox_search_order.html
    When viewing the above link, also make sure to look in the left-hand pane and see the section on “Controlling the sandbox location”.
    Additionally, you may also wish to review the article on the Package.ini file.
    http://blogs.vmware.com/thinapp/2009/12/the-packageini-file-explained.html

  62. Matthias Wohlgemuth

    I did thinapp Office 2007. Everything seems to work fine except one thing in Outlook:
    If I start Outlook the first time it asks me to configure an e-mail account. If I choose “no” and check the box for “proceed without e-mail support” outlook dos start but it crashes during using all the time.

  63. TobyFruthParsons

    I followed these instructions to capture and build Visio 2007 SP3. One issue so far. I captured the install of the Office 2007 shared components, like Graph and picture manager, etc. During that same session I installed Visio 2007 SP3. Prior to post scan I opened Visio and made sure I could insert a chart. I saved the diagram. I finished the capture, did all the pre-build changes, built the application.
    I rolled back the packaging VM, installed the Visio 2007 MSI, and created a new diagram, inserting a chart. This works fine. I saved the diagram, closed Visio 2007 ThinApp. I open Visio 2007 ThinApp and open the diagram I just created and the chart isn’t visible. Graph.exe should be called when Excel isn’t present (which it isn’t.)

  64. Dean Flaming

    @Jason – This is current but please make certain to read all of the comments as this is a living document. There were a number of suggested resolutions for different issues in the comments.

  65. Farhad

    Hi, there seems to be no more posts since 2009. Has Priting from Outlook been resolved, can someone please confirm. Thank you, Farhad

Comments are closed.