• Author / Uploaded
• roni_wiharyanto

• Categories
• Registro de Windows
• Microsoft Outlook
• Archivo de computadora
• Microsoft Office
• Microsoft Windows

Citation preview

VMware: VMware ThinApp Blog: Step by Step Instructions on How to...

http://blogs.vmware.com/thinapp/2008/10/how-to-thinap-1.html

VMware ThinApp Blog (http://blogs.vmware.com/thinapp/) Creating Windows Entry Points for Troubleshooting ThinApp Packages (http://blogs.vmware.com/thinapp/2008/10/creating-window.html) | Main (http://blogs.vmware.com/thinapp/) |

Excel DDE Workaround (http://blogs.vmware.com/thinapp/2008/10/excel-dde-worka.html)

October 08, 2008

Step by Step Instructions on How to ThinApp Microsoft Office 2007 (http://blogs.vmware.com/thinapp/2008/10/how-to-thinap-1.html)

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 of 13

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. 22/06/2010 8:11

VMware: VMware ThinApp Blog: Step by Step Instructions on How to...

http://blogs.vmware.com/thinapp/2008/10/how-to-thinap-1.html

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.

2 of 13

22/06/2010 8:11

VMware: VMware ThinApp Blog: Step by Step Instructions on How to...

http://blogs.vmware.com/thinapp/2008/10/how-to-thinap-1.html

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.

3 of 13

22/06/2010 8:11

VMware: VMware ThinApp Blog: Step by Step Instructions on How to...

http://blogs.vmware.com/thinapp/2008/10/how-to-thinap-1.html

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

4 of 13

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.

2.

Set your Access Denied message if using groups.

Select the default sandbox location

Click NEXT when ready. 6.

Now you need to select the default Isolation Mode for the packaged application. 22/06/2010 8:11

VMware: VMware ThinApp Blog: Step by Step Instructions on How to...

5 of 13

http://blogs.vmware.com/thinapp/2008/10/how-to-thinap-1.html

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. 22/06/2010 8:11

VMware: VMware ThinApp Blog: Step by Step Instructions on How to...

10. 20.

6 of 13

http://blogs.vmware.com/thinapp/2008/10/how-to-thinap-1.html

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.

Click FINISH when done.

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.

2.

3.

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

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

HKEY_CURRENT_USER.TXT Outlook Secure Temp folder modifications: 1.

4.

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.

Office 2007 Modifications: 22/06/2010 8:11

VMware: VMware ThinApp Blog: Step by Step Instructions on How to... 1.

http://blogs.vmware.com/thinapp/2008/10/how-to-thinap-1.html

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.

2.

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

Posted by Dean Flaming on October 8, 2008 in Applications (http://blogs.vmw are.c om/thinapp/applic ations/) , Tips (http://blogs.vmw are.c om/thinapp/tips/) | Permalink (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-1.html) |

(http://w w w .addthis.c om/bookmark.php)

TrackBack TrackBack URL for this entry: http://www.typepad.com/services/trackback/6a00d8341c328153ef0105352dae58970c Listed below are links to weblogs that reference Step by Step Instructions on How to ThinApp Microsoft Office 2007 (http://blogs.vmware.com/thinapp /2008/10/how-to-thinap-1.html) :

Comments

Hi, How to proceed with future patches released by MS?

7 of 13

22/06/2010 8:11

VMware: VMware ThinApp Blog: Step by Step Instructions on How to...

http://blogs.vmware.com/thinapp/2008/10/how-to-thinap-1.html

Is there a way to link the package with Microsoft update? Regards Posted by: Olivier | October 15, 2008 at 02:00 AM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-1.html?c id=134794333#c omment-6a00d8341c 328153ef0105358baa8b970c )

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 (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. Posted by: Dean Flaming (http://profile.typepad.c om/1222903144s22369) | October 15, 2008 at 08:55 AM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap1.html?c id=134830583#c omment-6a00d8341c 328153ef0105358c 7880970c )

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? Posted by: Lucas | October 28, 2008 at 07:51 AM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-1.html?c id=136703007#c omment-6a00d8341c 328153ef010535c 532aa970c )

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. Posted by: Lucas | November 02, 2008 at 06:38 AM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-1.html?c id=137370067#c omment-6a00d8341c 328153ef010535c c 0196970b)

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. Posted by: Dean Flaming (http://profile.typepad.c om/1222903144s22369) | November 02, 2008 at 10:09 AM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap1.html?c id=137387339#c omment-6a00d8341c 328153ef010535d2af25970c )

Thanks a lot! I will try it. Posted by: Lucas | November 02, 2008 at 10:13 PM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-1.html?c id=137452337#c omment-6a00d8341c 328153ef010535d410ee970c )

8 of 13

22/06/2010 8:11

VMware: VMware ThinApp Blog: Step by Step Instructions on How to...

http://blogs.vmware.com/thinapp/2008/10/how-to-thinap-1.html

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 Posted by: Kris | November 14, 2008 at 08:18 AM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-1.html?c id=139134694#c omment-6a00d8341c 328153ef010535f569b0970c )

KrisYes 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. Posted by: Dean Flaming (http://profile.typepad.c om/1222903144s22369) | November 14, 2008 at 02:51 PM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap1.html?c id=139185212#c omment-6a00d8341c 328153ef010535eff3d5970b)

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? Posted by: Paolo | November 17, 2008 at 11:57 AM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-1.html?c id=139454556#c omment-6a00d8341c 328153ef010535fc dc 75970c )

PaoloYou 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 Posted by: Dean Flaming (http://profile.typepad.c om/1222903144s22369) | November 17, 2008 at 01:30 PM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap1.html?c id=139466744#c omment-6a00d8341c 328153ef010535fdff40970c )

Is it safe to say that in your point #20 we can delete all of those folders for any application we thinapp? Posted by: Chris | November 28, 2008 at 09:33 AM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-1.html?c id=140710532#c omment-6a00d8341c 328153ef010536296b16970c )

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

9 of 13

22/06/2010 8:11

VMware: VMware ThinApp Blog: Step by Step Instructions on How to...

http://blogs.vmware.com/thinapp/2008/10/how-to-thinap-1.html

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. :-) Posted by: Dean Flaming (http://profile.typepad.c om/1222903144s22369) | November 28, 2008 at 09:58 PM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap1.html?c id=140750188#c omment-6a00d8341c 328153ef0105362a4baa970c )

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. Posted by: Alex Gomes | December 05, 2008 at 10:27 AM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-1.html?c id=141537264#c omment-6a00d8341c 328153ef010536342a15970b)

AlexThanks 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 Posted by: Dean Flaming (http://profile.typepad.c om/1222903144s22369) | December 05, 2008 at 10:49 AM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap1.html?c id=141540192#c omment-6a00d8341c 328153ef0105363437bf970b)

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. Posted by: DaveW | January 08, 2009 at 10:43 PM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-1.html?c id=6a00d8341c 328153ef010536bfb2f9970c #c omment6a00d8341c 328153ef010536bfb2f9970c )

ThinApp 4.0.1 resolves some of the isolation mode issues so you don't have to manually specify them in ##attributes Posted by: Jonathan Hemming | January 13, 2009 at 01:51 PM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-1.html?c id=6a00d8341c 328153ef010536c d9a95970c #c omment6a00d8341c 328153ef010536c d9a95970c )

DaveW- I just wanted to let you know I saw your request. I'll test the OneNote issue and post my results as soon as I get a chance to. Posted by: Dean Flaming (http://profile.typepad.c om/1222903144s22369) | January 15, 2009 at 01:30 PM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap1.html?c id=6a00d8341c 328153ef010536c b73b1970b#c omment-6a00d8341c 328153ef010536c b73b1970b)

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. Posted by: Dean Flaming (http://profile.typepad.c om/1222903144s22369) | January 15, 2009 at 01:32 PM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-

10 of 13

22/06/2010 8:11

VMware: VMware ThinApp Blog: Step by Step Instructions on How to...

http://blogs.vmware.com/thinapp/2008/10/how-to-thinap-1.html

1.html?c id=6a00d8341c 328153ef010536c b758c 970b#c omment-6a00d8341c 328153ef010536c b758c 970b)

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-006E0409-0000-0000000FF1CE} folders. Posted by: Phil Helmling | January 21, 2009 at 03:11 AM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-1.html?c id=6a00d8341c 328153ef010536e0df9c 970b#c omment6a00d8341c 328153ef010536e0df9c 970b)

Hi, Dean. Did you get a chance to look into the OneNote 2007 thinapp problem? Looking forward to seeing a fix here. Posted by: DaveW | January 28, 2009 at 06:57 PM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-1.html?c id=6a00d8341c 328153ef010536ffdf3b970c #c omment6a00d8341c 328153ef010536ffdf3b970c )

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? Posted by: Anthony | January 30, 2009 at 02:41 PM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-1.html?c id=6a00d8341c 328153ef01053704a5ba970c #c omment6a00d8341c 328153ef01053704a5ba970c )

TO CORRECT CLIP ART PROBLEMS... Greetings I'm Paul W.

As quoted by: irishmn76 Web Link: https://thinstall.com/thintalk/viewtopic.php?t=361&highlight=&sid=40efea5b29ac91461be1db10292844db (https://thinstall.com/thintalk /viewtopic.php?t=361&highlight=&sid=40efea5b29ac91461be1db10292844db)

To correct clipart problems... 1. create your Prescan. 2. Install... A) .Net 2.0 B) Windows Installer, (I used Installer 4.5) C) Office 2007 3. Create your Postscan, and that should correct the problem concerning the Clip Art.

11 of 13

22/06/2010 8:11

VMware: VMware ThinApp Blog: Step by Step Instructions on How to...

http://blogs.vmware.com/thinapp/2008/10/how-to-thinap-1.html

Cheers, Paul W. Posted by: Paul W. | February 25, 2009 at 06:30 AM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-1.html?c id=6a00d8341c 328153ef011168973ab9970c #c omment6a00d8341c 328153ef011168973ab9970c )

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? Posted by: Erik Jongebloed | February 27, 2009 at 06:45 AM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-1.html?c id=149869611#c omment6a00d8341c 328153ef01127911205c 28a4)

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. Posted by: James | March 04, 2009 at 07:11 AM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-1.html?c id=6a00d8341c 328153ef011168a94f14970c #c omment6a00d8341c 328153ef011168a94f14970c )

We are also running into the printing issue after the recommended customizations. Posted by: Jason Shroll | March 24, 2009 at 07:25 AM (http://blogs.vmw are.c om/thinapp/2008/10/how -to-thinap-1.html?c id=6a00d8341c 328153ef01156f46822e970b#c omment6a00d8341c 328153ef01156f46822e970b)

Verify your Comment Previewing your Comment Posted by: |

This is only a preview. Your comment has not yet been posted. Post Edit Your comment could not be posted. Error type: Your comment has been posted. Post another comment (javascript:void 0;) The letters and numbers you entered did not match the image. Please try again. As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments. Having trouble reading this image? View an alternate. (#comment-captcha)

Continue

Post a comment If you have a TypeKey or TypePad account, please Sign In (https://www.typekey.com/t/typekey/login?v=1.0&t=02f7e81a7fc26ef8af6c2535a10e8f9d1385a082&lang=en_US& _return=http%3A%2F%2Fblogs.vmware.com%2Fthinapp%2F2008%2F10%2Fhow-to-thinap-1.html&_portal=typepad) .

Name: Email Address: (Not displayed with comment.) URL:

12 of 13

22/06/2010 8:11

VMware: VMware ThinApp Blog: Step by Step Instructions on How to...

http://blogs.vmware.com/thinapp/2008/10/how-to-thinap-1.html

Remember personal info?

Comments: Preview

Post

Copyright © 2010 VMware, Inc. All rights reserved. rss feed (http://vmware.simplefeed.net/subscription)

13 of 13

22/06/2010 8:11