Prescriptive Guidance for Sequencing Office 2010 in App-V 4.6 SP1


Virtualizing Microsoft Office 2010 using Microsoft Application Virtualization (App-V) is a common task in many App-V environments.  This document describes a well-defined series of steps designed to aid customers in successfully sequencing Microsoft Office 2010.

This document guides you through the process of sequencing Office 2010 using the App-V 4.6 SP1 sequencer. If you are using the App-V 4.6 sequencer (i.e App-V 4.6 with no service pack), please follow this document instead: Prescriptive guidance for sequencing Office 2010 in Microsoft App-V.

IMPORTANT: Before starting to sequence, we strongly suggest to read this guide completely in order to understand all of the configuration options available.


You will need the following software to use this guide:

  • Microsoft Application Virtualization version 4.6 SP1:  The App-V 4.6 SP1 Sequencer is installed on the Sequencing workstation.  It is recommended to apply the latest App-V updates as well.
  • Microsoft Office 2010 volume SKU (32-bit).  Only the 32-bit version of Office 2010 is supported.  This may be deployed to either 32 or 64-bit operating systems.  We recommend sequencing on the same operating system as that of the operating system to which you will deploy the package.
  • Microsoft Office 2010 Deployment Kit for App-V: The Deployment Kit installs the Office 2010 licensing service and optionally installs proxies to enable integration features.


The Microsoft Office 2010 Deployment Kit for App-V is a required component to sequence and deploy Microsoft Office 2010.  The deployment kit provides two main functions:

  • Installation and configuration of the Office Software Protection Platform service.
  • Optional configuration of virtualized components to allow for seamless interaction with the operating system.

The Deployment Kit is first installed on the sequencing workstation.  The Deployment Kit must also be installed on all App-V clients where your Office 2010 package will be deployed.

Understanding Proxies

Proxies are components included with the Office 2010 Deployment Kit for App-V that allow interaction between virtualized components such as Outlook, Windows Desktop Search, and Internet Explorer SharePoint add-ons and Windows.  For example, the Outlook proxy launches the virtualized Outlook 2010 executable when a user-right clicks on a file and chooses Sent To\Mail Recipient.  Running OffVirt.msi with a specific set of command-line parameters installs the proxies.  For most installations, this means that you will run MSIExec.exe twice to install first the proxies and then the licensing components.  Installing proxies adds files, registry accounts, and the Office Licensing Service to the local computer.

Before installing proxies, it is recommended that you review the document Known issues and limitations when using virtualized Office 2010 applications on App-V 4.6 and App-V 4.5 SP2 clients.


Step 1: Prepare the Sequencing Workstation   

1.   Prepare the sequencing machine following the guidelines provided in the Best Practices for the Application Virtualization Sequencer document.

2.       On the App-V 4.6 SP1 sequencing workstation, open Regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Sequencer\SxSAppExtensions.  For 64-bit 32-bit operating systems, the value will be located at HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Sequencer\SxSAppExtensions.  Double-click on the SxSAppExtensions value.  In the Edit Multi-String dialog box, append the value VSL to the end of the list.  Click OK to save the change.

Note:  Append this value to the end of the list of entries in this key.  Do not remove any existing values.

3.       For down-level operating systems (pre-Windows 7 or Server 2008 R2), install Windows Search 4.0.

By default, Windows Search is installed on Windows 7 and Windows Server 2008 R2. If it is not present, enable it via Control Panel\All Control Panel Items\Programs and Features\Turn Windows Features on or off.

4.       For down-level operating systems, download the XPS Viewer by installing the Microsoft XML Paper Specification Essentials Pack.

By default, XPS Viewer is installed on Windows Vista and Windows 7.  If it is not present, enable it in Control Panel\All Control Panel Items\Programs and Features\Turn Windows Features on or off.

5.       Stop and set the Windows Update service to Disabled.

6.       Stop and set the Windows Defender service to Disabled. 

7.       Install the App-V 4.6 SP1 Sequencer if you have not already done so.

8.       Download and install the Microsoft Office 2010 Deployment Kit for App-V. Setup will extract the Microsoft Office 2010 Deployment Kit for App-V and ask you where to save the files.

9.       Open an elevated command prompt by right clicking on Start\All Programs\Accessories\Command Prompt and choosing Run as administrator. Navigate in the command prompt to the directory that you specified in the previous step (for example, CD C:\offvirt).

10 Determine the appropriate command line for your environment and install the Office 2010 Deployment kit for App-V on the Sequencer.  The generalized syntax is:

