Prescriptive Guidance for Sequencing Microsoft Office 2010 on Microsoft AppV 4.

6
This document describes one method that you can use to successfully sequence Microsoft Office 2010 for use with Microsoft Application Virtualization 4.6. The method that is described in this article is not the only method that is available. You may have to modify the information in the article as appropriate for your particular environment. Introduction Microsoft Office 2010 uses the Office Software Protection Platform (SPP) service, which essentially is the same activation technology used to activate volume editions of Windows Vista and Windows 7. This service in contained in the Microsoft Office 2010 Deployment Kit for AppV. Prior to sequencing Office 2010, this service must be installed and configured on the sequencing machine. It must also be installed on any client machines wishing to stream Office 2010. Prerequisites Below are the prerequisites for installing and sequencing Microsoft Office 2010 for use with Microsoft App-V 4.6: Microsoft Application Virtualization version 4.6 Microsoft Office 2010 is currently not supported on App-V 4.5. Microsoft Office 2010 volume SKU (32-bit or 64-bit) Note: Proxies are not supported on 64-bit versions of Microsoft Office 2010. Microsoft Office 2010 Deployment Kit for App-V The Deployment Kit contains the required Office 2010 licensing service and optional proxies to enable integration features.

Below are the steps to sequence Microsoft Office 2010 with App-V.

Sequence Microsoft Office 2010

Tasks Prepare a machine for sequencing Detailed steps Perform the following on the sequencing machine. 1. 1. Prepare your machine for sequencing following the guidelines provided in the Best Practices for the Application Virtualization Sequencer document. Not following the guidelines in the sequencing document can cause errors in functionality.

For this recipe, we recommend the following settings in accordance with the best practices document above.

2.

Ensure you have Windows Search 4.0 installed, and set the Windows Search service to either Manual or Automatic.

Windows Search is installed in Windows 7 by default: Activate it through Windows Features in Add/Remove Programs. 3. Download the XPS Viewer by installing the Microsoft XML Paper Specification Essentials Pack. XPS Viewer is installed on Windows Vista and Windows 7 by default. 4. Set the Windows Update service to disabled. 5. 6. 7. 2. Install the deployment kit 1. 2. 3. Install the App-V 4.6 Sequencer, if you have not already done so. Download the Deployment Kit and extract the .exe. After extracting the .exe, you should have an OffVirt.msi file. Open a command prompt with administrative privileges. Navigate to the directory containing the Offvirt.msi. Execute the following command: msiexec /i OffVirt.msi [feature flags] [licensing flags]

Feature Flags: Use the feature flags for the architecture that matches your sequencing station operating system: 32-bit: ADDLOCAL= Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OS pp_Core 64-bit: ADDLOCAL= Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OS pp_Core,OSppWoW64 You must enter a proper licensing flag below to properly configure the Deployment Kit; otherwise, functionality may be incorrect. Licensing Flags: Learn more about Office 2010 volume activation to determine which activation (and licensing flags) to use. 1. KMS activation: Setting these flags to 1 will install the KMS client key for the specified products. Properties for Office 2010 suites:
Flag PROPLUS SMALLBUSBASICS STANDARD Value 0 or 1 0 or 1 0 or 1 Enables licensing for: Office Professional Plus Small Business Basics Standard

Properties for Office 2010 standalone applications:

Flag: ACCESS EXCEL GROOVE INFOPATH Value 0 or 1 0 or 1 0 or 1 0 or 1 Enables licensing for: Access Excel SharePoint Workspace InfoPath

ONENOTE OUTLOOK POWERPOINT PROJECTPRO PROJECTSTD PUBLISHER SPD VISIOPREM VISIOPRO VISIOSTD WORD

0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1

OneNote Outlook PowerPoint Project Professional Project Standard Publisher SharePointDesigner Visio Premium Visio Professional Visio Standard Word

Properties for KMS Host configuration

Flag: KMSSERVICENAME Value [Host] Description: Enter KMS hostname (not required if KMS host is registered on DNS and port = 1688.) Not required if KMS host is registered on DNS and port = 1688.

KMSSERVICEPORT

[Port]

Example 1: KMS activation, default KMS host settings, on 32-bit sequencing station: msiexec /i OffVirt.msi ADDLOCAL= Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp _Core PROPLUS=1 VISIOPREM=1 Example 2: KMS activation, user-defined KMS host settings, on 64-bit sequencing station: msiexec /i OffVirt.msi ADDLOCAL= Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp _Core,OSppWoW64 PROPLUS=1 PROJECTPRO=1 KMSSERVICENAME=kms.contoso.com KMSSERVICEPORT=1689

2.

MAK activation: Option 1: Use VAMT 2.0 (recommended) to install product keys on client machines streaming Office 2010. Option 2:
Flag: PIDKEYS Multiple product keys are semi-colon delimited. Ex. PIDKEYS=X-X-X-X-X; Y-Y-Y-Y-Y; USEROPERATIONS Value: XXXXX-XXXXX-XXXXX-XXXXXXXXXXX

0 or 1

Important! You must set USEROPERATIONS=1 to allow a user to activate licensing on the client machine.

Example MAK activation, on 64-bit sequencing station: msiexec /i OffVirt.msi ADDLOCAL= Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp _Core,OSppWoW64 PIDKEYS=XXXXX-XXXXX-XXXXXXXXXX;YYYYY-YYYYY-YYYYY-YYYYY-YYYYY USEROPERATIONS=1

3.

Mixed activation (KMS/MAK): If you want some client machines to use KMS activation, but others to use MAK. Use the KMS flags to install KMS client keys. Use VAMT 2.0 to install MAK key post-deployment.

2.

Sequence Microsoft Office 2010

1. 2. 3. 4. 5. 6. 7.

Launch sequencer. Click Create Package. Create a name for the package. For install folder, install to a new directory with an 8.3 format (ex. Q:\Temp123.wxp). Click OK. Click Begin Monitoring. Start the setup.exe for Office 2010. At the Choose the installation that you want screen, click Customize.

In the Office install procedure, ensure you select Install to hard drive if you want that feature installed. 8. Select the File Location tab, and change the path to match the directory that you selected to install to when you begin monitoring (ex. Q:\Temp123.wxp). 9. 3. (Optional) Launch virtual applications during monitoring This step is performed to configure first launch use settings (ex. Customizing user settings) 4. (Optional) Configure additional proxies Click Install Now. You must navigate to actual path of the virtual application. 1. Go to Start Menu, select Run. 2. Navigate to the executable virtual file to launch: For example, to launch Word, type: Q:\Temp123.wxp\Office14\WINWORD.EXE 3. 4. Click Stop Monitoring. Click Next to end the monitoring.

Proxies enable Fast Search in Outlook Search, integration with SharePoint (opening, editing documents), and other features. 1. See the Configure Additional Proxies section below. OneNote, Outlook, Sharepoint are NOT recommended for launch due to the customizable settings. 1. On Application page, click Next. 2. 3. 4. Select and launch preferred applications to generate the primary feature block for each application. Click Next. Once sequencing completes, click Finish.

Important! If you performed Step 4, skip to Step 6. 5. Launch Applications to create primary feature block

6.

Save the package.

1.

On the menu toolbar, select Package, Save As

Configure Additional Proxies

Tasks Add new proxy applications for proxy support Detailed steps Perform the following on the sequencing machine. 1. 1. 2. On the Configure Applications page, select the Applications root directory. Click Add, and add the following applications below.

Application (OSD) Files to add: 1. Instant Search (Virtual Search Host) Application Path: %commonprogramfiles%\microsoft
shared\virtualization handler\VirtualSearchHost.exe

To quickly locate the path, click Browse and copy and paste the Application Path into File name: text field Name: <Specify a name, default Search MAPI Protocol Handler Host
>

2.

Virtual SharePoint Proxy Application Path: %commonprogramfiles%\microsoft

shared\virtualization handler\VirtualOWSSuppManager.exe

Name: <Specify a name, default Microsoft SharePoint Client Support

Manager >

3.

