Open the core product folder and locate the Config.xml file. For example, if my Microsoft Office 2010 media was Professional Plus, the folder name would be “ProPlus.WW”.Ĩ. By default, the Microsoft Office 2010 Config.xml file is stored in the core product folder in the Microsoft Office 2010 installation media. Explore the Office 2010 installation media on the capture machine and you should see a folder named similar to “core_product_folder_name.WW folder”. In order for Office 2010 to activate correctly we need to edit the Config.xml file and specify your Multiple Activation Key (MAK). Open a new command prompt window and type the following command and press return:Ĭ:\WINDOWS\Microsoft.NET\Framework\v7\ngen.exe executequeueditemsħ. NET installation generates the mscorsvw.exe process that continues for an extended period, we need to stop the process with the ngen.exe tool. When the pre-scan is complete, on the Install Application page of the Setup Capture wizard, minimize the wizard and install Microsoft. Run the Setup Capture wizard, start and complete the pre-scan process.ĥ. Install VMware ThinApp on capture machine.Ĥ. Ensure you have internet access on the ThinApp capture machine.ģ. NET Framework 3.5 and Microsoft Office 2010 installation files to the ThinApp capture machine.Ģ. The following ThinApp capture has been performed on a fresh installation of Windows XP SP3 with VMware ThinApp 4.6.1.ġ. This article has been written using information for VMware sources and my own experience. After successfully being able to create a full Microsoft Office 2010 suite ThinApp, I have written a setup guide to detail the steps that had to be taken in order to get all Office applications working and to allow standard windows users (non local administrators) to activate office when launching the ThinApp for the first time.
0 Comments
Leave a Reply. |