msiexec /i OffVirt.msi [feature flags][licensing flags]

Feature flags prepare the Sequencer for to configure the package to make use of proxy components for Office-OS integration.  Licensing flags specify the licensing mode the package will be configured to use.  Both are critical to successfully sequencing Office 2010.


Feature flags

Use the feature flags for the architecture that matches your Sequencing computer's operating system:

32-bit OS:


64-bit OS:



Licensing flags

Most installations will already have a licensing infrastructure in place.  Please refer to Office 2010 volume activation to determine which activation and licensing method to use.


KMS activation

Setting these flags to 1 will install the KMS client key for the specified applications or suites.  You must specify at least one application or suite.  If you are installing an Office suite such as Office 2010 Professional Plus, you do not need to specify individual components (Word, Excel, PowerPoint, etc.)  included in the suite.  If you will include Visio or Project in your package, those products must be specified individually in addition to the suite. 




Enables licensing for:


0 or 1

Office Professional Plus


0 or 1

Small Business Basics


0 or 1



Office 2010 stand-alone applications:



Enables licensing for:


0 or 1



0 or 1



0 or 1

SharePoint Workspace


0 or 1



0 or 1



0 or 1



0 or 1



0 or 1

Project Professional


0 or 1

Project Standard


0 or 1



0 or 1



0 or 1

Visio Premium


0 or 1

Visio Professional


0 or 1

Visio Standard


0 or 1



Properties for KMS Host configuration:





[Host name]

Enter KMS host name (not required if KMS host is registered on DNS and port = 1688.)


[Port number]

TCP port number of KMS service.  Not required if KMS host is registered on DNS and default port 1688 is used.

Example 1:  KMS activation, default KMS host settings, 32-bit Sequencer OS:

msiexec /i OffVirt.msi ADDLOCAL=Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp_Core PROPLUS=1

Example 2:  User-defined KMS host settings, Project Professional 2010, Vision 2010 Professional, 64-bit Sequencer OS:

msiexec /i OffVirt.msi ADDLOCAL=Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp_Core,OSppWoW64  PROPLUS=1 PROJECTPRO=1 VISIOPRO=1 KMSSERVICENAME="" KMSSERVICEPORT=1689

                MAK activation

MAK Option 1: VAMT 2.0
Use VAMT 2.0 (recommended) to install product keys on client computers streaming Office 2010.  In this scenario, you do not specify a licensing flag in the setup command line.  For example (VAMT activation; 32-bit Sequencer OS):

msiexec /i OffVirt.msi   ADDLOCAL=Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp_Core  

MAK Option 2:  Specify 25-Character Product Keys



Multiple product keys are semicolon delimited. For example:




Important: You must set USEROPERATIONS=1 to allow non-administrator users to activate MAK keys.  This licensing flag allows standard users (users who are not members of the local administrators groups) to apply a MAK key in order to activate Office applications.   By default, this is set to 0 if it is not specified.  KMS clients do not use this flag.  In general, most MAK installs should specify this setting.

The following is an example of a command line for MAK activation on a 64-bit App-V Sequencer:


Mixed activation (KMS and MAK together): If some client computers will use KMS activation, and other client computers to use MAK, use the KMS flags to install KMS client keys. Use VAMT 2.0 to install the MAK key after the deployment.             

If in Doubt

Most installations will use the following command lines on the sequencing workstation:

32-bit OS:

msiexec /i OffVirt.msi ADDLOCAL=Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp_Core PROPLUS=1

64-bit OS:

msiexec /i OffVirt.msi ADDLOCAL=Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp_Core,OSppWoW64  PROPLUS=1


Step 2: Sequence Microsoft Office 2010

1.       Launch the App-V 4.6 SP1 Sequencer.

2.       Select Create a New Virtual Package.

3.       Select Create Package (default) then click Next.

4.       On the Prepare the computer for creating a virtual package dialog, follow the instructions to correct any warning messages, then click Next.

5.       On the Describe the type of application you want to package dialog, select Standard Application, then click Next.

6.       On the Select Installer dialog, select Browse and locate Setup.exe in the root folder of your Office 2010 installation media and click Next.

7.       On the Package Name dialog, give the package a descriptive name. Notice that the folder on Q:\ that will serve as the application root is automatically filled in.  If you need to change it, select Edit (advanced) and enter a different path. Click Next.

8.       On the Installation dialog, Office 2010 Setup will start.

