Video Screencast Help

How to Virtualize Microsoft Office 2010

Created: 05 Jul 2011 • Updated: 25 Apr 2013 | 5 comments
Language Translations
Dwight Tanner's picture
+4 4 Votes
Login to vote

An updated guide for packing Office 2010 can be found here.  It contains updated information on how to remove the Office Licensing Service from a layer and how to install that service to it's own layer or to the base.

This guide provides a collection of best practices when you virtualize Microsoft Office 2010. Office is one of the most virtualized applications with Symantec Workspace Virtualization. However, certain issues arise due to the diverse ways that customers virtualize Office along with the Microsoft licensing features unique to Office 2010. These instructions help you navigate these realities through three standard use cases.

This guide is meant to document specific steps for Office 2010. However, additional information is included such as how to use virtualization to run two versions of Office concurrently.

Furthermore, this guide is not intended to present all aspects of packaging and deploying in Wise Virtual Composer (WVC). Instead, the guide provides information on the unique aspects and necessary steps for packaging Office 2010.


Introducing virtualized Microsoft Office 2010

  • About virtualized Microsoft Office
  • Use cases

Chapter 2: Packaging Microsoft Office

  • About preparing a packaging system
  • About packaging Office 2010
  • About Visual C++ runtime dependencies

Chapter 3: Preparing to deploy Office 2010

  • Licensing virtualized Microsoft Office 2010 with a KMS or MAK
  • Setting up a service in a layer
  • Rearming the 30-day token renew timer
  • Running Office 2010 with multiple layers
  • Running Office 2010 with MUI layers

Chapter 4: Configuring additional options

  • Optimizing virtualized Office 2010
  • Configuring administrator permissions
  • About running two versions of Office

Comments 5 CommentsJump to latest comment

CableGuy41's picture

thanks for sharing.


Do not forget to mark a SOLUTION

Login to vote
EddieNYC's picture

As the guide was partially based on my article:

I just need to comment one thing that was missing on my original post that should be added to the PDF here...  (As I find new things, I'll post them in my original article in the above URL).

A few people pinged me about trust center sometimes takes awhile to open (30 seconds).  To fix this, simply disable the research options by adding these keys to the Office 2010 layer (keep note that it's both on the user template hive and local machine hive):







"Rather fail with honor than succeed by fraud." - Sophecles

Login to vote
EddieNYC's picture

Noticed a bug that wasn't picked up because the test machine was always in English and not using the language bar.  After putting this on a machine that uses IME multilanguage inputs the layer drops Chinese (simplified, traditional), Korean, and Japanese to the added keyboards for some weird reason.  This is irritating to the end user if they don't need these languages and only use say French and English.  The source of these is coming from the proofing tools and proofing tools SP1 that get installed to the layer and leave junk all over the place and for some reason leave these 3 countries keyboards enabled.

Basically what we need to do is pull the keyboards from the preloaded keyboards and disable the preload of the IME's for those country codes.

For reference, you can pull the full list of country codes from your own registry which list every country code here:
HK Local Machine\System\CurrentControlSet\Control\Keyboard Layouts\

In the layer remove from country codes from HK Current user\keyboard layout\preload
804 - China Simplified
404 - China Traditional
411 - Japan
412 - Korea

This is not enough to stop the preloading.  You need to go to all the CTF\TIP for each language and disable them... (also in current user)
[HKEY_LOCAL_MACHINE\Software\Microsoft\CTF\TIP\{GUID}\LanguageProfile\0x00000404\{GUID}] (replace 40 with other country code)
- set value: Enable = 0

Also in Current user, you need to set all the preloads to 0 for any IME* library.

Don't worry, this only removes it from the Office 2010 layer, the keyboard will still remain on the OS level for that user.  Also if you're using MUI's in a separate layer, it'll take care of the keyboard localization nicely.  This is only for your main office 2010 layer so it will only show up in English as a standard.

Below is what you can paste into a reg file, then import into the layer (don't run in the layer, go to the properties, registry and import the file), as these are the changes I made to fix this.  (note while [-HKEY\etc] will delete a key, apparently Value = "-" does not.  It will actually set the value to a dash!  Might be a SWV bug, so that's why I just simply wiped the hive and populated back the English).

Windows Registry Editor Version 5.00













[-HKEY_USERS\USER_TEMPLATE\Keyboard Layout\Preload]
[HKEY_USERS\USER_TEMPLATE\Keyboard Layout\Preload]





















"Rather fail with honor than succeed by fraud." - Sophecles

Login to vote
Thriymapagan's picture


We have virtualized the MS-Access-2010 only. When we launch the other components like (Work, Excel), It is going to Self Repair.
We followed the below steps

Go to HKLM\System\CurrentControlSet\services\FSLX\Parameters\FSL

Navigate to the ReadOnly # folder for your Office 2003 (or Office 2007 or whatever stand alone component)

Create a multistring value called "IsolationRules"

Cut and paste the following to notepad (the spaces are actual tabs, there are no spaces, this is important)

*\msaccess.exe BASE 0x0002 \REGISTRY\* * 50cfaaa9-258a-4bd2-87d6-b1bb5d2a3f99
*\msaccess.exe 50cfaaa9-258a-4bd2-87d6-b1bb5d2a3f99 0x0002 \REGISTRY\HKEY_CLASSES_ROOT\* * BASE
*\excel.exe BASE 0x0002 \REGISTRY\* * 50cfaaa9-258a-4bd2-87d6-b1bb5d2a3f99
*\excel.exe 50cfaaa9-258a-4bd2-87d6-b1bb5d2a3f99 0x0002 \REGISTRY\HKEY_CLASSES_ROOT\* * BASE
*\powerpnt.exe BASE 0x0002 \REGISTRY\* * 50cfaaa9-258a-4bd2-87d6-b1bb5d2a3f99
*\powerpnt.exe 50cfaaa9-258a-4bd2-87d6-b1bb5d2a3f99 0x0002 \REGISTRY\HKEY_CLASSES_ROOT\* * BASE
*\winword.exe BASE 0x0002 \REGISTRY\* * 50cfaaa9-258a-4bd2-87d6-b1bb5d2a3f99
*\winword.exe 50cfaaa9-258a-4bd2-87d6-b1bb5d2a3f99 0x0002 \REGISTRY\HKEY_CLASSES_ROOT\* * BASE

It is not working. Kindly guide us

Login to vote
SUNNY1122's picture

Hello Guys,

I was trying to vitalizing Microsoft office 97 (Italian version - Need Access 97 only) for windows 7. Looks like the vitalized layer is working fine on XP SP3 machine but when trying to import & copy the same layer on Win 7 machine, Its just not working. By any change do you guys have vitalized Office 97 or Access 97 ( English or Italian ) layer which works on Win 7. Any kind of inputs are welcomed.

Thanks & Appreciate your help in advance.

Login to vote