Simple MAPI Application Path: %commonprogramfiles%\microsoft

shared\virtualization handler\MapiServer.exe

Name: <Specify a name, default Microsoft Virtual Office Simple Mapi

Proxy Server>

4.

Virtual Mail Control Panel Applet Application Path: %windir%\system32\Control.exe

%SFT_MNT%\<short path>\Office14\mlcfg32.cpl

Name: <Specify a name, default Windows Control Panel> To add the parameter %SFT_MNT%\~~~~~~\Office14\mlcfg32.cpl into the Application Path, browse to the Control.exe application path and select OK, then append the parameter in the Application Path: text field. The short path is the 8.3 directory you installed Office 2010 to. For example, if you installed Office 2010 to Q:\Temp123.wxp, then the shortpath would be Temp123.wxp. 5. Office Document Cache Application Path: Q:\<short path>\Office14\MSOSync.exe Name: <Specify a name, default Microsoft Office Document Cache>

2.

Set Office Document Cache application to start automatically Synchronize all application OSD file versions with proxy OSD version

1. 2. 3. 1. 2. 3.

Expand the Office Document Cache element in the Applications tree Select Shortcuts Edit the shortcut location to be Start Menu\Programs\Startup Right-click the Office installation file, setup.exe, and select Properties. Go to Version tab. Change the version of all OSD files to match that version.

3.

Example: If the version of setup.exe is 14.0.4763.1000, then ensure that the version number of all Proxy application OSDs and all Office OSDs are set to 14.0.4763.1000. 4. Click Next. 4. Launch Applications This step is to create your primary feature block It is not recommended to launch OneNote, Outlook, and Sharepoint due to the customization settings that are better preserved. 1. In the Launch Applications page, select and launch all desired applications to generate the primary feature block for each application. 2. 3. 5. Configure SharePoint proxy registry settings 1. 2. Click Next. Once sequencing completes, click Finish. Click the Virtual Registry tab. Create a new Key named TreatAs under each of the following keys: If you are sequencing on a 32-bit OS, the keys are: MACHINE\Software\Classes\CLSID\{9203C2CB-1DC1-482D967E-597AFF270F0D} MACHINE\Software\Classes\CLSID\{BDEADEF5-C265-11D0BCED-00A0C90AB50F} MACHINE\Software\Classes\Wow6432Node\CLSID\{9203C2C B-1DC1-482D-967E-597AFF270F0D} MACHINE\Software\Classes\Wow6432Node\CLSID\{BDEADEF 5-C265-11D0-BCED-00A0C90AB50F}

If you are sequencing on a 64-bit OS, the keys are: 3.

Verify that the new TreatAs keys you created are set to Override Local Key - Right-click the key, select Key, verify the checkmark next to Override Local Key. Verify that the following virtual registry key is set to Merge with Local: If you are sequencing on a 32-bit OS, the key is: MACHINE\Software\Microsoft\Office\14.0 MACHINE\Software\Wow6432Node\Microsoft\Office\14.0 If you are sequencing on a 64-bit OS, the key is:

6.

Configure Office 2010 registry setting

1.

2.

Right-click the key, select Key, verify the checkmark next to Merge with Local Key.

Important: Perform the following steps if you are deploying Office 2010 to machines that already have Office 2007 installed (Office 2007 and Office 2010 co-existence). Otherwise, skip the rest of these steps

and continue. 3. Create the following registry sub-key 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 sub-key and make sure that the sub-key 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. 4. In the menu toolbar, select Tools, Sequencing Wizard 5. 6. 7. Select Next. Set the sequencer to Begin Monitoring. Create the following virtual registry sub-key and then delete it so that the sequencer monitors the deletion of the newly added key: 8. 9. Configure virtual applications to interact with the local environment HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook \Addins\Microsoft.OMSAddin

Select Stop Monitoring and continue to click Next/Finish to get back to advanced sequencer properties page.

Note: You may need to add some of these XML nodes if they do not currently exist. 1. For each OSD, add TRUE to the following Element text of the tag: SOFTPKG -> IMPLEMENTATION -> VIRTUALENV -> POLICIES -> LOCAL_INTERACTION_ALLOWED.

Configure a Client machine to run Office 2010

Tasks Prepare the client machine Install the Microsoft Office 2010 Deployment Kit Detailed steps Perform the following on the client machine. 1. 1. 2. 1. 2. 3. Install the App-V client, if you have not already done so. Download the Deployment Kit and extract the .exe. Open a command prompt with administrative privileges. Navigate to the directory containing the Offvirt.msi. Execute the following command: msiexec /i OffVirt.msi [licensing flags]

After extracting the .exe, you should have an OffVirt.msi file. 2.

You must enter a proper licensing flag below to properly configure the Deployment Kit; otherwise, functionality may be incorrect. Licensing Flags: To determine which activation (and licensing flags) to use, learn more

about Office 2010 volume activation here. 1. KMS activation: Setting these flags to 1 will install the KMS client key for the specified products. Properties for Office 2010 suites:
Flag PROPLUS SMALLBUSBASICS STANDARD Value 0 or 1 0 or 1 0 or 1 Enables licensing for: Office Professional Plus Small Business Basics Standard

Properties for Office 2010 standalone applications:

Flag: ACCESS EXCEL GROOVE INFOPATH ONENOTE OUTLOOK POWERPOINT PROJECTPRO PROJECTSTD PUBLISHER SPD VISIOPREM VISIOPRO VISIOSTD WORD Value 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 Enables licensing for: Access Excel SharePoint Workspace InfoPath OneNote Outlook PowerPoint Project Professional Project Standard Publisher SharePointDesigner Visio Premium Visio Professional Visio Standard Word

Properties for KMS Host configuration

Flag: KMSSERVICENAME Value [Host] Description: Enter KMS hostname (not required if KMS host is registered on DNS and port = 1688.) Not required if KMS host is registered on DNS and port = 1688.

KMSSERVICEPORT

[Port]

2.

MAK activation: Option 1: Use VAMT 2.0 (recommended) to install product keys on client machines streaming Office 2010. Option 2:
Flag: PIDKEYS Multiple product keys are semi-colon delimited. Ex. PIDKEYS=X-X-X-X-X; Value: XXXXX-XXXXX-XXXXX-XXXXXXXXXXX

Y-Y-Y-Y-Y; USEROPERATIONS 0 or 1

Important! You must set USEROPERATIONS=1 to allow a user to activate licensing on the client machine. Example MAK activation: msiexec /i OffVirt.msi PIDKEYS=XXXXX-XXXXX-XXXXXXXXXX;YYYYY-YYYYY-YYYYY-YYYYY-YYYYY USEROPERATIONS=1

3.

Mixed activation (KMS/MAK): If you want some client machines to use KMS activation, but others to use MAK. Use the KMS flags to install KMS client keys. Use VAMT 2.0 to install MAK key post-deployment.

Perform Step 2 only if you have configured proxies during the sequencing step. 2. (Optional) Enable the Proxies on the client 1. To enable the virtual proxies for the package open a command prompt as an administrator. Run the following command:

msiexec /i <Path to the OffVirt.msi>\OffVirt.msi ADDDEFAULT=Click2runOneNoteProxy,Click2runOutlookProxies,Click2r unWDSProxy,Click2runOWSSuppProxies PACKAGEGUID=<SFT package GUID with {}> 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 config> OWSSUPPServer=<app name for sharepoint proxy >

For example:
msiexec /i c:\OffVirt.msi ADDDEFAULT=Click2runOneNoteProxy,Click2runOutlookProxies,Click2r unWDSProxy,Click2runOWSSuppProxies PACKAGEGUID={5971AF75-78314AE9-906F-0F30C7DD0CA5} PACKAGEVERSION=14.0.4763.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

Known Issues
Why cant I launch x64 Visio 2010 during the monitoring phase of sequencing on an x64 Vista machine? This is a known issue. To solve the issue, restart monitoring by pressing stop monitoring and restart monitoring.

Visio 2010: Cannot create new block timeline This is a known issue and we are currently working on a fix.