Important: If you are sequencing Visio 2010 you will need to perform the following numbered steps to ensure it is licensed correctly. This must be applied during installation and these steps apply to Visio 2010 only.

  1. Within the Sequencer, choose a custom installation.
  2. When prompted, choose Run...
  3. Open a command prompt with Administrative rights and locate the setup executable for Visio 2010.
  4. Open Notepad, and enter the following text:
  5. <Configuration Product="Visio">
    <PIDKEY Value="xxxxxxxxxxxxxxxxxxxx" />
  6. Replace the xxx's with the appropriate 25-digit KMS or MAK key, depending on your licensing model and version of Visio. A list of KMS keys can be found at
  7. For further guidance with these parameters, see
  8. Save the file as config.xml in the same directory as the Visio setup executable
  9. From the open command prompt, run the following command: setup.exe /config <absolute file path to config.xml>

9.       At the Choose the installation that you want screen, click Customize. In the Installation Options tab, make sure that you select Run From My Computer for all features that you wish to install.  Users will not be able to later install any items marked Installed on First Use.

10.    Click the File Location tab and change the path so that it matches the application root directory that you selected to install to from Step 7 (for example, Q:\

11.    Click Install Now.

12.    After Office 2010 setup completes, return to the Installation dialog of the Sequencer. If desired while in monitoring mode, launch the virtual applications to configure customized settings such as ribbon items or default document locations. To do so, browse to the path of the virtual application.  For example:

a.       Click Start and then click Run

b.       Browse to the executable virtual file that you want to launch, for instance Q:\O2010\Office14\WINWORD.EXE, then press Enter

c.       Configure custom ribbon settings then close Word.

Important:  Never launch Outlook, OneNote or Microsoft SharePoint Workspace 2010, since doing so may capture user-specific information

13.    While at the Installation dialog, click Run and navigate to C:\windows\system32\regedit.exe.

14.    Once Regedit launches, we will create two TreatAs registry keys and then delete them so that the Sequencer records the deletion of these keys.

a.       Navigate to HKEY_CLASSES_ROOT\CLSID\{9203C2CB-1DC1-482d-967E-597AFF270F0D} for 32-bit OSes, HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{9203C2CB-1DC1-482d-967E-597AFF270F0D} for 64-bit OSes.

b.       Create a new key under {9203C2CB-1DC1-482d-967E-597AFF270F0D} named TreatAs.

c.       Delete the TreatAs key.

d.       Repeat steps 1-3 under the key HKEY_CLASSES_ROOT\CLSID\{BDEADEF5-C265-11D0-BCED-00A0C90AB50F} for 32-bit OSes, HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{BDEADEF5-C265-11D0-BCED-00A0C90AB50F} for 64-bit OSes.

e.       Close Regedit

15.    Use this step only if you have Office 2007 installed locally and Office 2010 virtualized. If you do not have Office 2007 installed locally, continue to the next step.

a.       While at the Installation dialog, click Run and browse to C:\windows\system32\regedit.exe.

b.       Once Regedit launches, create the following virtual registry key and then delete it so that the sequencer monitors the deletion of the newly added key.


c.       Close Regedit.

16.    On the Installation dialog, check the checkbox next to I am finished installing and click Next.

17.    While on the Configure Software dialog, select each of your frequently used programs and run it once in order to build Feature Block One (Word, Excel, Publisher, etc.). Never launch Outlook, OneNote or Microsoft SharePoint Workspace 2010. Once you are finish, click Next.

18.    On the Installation Report dialog, review and click Next.

Step 3:  Configure Applications - Add Proxies and Modify Applications

In this section, we will configure the 5 proxies included in the Microsoft Office 2010 Deployment Kit for App-V and edit the shortcuts generated by the Sequencer. 

A common version number will be used for all applications in this package.  It is important that the version number used for all applications be the same.  By default, the version number will be the version of the target executable, not the package.  This actual number is arbitrary; in this example, we will use 14.0.6024.1000 (Office 2010 SP1) for consistency.  Also note that the default OSD File Name is changed for each component.

Note: Multiple dependencies between proxy components exist.  In general, it is recommended to include all 5 proxy components in your Office package. Omission of a step or proxy component may result in unexpected behavior or failure of the component.

Add new Proxy Applications for Proxy Support

1.       At the Customize screen, select the radio button for Customize.  Further configure the virtual application package. and then click Next.

2.       At the Edit Shortcuts dialog, click Add

3.       Add all 5 applications listed in the table below to the Office 2010 package

4.       Highlight and edit each application to update the Version and OSD File Name fields to include the 14.0.6024.1000 version number.  Most installations will have approximately 15-20 applications.

Note: The <short path> is the 8.3 directory that you installed Office 2010 to. For example, if you installed Office 2010 to Q:\Office2010.014, the <short path> would be OFFICE~1.014.  If possible, it is recommended to give the folder an 8.3 name such as OF2010.014.  To determine the <short path> value, open a command prompt on the sequencing workstation and type dir /x on the root of Q:.  Do not include the drive letter in the short path (in the example above, use %SFT_MNT%\OFFICE~1.014\Office14; an 8.3 name will yield a path like %SFT_MNT%\Office.014\Office 14).

Application Path



OSD File Name

%commonprogramfiles%\Microsoft Shared\virtualization handler\VirtualSearchHost.exe

Search MAPI Protocol Handler Host


Search MAPI Protocol 14.0.6024.1000.osd

%commonprogramfiles%\Microsoft Shared\Virtualization Handler\VirtualOWSSuppManager.exe

Microsoft SharePoint Client Support Manager


Microsoft SharePoint Client Support Manager 14.0.6024.1000.osd

%commonprogramfiles%\Microsoft Shared\Virtualization Handler\MapiServer.exe

Microsoft Virtual Office Simple Mapi Proxy Server


Microsoft Virtual Office Simple Mapi Proxy Server 14.0.6024.1000.osd

%windir%\system32\Control.exe %SFT_MNT%\<short path>\Office14\mlcfg32.cpl



Windows Control Panel


Windows Control Panel 14.0.6024.1000.osd

%SFT_MNT%\<short path>\Office14\MSOSync.exe



Microsoft Office Document Cache


Microsoft Office Document Cache 14.0.6024.1000.osd


Set the Office Document Cache Application to Start Automatically

1.       While at the Edit Shortcuts screen, double-click the entry for Microsoft Office Document Cache on the right-hand side of the dialog.

2.       Double-click on Shortcuts under Microsoft Office Document Cache on the left-hand side of the dialog and click Edit Locations…

3.       Check Start Menu  and type Programs\Startup in the text box.  Click OK to return to the Edit Shortcuts dialog.

4.       At the Edit Shortcuts dialog, click Next.


Optimize the Package for Streaming

  1. At the Prepare for Streaming page, launch your most frequently used applications once, then close it down (Word, Excel, PowerPoint, etc.). Never launch Outlook, OneNote or SharePoint.
  2. Once complete, at the Streaming dialog, click Next.
  3. At the Target OS page select the OSes relevant to your organization. 

Create and Save the Package

  1. On the Create Package page, ensure that the Save the package now option is selected and click Create.
  2. The package will be created in a folder on the desktop by default. Upon completion, click Close to return to the main Sequencer page.  Do not exit the Sequencer yet.

Step 4: Configure Office 2010 Registry and OSD Settings

Registry setting for all installations

  1. On the main page of the Sequencer, click Modify an Existing Virtual Application Package.
  2. On the Select Task page, select Edit Package and click Next.
  3. At the Select Package page, browse to the location where you saved your package. Select the .SPRJ file in the folder and click Open.  Click Edit when you return to the Select Package page.
  4. The Sequencer will display eight tabs. Select the Virtual Registry tab. Double-click REGISTRY on the left-hand side to expand the view of the registry.  Verify that the following virtual registry key is set to Merge with Local.

MACHINE\Software\Microsoft\Office\14.0   (for 32-bit OSes)

MACHINE\Software\Wow6432Node\Microsoft\Office\14.0   (for 64-bit OSes)

    5.  Right-click the key, select Key, and check Merge with Local Key.

Registry setting for environments with Office 2007 coexistence

If you are deploying your Office 2010 package to computers that already have 2007 Office installed locally (2007 Office and Office 2010 coexistence), use the steps in this section. Otherwise, skip this step and continue on to the next section.   Also, refer to the note on Microsoft Outlook co-existence in on Known issues and limitations when using virtualized Office 2010 applications on App-V 4.6 and App-V 4.5 SP2 clients.

1.       On the Virtual Registry tab, expand REGISTRY\USER on the left-hand side of the dialog and navigate to USER\%SFT_SID%\Software\Microsoft\Windows NT\CurrentVersion

2.       Right-click CurrentVersion, click Key then click New.

3.       Right-click the resulting New Key 1 entry, click Key then click Rename.

4.       Type Windows Messaging Subsystem for the new key name.

5.       Select Windows Messaging Subsystem and repeat the steps above to create a sub-key named Profiles (i.e. the complete path will be REGISTRY\USER\%SFT_SID%\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles)

6.       If you are sequencing on a 64-bit OS, create this registry key in addition:

REGISTRY\USER\%SFT_SID%\ Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles

7.       If your clients are running the App-V 4.6 client, set the Profiles key to Override Local Key.

8.       If the clients are App-V 4.5 clients, set the Windows Messaging Subsystem key to Merge with Local Key.

Configure Virtual Applications to Interact with the Local Environment

In this section, we will configure the LOCAL_INTERACTION_ALLOWED tag for all applications in the package.  Performing this step allows Office applications to share data and interact with the operating system and other applications.


  1. Click on the OSD tab in the Sequencer.
  3.  Highlight LOCAL_INTERACTION_ALLOWED and change the Element Text: to TRUE from the default setting of FALSE.
  4.  Click on the drop-down menu under Select Application: and select the next application in the list.  Repeat the steps above for all applications in your Office package.

Save the Package

Click on File then Save to save the package.   Exit the Sequencer and publish the package to your App-V clients.


Step 5:  Configure a Client Computer to Run Virtualized Office 2010

Follow the steps in this section on the App-V client computer.  To install the Microsoft Office 2010 Deployment Kit for App-V on the client, you will run OffVirt.MSI twice.  The first command configures licensing mode; the second will configure Office proxies.   The commands must be ran separately (i.e. you cannot create a single command line to perform both operations).  For electronic software delivery (ESD) platforms such as Microsoft System Center Configuration Manager 2007 or 2012, you may safely add the /quiet switch to the MSIExec command line to run non-interactively.  Refer to the Licensing flags section under Step 1: Prepare the Sequencing Workstation above for details about the command line parameters.

Install the Microsoft Office 2010 Deployment Kit for App-V - Licensing

1.       Download and install the Microsoft Office 2010 Deployment Kit for App-V.  Record the location that setup extracts its files to.

2.       Open an elevated command prompt by right-clicking on Start\All Programs\Accessories\Command Prompt and choosing Run as administrator.

3.       Navigate to the folder you created above in the command prompt (e.g. type CD C:\OFFVIRT).

4.       Type the following command in the elevated command prompt:

Msiexec /i OffVirt.msi [licensing flags]

[licensing flags] is normally the same set of licensing flags that were specified during sequencing.  Do not specify any feature flags at this time. 

                Example 1:  If you will use KMS activation, run the following command on the App-V client (this is the most common scenario):

                Msiexec /i OffVirt.MSI PROPLUS=1

                Example 2: Use this command for KMS activation for an Office package that will also include Visio and Project:

                Msiexec /i OffVirt.MSI PROPLUS=1 PROJECTPRO=1 VISIOPRO=1

Example 3:  If you specified feature flags of PROPLUS=1 during sequencing for a MAK client that will obtain its keys from a VMT 2.0 server, on the App-V client run:


Example 4: MAK client with VAMT 2.0 infrastructure (recommended for MAK clients):

                Msiexec /i  PROPLUS=1 USEROPERATIONS=1

Example 5: MAK client with a product key specified:


Mixed activation (KMS and MAK in the same environment)

If you want some client computers to use KMS activation, but other client computers to use MAK, do the following:

·         Use the KMS flags to install KMS client keys (e.g. run Msiexec /i OffVirt.MSI PROPLUS=1)

·         Use VAMT 2.0 to install the MAK key after the deployment.

Install the Microsoft Office 2010 Deployment Kit for App-V - Proxies

After the license flags have configured, configure Office proxies on the client workstation.  This step configures the client to be able to take advantage of integration features such as Outlook integration, accessing SharePoint sites from Office, and enabling search in Outlook.  To do this, binary components and registry key modifications must be made to the host OS.

To successfully run the command line in this section, you will need to construct a command line based on settings in your Office package.  The general syntax is (single command line, may wrap on your screen):

msiexec /i OffVirt.msi ADDDEFAULT=Click2runOneNoteProxy,Click2runOutlookProxies,Click2runWDSProxy,Click2runOWSSuppProxies PACKAGEGUID={SFT package GUID} PACKAGEVERSION=versions found in OSD files for proxies, Outlook, and OneNote OUTLOOKNAME=app name for Outlook from OSD ONENOTENAME=app name for OneNote from OSD MAPISERVER=MAPI proxy app name VIRTUALSEARCHHOST=Search proxy app name MLCFG32CPL=app name for virtual mail configuration OWSSUPPServer=app name for SharePoint proxy

Individual command line settings will need to be verified in your environment:

1.       msiexec /i OffVirt.msi - this is the main command line.  It assumes that you are in the working directory where OffVirt.msi is located.  If not, specify the full pat to OffVirt.msi.

2.       ADDDEFAULT=Click2runOneNoteProxy,Click2runOutlookProxies,Click2runWDSProxy,Click2runOWSSuppProxies - this section does not need to be modified.

3.       PACKAGEGUID={SFT_package_GUID} - the package GUID is identical for all applications in the package.  Open any OSD from your Office package in Notepad and located the line <SOFTPKG GUID= in the .OSD file.  Record the GUID and replace SFT_package_GUID with this number.  Note that the OSD will record the number in quotation marks; the command line requires that you place the number in curly brackets ({}).  For example:

<SOFTPKG GUID="7DEE47AD-B420-3488-867D-186577DA9539"



4.       PACKAGEVERSION  - this is the package version you entered in the section "Step 3:  Configure Applications - Add Proxies and Modify Applications" during sequencing.  Verify this by opening any OSD in Notepad and locating the line that looks like this:  <SOFTPKG GUID="7DEE47AD-B420-3488-867D-186577DA9539" NAME="Microsoft Access 2010" VERSION="14.0.6024.1000">.  Copy the VERSION attribute without the quotes.  In this example, you would construct the command line PACKAGEVERSION=14.0.6024.1000.

5.       OUTLOOKNAME, ONENOTENAME, MAPISERVER, VIRTUALSEARCHHOST, MLCFG32CPL, OWSSUPPServer  – These command-line variables are constructed from specific values in the application’s OSD configuration file.  Locate the OSD in your package that corresponds to Outlook.exe.  To identify this file, search the OSDs in your package for the string Outlook.exe.  Open the OSD file in Notepad and verify the FILENAME attribute of the CODEBASE tag.  For example:  FILENAME="OFF2K10.001\Office14\OUTLOOK.EXE".  Above this value, locate the <SOFTPKG> tag.  Record the name of NAME field from this tag.  Use the value of NAME in your command line.  For example, <SOFTPKG GUID="AB404D53-3EB3-4D2D-9EC7-4513687FFA1E" NAME="Microsoft Outlook 2010" yields the command line variable OUTLOOKNAME="Microsoft Outlook 2010".  Repeat this process for all components using the following table:



Executable in FILENAME













*verify that PARAMETERS references “mlcfg32.cpl”; for example: - PARAMETERS="%SFT_MNT%\OFF2K10.001\Office14\mlcfg32.cpl" FILENAME="%windir%\system32\control.exe"

1.       Open an elevated command prompt by right-clicking on Start\All Programs\Accessories\Command Prompt and choosing Run as administrator.

2.       Run the command line you constructed above.

For example:

msiexec /i c:\OffVirt.msi ADDDEFAULT=Click2runOneNoteProxy,Click2runOutlookProxies,Click2runWDSProxy,Click2runOWSSuppProxies PACKAGEGUID={5971AF75-7831-4AE9-906F-0F30C7DD0CA5} PACKAGEVERSION=14.0.6024.1000 OUTLOOKNAME=”Microsoft Outlook 2010” ONENOTENAME=”Microsoft OneNote 2010” MAPISERVER=”Microsoft Virtual Office Simple Mapi Proxy Server” VIRTUALSEARCHHOST=”Search MAPI Protocol Handler Host” MLCFG32CPL=”Windows Control Panel” OWSSUPPServer=”Microsoft SharePoint Client Support Manager”

Note Registration of each component as shown above is required due to dependencies between proxy components.


Known Issues when Sequencing Office 2010

Cannot start x64 Visio 2010 during the monitoring phase of sequencing on an x64 Vista computer

To resolve the issue, restart monitoring. To do this, click Stop monitoring, and click Start monitoring, then launch Visio.

Outlook 2003 Launches Instead of Outlook 2010

If Outlook 2003 is installed locally, Send to\Mail Recipient functionality in Explorer will always launch Outlook 2003.  To prevent this behavior, uninstall Outlook 2003.

SharePoint Site Taking a Long Time To Launch

Known issues and Limitations when Using Office 2010 Virtualized

The list of known issues and limitations when using Office 2010 virtualized on App-V is documented in the following article in the Microsoft Knowledge Base: