Prescriptive guidance for sequencing the Beta version of the 2010 Office system in Microsoft App-V

Article translations Article translations
Article ID: 980861
Expand all | Collapse all

On This Page

INTRODUCTION

Beta Information
This article discusses a beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this beta product. For information about how to obtain support for a beta release, see the documentation that is included with the beta product files, or check the Web location where you downloaded the release.
This article describes one method that you can use to successfully sequence the Beta version of the 2010 Microsoft Office system for use with Microsoft Application Virtualization (App-V) 4.6. The method that is described in this article is not the only method that is available. You may have to change the information in the article as appropriate for your particular environment.

MORE INFORMATION

The 2010 Office system uses the Office Software Protection Platform (SPP) service. This basically is the same activation technology that is used to activate volume editions of Windows Vista and of Windows 7. This service is contained in the Microsoft Office 2010 Deployment Kit for App-V. Before you can sequence the 2010 Office system, this service must be installed and configured on the sequencing computer. The service must also be installed on any client computer that is needed to stream 2010 Office.

Prerequisites

The following are prerequisites for installing and sequencing the 2010 Office system for use with Microsoft App-V 4.6:
  • Microsoft Application Virtualization version 4.6.0.1401 and later versions. The 2010 Office system is not supported on App-V 4.5.
  • The 2010 Office system, both the 32-bit and 64-bit versions. Proxies are not supported on 64-bit versions of the 2010 Office system.
  • Microsoft Office 2010 Deployment Kit for App-V. The Deployment Kit contains the required 2010 Office licensing service and optional proxies to enable integration features.

Sequence the 2010 Office system with App-V

To sequence the Beta version of the 2010 Office system with App-V, perform the following procedures:

Procedure 1: Sequence the2010 Office system

Step 1: Prepare a computer for sequencing

  1. Prepare your computer for sequencing by following the guidelines that are provided in the "Best Practices for the Application Virtualization Sequencer" document. If you do not follow these guidelines in the sequencing document, errors in functionality can occur.
  2. Make sure that Windows Search 4.0 is installed, and then set the Windows Search service to either Manual or Automatic. By default, Windows Search is installed in Windows 7. Activate Windows Search by using Windows Features in the Add or Remove Programs item in Control Panel.
  3. Download the XPS Viewer by installing the Microsoft XML Paper Specification Essentials Pack. By default, XPS Viewer is installed on Windows Vista and on Windows 7.
  4. Set the Windows Update service to Disabled.
  5. Install the App-V 4.6 Sequencer, if you have not already done this.
  6. Download the Deployment Kit, and extract the .exe file.
  7. After you extract the .exe file, an OffVirt.msi file is available.

Step 2: Install the deployment kit

  1. Open an elevated command prompt.
  2. Browse to the directory that contains the Offvirt.msi file.
  3. Execute the following command:
    msiexec /i OffVirt.msi [licensing flags]
    Note You must enter a correct licensing flag here to correctly configure the Deployment Kit. Otherwise, functionality may be incorrect.
Licensing Flags
For more information about the 2010 Office system volume activation and to determine which activation and licensing flags to use, visit the following Microsoft TechNet Web site:
http://technet.microsoft.com/en-us/office/ee691939.aspx
KMS activation
To install the KMS client key for the products that are specified, set the flags in the following table to 1..
Collapse this tableExpand this table
FlagValueProduct and Description
PROFESSIONALPLUS0 or 11 = Install Microsoft Office Professional Plus KMS client key
VISIOULTIMATE0 or 11 = Install Microsoft Office Visio Ultimate KMS client key
PROJECTPROFESSIONAL0 or 11 = Install Microsoft Office Project Professional KMS client key
KMSSERVICENAME[Host]Enter KMS host name (This flag is not required if the KMS host is registered on DNS and port = 1688.
KMSSERVICEPORT[Port]This flag is not required if the KMS host is registered on DNS and port = 1688.
Examples of KMS activation
  • Default KMS host settings:
    msiexec /i OffVirt.msi PROFESSIONALPLUS=1 VISIOULTIMATE=1
  • User-defined KMS host settings:
    msiexec /i OffVirt.msi PROFESSIONALPLUS=1 PROJECTPROFESSIONAL=1 KMSSERVICENAME=”kms.contoso.com” KMSSERVICEPORT=1689
MAK activation
Option 1: Use the Volume Activation Management Tool (VAMT) 2.0 (recommended) to install product keys on client computers that stream the 2010 Office system. To obtain VAMT, visit the following Microsoft Download Center Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=8265fdef-b921-4dbf-ba8b-bb1cbe238ce6
Option 2: Use the PIDKEYS flag or use the USEROPERATIONS flag as described in the following table.
Collapse this tableExpand this table
FlagValue
PIDKEYS

Multiple product keys are semicolon delimited.

Ex. PIDKEYS=X-X-X-X-X; Y-Y-Y-Y-Y;
XXXXX-XXXXX-XXXXX-XXXXX-XXXXXX
USEROPERATIONS0 or 1
Important You must set USEROPERATIONS=1 to let a user activate licensing on the client computer.

Example of MAK activation
msiexec /i OffVirt.msi PIDKEYS=XXXXX-XXXXX-XXXXX-XXXXX;YYYYY-YYYYY-YYYYY-YYYYY-YYYYY USEROPERATIONS=1
Mixed activation (KMS/MAK)
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.
  • Use VAMT 2.0 to install MAK key post-deployment.

Step 3: Sequence the2010 Office system

  1. Start the sequencer.
  2. Click Create Package.
  3. Create a name for the package.
  4. For the installation folder, install to a new directory by using an 8.3 format such as Q:\Temp123.wxp, and then click OK.
  5. Click Begin Monitoring.
  6. Start the setup.exe for the 2010 Office system.
  7. At the Choose the installation that you want prompt, click Customize.

    Note In the Office installation procedure, make sure that you select Install to hard drive if you want that feature installed.
  8. Click the File Location tab, and change the path to match the installation directory that you selected in step 4.
  9. Click Install.

Step 4: Start virtual applications during monitoring (optional)

  1. Click Start, and then click Run.
  2. Enter the path of the executable virtual file to start the virtual application.

    For example, to start Microsoft Word, type Q:\Temp123.wxp\Office14\WINWORD.EXE, and then click OK.
Note You must enter the actual path of the virtual application.

Step 5: Configure additional proxies (optional)

  1. Make sure that the sequencer is still monitoring.
  2. See Procedure 2: Configure additional proxies.
Note Proxies enable Fast Search in Outlook Search, integration with Microsoft SharePoint Server, such as opening or editing documents, and other features.

Important If you performed the steps in "Step 5: Configure additional proxies (optional)," skip step 6, and go to "Step 7: Save the package."

Step 6: Start applications to create the primary feature block

To do this, follow these steps:
  1. On the Application page, click Next.
  2. Select and start preferred applications to generate the primary feature block for each application.
  3. Click Next.
  4. After sequencing is finished, click Finish.
Notes
  • We do not recommend starting Microsoft OneNote, Microsoft Outlook, and SharePoint Server because of their customizable settings.
  • We do not recommend that you press F1 for help in this step.

Step 7: Save the package

To save the package, click Package, and then click Save As.

Procedure 2: Configure additional proxies

To configure additional proxies, follow these steps on the sequencing computer.

Note We highly recommend that you add these subkeys during monitoring by using Registry Editor or by using a REG ADD command.

Step 1: Configure Windows Desktop Search proxy registry settings

Add the values in the following table to this registry subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Search\Preferences
Note Create the subkey if it does not exist.
Collapse this tableExpand this table
DWORD ValueValue data
{4154494E-BFF9-01B8-00AA-0037D96E0000}1
{C0A19454-7F29-1B10-A587-08002B2A2517}1
{70fab278-f7af-cd11-9bc8-00aa002fc45a}1
{c34f5c97-eb05-bb4b-b199-2a7570ec7cf9}1
{0077B49E-E474-CE11-8C5E-00AA004254E2}1

Step 2: Configure SharePoint proxy registry settings

Important The following step must be performed during monitoring to have these keys persist in a deleted state in the virtual registry.
  1. Make sure that the sequencer is still monitoring.
  2. Create the following virtual registry subkeys and then delete them so that the sequencer monitors the deletion of the newly added subkeys:
    HKEY_CLASSES_ROOT\CLSID\{9203C2CB-1DC1-482d-967E-597AFF270F0D}\TreatAs


    HKEY_CLASSES_ROOT\CLSID\{BDEADEF5-C265-11D0-BCED-00A0C90AB50F}\TreatAs
    If you are sequencing on a 64-bit version of Windows, also create and delete the following keys:
    HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{9203C2CB-1DC1-482d-967E-597AFF270F0D}\TreatAs


    HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{BDEADEF5-C265-11D0-BCED-00A0C90AB50F}\TreatAs
  3. Locate the following virtual registry subkeys:
    HKEY_CLASSES_ROOT\CLSID\{3FD37ABB-F90A-4DE5-AA38-179629E64C2F}\InprocServer32\(Default)


    HKEY_CLASSES_ROOT\CLSID\{62B4D041-4667-40B6-BB50-4BC0A5043A73}\InprocServer32\(Default)


    HKEY_CLASSES_ROOT\CLSID\{9203C2CB-1DC1-482D-967E-597AFF270F0D}\InprocServer32\(Default)


    HKEY_CLASSES_ROOT\CLSID\{BDEADEF5-C265-11D0-BCED-00A0C90AB50F}\InprocServer32\(Default)
    If you are sequencing on a 64-bit version of Windows, also locate the following virtual registry keys:
    HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{3FD37ABB-F90A-4DE5-AA38-179629E64C2F}\InprocServer32\(Default)


    HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{62B4D041-4667-40B6-BB50-4BC0A5043A73}\InprocServer32\(Default)


    HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{9203C2CB-1DC1-482D-967E-597AFF270F0D}\InprocServer32\(Default)


    HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{BDEADEF5-C265-11D0-BCED-00A0C90AB50F}\InprocServer32\(Default)
  4. Change the data in each key that you located in step 3 to the following data:
    %SFT_MNT%\shortpath\VFS\CSIDL_PROGRAM_FILES\Microsoft Office\Office14\OWSSUPP.DLL
    Here is an example of the shortpath placeholder: If the installation drive is Q:/Temp123.wxp, then the shortpath is Temp123.wxp.

Step 3: Add new proxy applications for proxy support

  1. Click Stop Monitoring.
  2. Click Next.
  3. On the Configure Applications page, select the Applications root directory.
  4. Click Add, and then add the following Application (OSD) files:
    • Instant Search (Virtual Search Host)

      To quickly locate the path, click Browse, and then type or paste the following application path into the File name box:
      %commonprogramfiles%\microsoft shared\virtualization handler\VirtualSearchHost.exe
      In the Name box, type a specific name, such as Virtual Search Host.
    • Virtual SharePoint Proxy

      To quickly locate the path, click Browse, and then type or paste the following application path into the File name box:
      %commonprogramfiles%\microsoft shared\virtualization handler\VirtualOWSSuppManager.exe
      In the Name box, type a specific name, such as Virtual OWSSupp Manager.
    • Mail To: (Simple MAPI)

      To quickly locate the path, click Browse, and then type or paste the following application path into the File name box:
      %commonprogramfiles%\microsoft shared\virtualization handler\MapiServer.exe
      In the Name box, type a specific name, such as Mail To Host.
    • Virtual Mail Control Panel Applet

      To quickly locate the path, click Browse, and then type or paste the following application path into the File name box:
      %windir%\system32\Control.exe %SFT_MNT%\shortpath\Office14\mlcfg32.cpl
      In the Name box, type a specific name, such as Mail Control Panel.

      Notes
      • To add the %SFT_MNT%\shortpath\Office14\mlcfg32.cpl path to the application path, browse to the Control.exe application path, click OK, and then append the path to the end of the parameter in the Application Path box.
      • The shortpath placeholder is the 8.3 directory in which you installed the 2010 Office system. For example, if you installed the 2010 Office system to Q:\Temp123.wxp, then the shortpath would be Temp123.wxp.

Step 4: Synchronize all application OSD file versions with the proxy OSD version

  1. Right-click the Office installation file, setup.exe, and then click Properties.
  2. Click the Version tab.
  3. Change the version of all OSD files to match the version that you found in step 2.

    For example, if the version of ProfessionalPlus is 14.4514.1004, make sure that the version number of all Proxy application OSDs and all Office OSDs are set to 14.4514.1004.
  4. Click Next.

Step 5: Start the applications

This step is to create the primary feature block. We do not recommend that you start OneNote, Outlook, or SharePoint Server in this step. This will help preserve the customization settings for these applications.
  1. On the Launch Applications page, select and then start all the desired applications. This will generate the primary feature block for each application.
  2. Click Next.
  3. After sequencing is finished running, click Finish.

Step 6: Configure the 2010 Office system registry settings

  1. Click the Virtual Registry tab.
  2. Verify that the following virtual registry subkey is set to Merge with Local:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Office\14.0
  3. Right-click the subkey, click Key, and then make sure that the Merge with Local Key check box is selected.
  4. If you are sequencing on a 64-bit version of Windows, make sure that the following virtual registry subkey is set to Merge with Local:
    HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\Office\14.0
  5. Create the following registry subkey and make sure that the subkey is set to Override local key:
    HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles
    If you are sequencing on a 64-bit version of Windows, also create the following subkey and make sure that the subkey is set to Override local key:
    HKEY_CURRENT_USER\Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles
    Important The following steps must be performed during monitoring to have the key persist in a deleted state in the virtual registry.
    1. Set the sequencer to start monitoring.
    2. Create the following virtual registry subkey and then delete it so that the sequencer monitors the deletion of the newly added key:
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins\Microsoft

Step 7: Configure virtual applications to interact with the local environment

For each OSD, add TRUE to the following Element text of the tag:
SOFTPKG -> IMPLEMENTATION -> VIRTUALENV -> POLICIES -> LOCAL_INTERACTION_ALLOWED

Procedure 3: Configure a client computer to run the 2010 Office system

To configure a client computer to run the 2010 Office system, follow these steps on the client computer.

Step 1: Prepare the client computer

  1. Install the App-V client, if you have not already done this.
  2. Download the Deployment Kit, and extract the executable file (.exe).

    Note After you extract the executable file, an OffVirt.msi file is available.

Step 2: Install the Microsoft Office 2010 Deployment Kit

  1. Open an elevated command prompt.
  2. Browse to the directory that contains the Offvirt.msi file that you extracted in "Step 1: Prepare the client computer."
  3. Execute the following command:
    msiexec /i OffVirt.msi [licensing flags]
    Note You must provide a correct licensing flag to correctly configure the Deployment Kit. Otherwise, functionality may be incorrect.
Licensing flags
For more information about 2010 Office volume activation and to determine which activation and licensing flags to use, visit the following Microsoft TechNet Web site:
http://technet.microsoft.com/en-us/office/ee691939.aspx
KMS activation
Collapse this tableExpand this table
FlagValue
PROFESSIONALPLUS0 or 1
VISIOULTIMATE0 or 1
PROJECTPROFESSIONAL0 or 1
KMSSERVICENAME

Not required if the KMS host is registered on DNS and port = 1688.
[KMS Hostname]
KMSSERVICEPORT

Not required if the KMS host is registered on DNS and port = 1688.
[Port number]
Note KMS Activation occurs only after five or more computers request activation.
MAK activation
Option 1: Use the Volume Activation Management Tool (VAMT) 2.0 (recommended). To obtain VAMT, visit the following Microsoft Download Center Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=8265fdef-b921-4dbf-ba8b-bb1cbe238ce6
Option 2: Use the PIDKEYS flag or use the USEROPERATIONS flag as described in the following table.
Collapse this tableExpand this table
FlagValue
PIDKEYS

Multiple product keys are comma delimited. Ex. PIDKEYS=X-X-X-X-X; Y-Y-Y-Y-Y;
XXXXX-XXXXX-XXXXX-XXXXX-XXXXXX
USEROPERATIONS0 or 1
Important You must set USEROPERATIONS=1 to let a user activate licensing on the client computer.

Example of MAK activation
msiexec /i OffVirt.msi PIDKEYS=XXXXX-XXXXX-XXXXX-XXXXX;YYYYY-YYYYY-YYYYY-YYYYY-YYYYY USEROPERATIONS=1
Mixed activation (KMS/MAK)
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.
  • Use VAMT 2.0 to install MAK key post-deployment.

Step 3: Enable the proxies on the client

To enable the virtual proxies for the package, open an elevated command prompt, and then run the following command:
msiexec /i <Path to the OffVirt.msi>\OffVirt.msi ADDDEFAULT=Click2runOneNoteProxy,Click2runOutlookProxies,Click2runWDSProxy,Click2runOWSSuppProxies PACKAGEGUID=<SFT package GUID with {}> PACKAGEVERSION=<versions found in OSD files for proxies, Outlook, and OneNote> OUTLOOKNAME=<application name for Outlook from OSD> ONENOTENAME=<application name for OneNote from OSD> MAPISERVER=<MAPI proxy application name> VIRTUALSEARCHHOST=<Search proxy application name> MLCFG32CPL=<application name for virtual mail config> OWSSUPPServer=<application name for sharepoint proxy>
For example, run this command:
msiexec /i c:\OffVirt.msi ADDDEFAULT=Click2runOneNoteProxy,Click2runOutlookProxies,Click2runWDSProxy,Click2runOWSSuppProxies PACKAGEGUID={5971AF75-7831-4AE9-906F-0F30C7DD0CA5} PACKAGEVERSION=14.0.4229.1000 OUTLOOKNAME=”Microsoft Outlook 2010” ONENOTENAME=”Microsoft OneNote 2010” MAPISERVER=”Simple MAPI Proxy Server” VIRTUALSEARCHHOST=”Virtual Search Host” MLCFG32CPL=”Mail Control Panel” OWSSUPPServer=”Virtual OWSSupp Manager”

Frequently Asked Questions

Q1: Why cannot I start x64 Visio 2010 during the monitoring phase of sequencing on an x64-based Windows Vista computer?

A1:
This is a known issue. To resolve the issue, restart the monitoring. To do this, click Stop monitoring, and then click Restart monitoring.


Q2: For the SharePoint Server proxy, why do I have to add a virtual registry subkey and delete it?

A2:
The subkey has to be specifically recognized in the virtual environment as deleted. It is not enough for the subkey not to exist. If you create the subkey and then delete it during monitoring, the virtual environment will recognize the subkey as deleted and will never fail over to the physical registry if the subkey exists there.

Q3: Is it okay to use Outlook 2010 and Outlook 2007 at the same time?

A3:
Yes. If you already have the release version of Outlook 2007 on your computer, and you start Outlook 2010, you are prompted to create your profile. After you use Outlook 2010, and you decide that you want to use Outlook 2007 instead, you must delete your Outlook 2010 OST file. This is a limitation in Office.

Properties

Article ID: 980861 - Last Review: March 22, 2012 - Revision: 1.1
Keywords: 
kbhowto kbexpertiseinter kbsurveynew kbinfo KB980861

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com