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.

• Visio 2007 Portable Mega

Java Project Tutorial - Make Login and Register Form Step by Step Using NetBeans And MySQL Database - Duration: 3:43:32. 1BestCsharp blog 3,269,448 views.

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. 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.

Start with a cleanly built Windows XP VM. NOTE: Use the 'How to make a ThinApp Application' as a reference. Run a ThinApp Pre-installation Setup Capture. Close the ThinApp Pre-installation Setup Capture using the red 'X' in the upper-right corner. Launch the Microsoft Office 2007 Setup. Input the valid Microsoft Office 2007 Volume License Key.

Accept the EULA. At the 'Choose the installation you want' screen, select the CUSTOMIZE button.

On the INSTALLATION OPTIONS tab, click the top level drop down to the left of MICROSOFT OFFICE and select RUN ALL FROM MY COMPUTER. All boxes should now be white. Click the INSTALL NOW button to continue.

Visio 2007 Portable Mega

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. 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. On the Microsoft Office site, click the DOWNLOADS link. On the Microsoft Office Download page, click the 'Office Update' link. On the Microsoft Office Update page, click the CONTINUE button if you get the Genuine Microsoft Office checker. Click the CONTINUE button once you get the Genuine Microsoft Office banner. 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 and following the directions in steps 12 and 13. After all updates are completed, reboot the VM to ensure proper updates occur.

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.

Click ADD to add in any groups desired. Set your Access Denied message if using groups. Select the default sandbox location Click NEXT when ready. Now you need to select the default Isolation Mode for the packaged application. Typically, most applications will be using MERGED for an isolation mode. 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. At this point, your package will be created based upon the differences between the pre-installation scan and post-installation scan. 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. 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. If you select BUILD NOW, your project will be packaged into an executable or executables (depending upon the number of entry points selected). If you select FINISH, the Setup Capture window will be closed. Click FINISH when done. 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. Change the isolation settings in the ##Attributes.INI file to WriteCopy in the following folders:.%ProgramFilesDir% Common Files Microsoft Shared INK.%ProgramFilesDir% Common Files Microsoft Shared Office11.%ProgramFilesDir% Common Files Microsoft Shared Office11 1033.%ProgramFilesDir% Microsoft Office NOTE: Depending on your language version, you may need to modify the language folder as well.%ProgramFilesDir% Common Files Microsoft Shared Office11 1033 English Language Version Code = 1033. 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 HKEYLOCALMACHINE.txt file and search for these keys and modify the from isolationmodefull to isolationmodewritecopy.

HKEYLOCALMACHINE SOFTWARE Microsoft Windows CurrentVersion Installer UserData S-1-5-18 Components 379E92CC2CB71D119A12000A9CE1A22A. HKEYLOCALMACHINE SOFTWARE Microsoft Windows CurrentVersion Installer UserData S-1-5-18 Components 1650EACF3C291D794C4E25. 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. 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 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!. 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. 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. 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?. 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?. 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. Isolationwritecopy HKEYCURRENTUSER Software Microsoft Windows NT CurrentVersion Devices Value=Microsoft Office Document Image Writer REGSZwinspool,Ne00:#2300 isolationwritecopy HKEYCURRENTUSER Software Microsoft Windows NT CurrentVersion PrinterPorts Value=Microsoft Office Document Image Writer REGSZwinspool,Ne00:, isolationwritecopy HKEYCURRENTUSER Software Microsoft Windows NT CurrentVersion Windows Value=Device REGSZMicrosoft Office Document Image Writer,winspool,Ne00:#2300. Larry- First and foremost, you can contact VMware Support by phone or visit the VMware support site at (see here – – 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. 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?. Mike This fixed it for me: 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. Isolationwritecopy HKEYCURRENTUSER Software Microsoft Windows NT CurrentVersion Devices Value=Microsoft Office Document Image Writer REGSZwinspool,Ne00:#2300 isolationwritecopy HKEYCURRENTUSER Software Microsoft Windows NT CurrentVersion PrinterPorts Value=Microsoft Office Document Image Writer REGSZwinspool,Ne00:, isolationwritecopy HKEYCURRENTUSER Software Microsoft Windows NT CurrentVersion Windows Value=Device REGSZMicrosoft Office Document Image Writer,winspool,Ne00:#2300.

Mike posted this originally 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.

Isolationwritecopy HKEYCURRENTUSER Software Microsoft Windows NT CurrentVersion Devices Value=Microsoft Office Document Image Writer REGSZwinspool,Ne00:#2300 isolationwritecopy HKEYCURRENTUSER Software Microsoft Windows NT CurrentVersion PrinterPorts Value=Microsoft Office Document Image Writer REGSZwinspool,Ne00:, isolationwritecopy HKEYCURRENTUSER Software Microsoft Windows NT CurrentVersion Windows Value=Device REGSZMicrosoft Office Document Image Writer,winspool,Ne00:#2300 -Dean. @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 for assistance in contacting VMware Support. 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 HKEYLOCALMACHINE.TXT file and add the following: isolationfull HKEYLOCALMACHINE SYSTEM CurrentControlSet Services MSIServer Value=ImagePath REGEXPANDSZ”%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.

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 HKEYLOCALMACHINE.TXT file and add the following: isolationfull HKEYLOCALMACHINE SYSTEM CurrentControlSet Services MSIServer Value=ImagePath REGEXPANDSZ”%SystemSystem% msiexec.exe” /V I’ve not tested this so please take appropriate steps prior to implementing in your environment.

@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 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. @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. 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. 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.).