You are currently offline, waiting for your internet to reconnect

How to sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0

Summary

This document describes a method that you can use to sequence Microsoft Office 2010 for use with Microsoft Application Virtualization (App-V) 5.0. To sequence Office 2010 by using the package accelerators that are issued by Microsoft, see the following resources:

The method that is described in this article is not the only method that is available. You may have to adjust the information in the article as appropriate for your particular environment.

Important Before you start to sequence, we strongly suggest that you read through this article several times to become familiar with your configuration options.
More Information

Microsoft Office 2010 uses the Office Software Protection Platform (OSPP) service. This service uses the same activation technology that is used to activate volume editions of Windows Vista, Windows 7, and Windows 8 and is contained in the Office 2010 Deployment Kit for App-V. Before you sequence Office 2010, this service must be installed and configured on the App-V 5.0 sequencer.

Before you start to sequence Office 2010, it is important to determine the sequencing path that you should follow. If your organization must be able to open and edit documents that are located on a Microsoft SharePoint site, or if you must have Fast Search functionality in Outlook Search, you will have to follow the instructions in this document for sequencing with integration. (This is the most common scenario.) If this functionality is not important to you, you should sequence without integration and skip the steps that begin with Skip for non-integration scenarios.

Sequencing with integration

The OSPP service is automatically installed on any App-V 5.0 client computers to which you want to stream Office 2010 when you publish the Office 2010 App-V package to those computers.

Sequencing without integration

You have to manually install the Office 2010 Deployment Kit for App-V on every App-V 5.0 client computer.

Prerequisites

The prerequisites for sequencing Office 2010 for use together with App-V are as follows:

  • Microsoft Application Virtualization version 5.0 or App-V 5.0 Service Pack 1 (SP1)
  • Microsoft Office 2010 Sequencing Kit for Application Virtualization 5.0
    The sequencing kit enables Office integration features and can be downloaded from Microsoft Office 2010 Sequencing Kit for Application Virtualization 5.0.
  • Microsoft Office 2010 Deployment Kit for App-V
    The deployment kit contains the required Office 2010 licensing service (OSPP) and is available here: http://www.microsoft.com/en-us/download/details.aspx?id=10386.
  • Microsoft Office 2010 volume SKU (32-bit or 64-bit)
    Integration is not supported on 64-bit versions of Office 2010. However, sequencing and deployment of 32-bit Office 2010 on 64-bit computers is supported.

Step 1: Prepare a reference computer for sequencing

a. Prepare the sequencing computer by following the guidelines that are provided in the "App-V 5.0 Sequencing Guide.docx" document that is available at http://www.microsoft.com/en-us/download/details.aspx?id=27760.  If you do not follow the guidelines in the sequencing document, you may experience errors in functionality.

b. Set the Windows Update service to Disabled, and then stop the Windows Update service.

c. Install the App-V 5.0 sequencer if you have not already done this.

Step 2: Download, extract and install the Office 2010 Deployment Kit for App-V

a. Download, extract, and install the Office Deployment Kit for App-V that is available at Microsoft Office 2010 Deployment Kit for App-V. Please make sure that you download both the x86 and x64 versions of the kit. Setup will extract the Office 2010 Deployment Kit for App-V and then ask you where you want to save the files.

Note For the folders to which you extracted the x86 and x64 versions, this procedure will refer to the x86 folder as DEPLOYMENT_KIT_32_FOLDER and to the x64 folder as DEPLOYMENT_KIT_64_FOLDER from this point forward.

b. Open an elevated command prompt.

c. If you are sequencing on an x64 computer, locate the DEPLOYMENT_KIT_64_FOLDER directory. Otherwise, locate the DEPLOYMENT_KIT_32_FOLDER directory.

d. At the command prompt, run the following command:

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

Use feature flags for the architecture that matches your sequencing station operating system:

For x86: ADDLOCAL=OSpp,OSpp_Core
For x64: ADDLOCAL=OSpp,OSpp_Core,OSppWoW64

For Licensing Flags, you must enter one of the licensing flags in the following list to correctly configure the deployment kit. Otherwise, functionality may be incorrect. To learn more about which activation and licensing flags to use, go to the following Microsoft website:

Office 2010 volume activation (http://blogs.technet.com/office2010/archive/2009/08/24/volume-activation.aspx)

KMS activation

Setting any of these flags to 1 will install the KMS client key for the specified product.

Properties for Office 2010 suites

Flag

Value

Product for which licensing is enabled

PROPLUS

0 or 1

Microsoft Office Professional Plus

SMALLBUSBASICS

0 or 1

Microsoft Office Small Business Basics

STANDARD

0 or 1

Microsoft Office Standard

Properties for Office 2010 stand-alone applications

Flag

Value

Product for which licensing is enabled

ACCESS

0 or 1

Microsoft Access

EXCEL

0 or 1

Microsoft Excel

GROOVE

0 or 1

Microsoft SharePoint Workspace

INFOPATH

0 or 1

Microsoft InfoPath

ONENOTE

0 or 1

Microsoft OneNote

OUTLOOK

0 or 1

Microsoft Outlook

POWERPOINT

0 or 1

Microsoft PowerPoint

PROJECTPRO

0 or 1

Microsoft Project Professional

PROJECTSTD

0 or 1

Microsoft Project Standard

PUBLISHER

0 or 1

Microsoft Publisher

SPD

0 or 1

Microsoft SharePoint Designer

VISIOPREM

0 or 1

Microsoft Visio Premium

VISIOPRO

0 or 1

Microsoft Visio Professional

VISIOSTD

0 or 1

Microsoft Visio Standard

WORD

0 or 1

Microsoft Word

Properties for KMS host configuration

Flag

Value

Description

KMSSERVICENAME

[Host]

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

KMSSERVICEPORT

[Port]

This is not required if the KMS host is registered in DNS and port = 1688.

Example 1

KMS activation, default KMS host settings, on a 32-bit sequencing station:

msiexec /i OffVirt.msi [featureflags] PROPLUS=1 VISIOPREM=1


Example 2

KMS activation, user-defined KMS host settings, on a64-bit sequencing station:

msiexec /i OffVirt.msi [featureflags] PROPLUS=1 PROJECTPRO=1 KMSSERVICENAME=”kms.contoso.com” KMSSERVICEPORT=1689


MAK activation

Option 1


Use VAMT 2.0 (recommended) to install product keys on client computers that are streaming Office 2010.

Option 2

Flag

Value

PIDKEYS
Multiple product keys are semicolon delimited. For example:
PIDKEYS=X-X-X-X-X; Y-Y-Y-Y-Y;

XXXXX-XXXXX-XXXXX-XXXXX-XXXXXX

USEROPERATIONS

0 or 1

Important You must set USEROPERATIONS to 1 (USEROPERATIONS=1) to let a user enable licensing on the client computer. 

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

msiexec /i OffVirt.msi [featureflags] 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, follow these steps:

    1. Use the KMS flags to install KMS client keys.
    2. Use VAMT 2.0 to install the MAK key after the deployment.

Step 3 (skip for a non-integration scenario): Download and extract the Office 2010 Sequencing Kit for App-V

Download the Office 2010 sequencing kit (Microsoft Office 2010 Sequencing Kit for Application Virtualization 5.0), and extract the files on the sequencing computer to a folder (for example, C:\SequencingKit). This folder will be referred to as SEQUENCING_KIT_FOLDER from this point forward.

Step 4: Sequence Office 2010

a. Start the App-V 5.0 sequencer.

Note Office 2010 sequencing relies on setting a primary virtual application directory. As of App-V 5.0 SP3, this feature is hidden for creating sequenced packages. To enable this feature, take one of the following actions:

Start the App-V 5.0 sequencer with EnablePVADControl flag "Sequencer.exe -EnablePVADControl." 

Create the DWORD registry entry EnablePVADControl = 1 in HKLM\Software\Microsoft\AppV\Sequencer\Compatibility.  Then, start the App-V 5.0 sequencer as usual.

b. Click Tools -> Options.

c. On the Exclusion Items tab, and add the following:

[{Common AppData}]\Microsoft\OfficeSoftwareProtectionPlatform
[{Common AppData}]\Microsoft\Windows

With Mapping Type = "VFS"

d. Click Create a New Application Package.

e. (Skip for non-integration scenario) Start Windows Services, and then start the "Windows Search" Service if it's not already running.

f. Resolve any warnings that are shown by the sequencer before you move forward. (Ignore the warning about Windows Search running.)

g. On the Types of Application screen, select Standard Application (Default).

h. On the Select Installer screen, select Select the installer for the application.

i. Browse to your Office 2010 installer directory, select Setup.exe, and then click Next.

j. Type a name for the Office 2010 package.

k. Install to a new directory (for example, C:\Office2010) as the primary virtual application directory, and then click Next. The Office installation directory will be referred to as OFFICE_INSTALL_DIR going from this point forward in this procedure.

Note You cannot use the default file path. Please choose a path without spaces in its name, because the sequencing kit doesn't support a path that includes spaces.

l. The sequencer starts to monitor and starts the Office 2010 installer.

Important If you are sequencing Visio 2010, you have to use the following steps to make sure that it is licensed correctly. You must do this during installation. These steps apply to Visio 2010 only.

1. In the sequencer, select a custom installation.

2. When you are prompted, select Run.

3. Open a command prompt with administrative rights, and locate the setup executable for Visio 2010.

4. Start Notepad, and enter the following text:

<Configuration Product="Visio">
<PIDKEY Value="xxxxxxxxxxxxxxxxxxxx" />
</Configuration>

Note The placeholder xxxxxxxxxxxxxxxxxxxx represents 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 http://technet.microsoft.com/en-us/library/ee624355.aspx.

5. For more information about these parameters, see http://technet.microsoft.com/en-us/library/cc179195.aspx#BKMK_PIDKEY_MAK.

6. Save the file as Config.xml in the directory that contains the Visio setup executable.

7. From the open command prompt, run the following command:

setup.exe /config <absolute file path of Config.xml>

m. At the Choose the installation that you want screen, click Customize. In the Office installation procedure, make sure that you select Install to hard drive if you want that feature installed.

n. On the File Location tab, change the path of OFFICE_INSTALL_DIR so that it matches the directory that you selected for installation when you started monitoring (for example, C:\Office2010).

o. Click Install Now.

p. After the installation is complete, click Close.

Note The Office 2010 Installer may prompt you for a restart. In this case, you should select the option to restart the computer without exiting the sequencer. After the restart is completed, browse to the desktop. The sequencer will auto-start to resume execution from where it left off. (A UAC prompt will appear.) You can now go to the next step.

q. (Skip for a non-integration scenario) Keep the sequencer running on the "Installation" step, and open an elevated command prompt.

r. (Skip for a non-integration scenario) Go to where you extracted the Office 2010 sequencing kit for App-V 5.0, and run the following command below an elevated prompt:

Msiexec /I "App-V Seq Kit.msi" PACKAGEROOT= OFFICE_INSTALL_DIR

For example, you could run the following command: 

Msiexec /I "App-V Seq Kit.msi" PACKAGEROOT=C:\Office2010

s. (Skip for a non-integration scenario) Go to OFFICE_INSTALL_DIR\Integration. There you will find subfolders that are named "X86" and "X64."

Destination computer is 32-bit: If your destination client computers are running 32-bit Windows, copy the 32-bit version of OffVirt.msi from DEPLOYMNT_KIT_32_FOLDER to the OFFICE_INSTALL_DIR\Integration\X86 subfolder.

Destination computer is 64-bit: If your destination client computers are running 64-bit windows, copy the 64-bit version of OffVirt.msi from DEPLOYMENT_KIT_64_FOLDER into the OFFICE_INSTALL_DIR\Integration\X64 subfolder.

You will have to take both actions if your deployment destination computers are a mix of both platforms.

t. Go back to the Open Sequencer dialog box, select I am finished installing, and then click Next. The sequencer starts collecting system changes.

Step 5 (optional): While you are still in monitoring mode, start the virtual applications to configure first-start user settings

a. On the Configure Software screen in the sequencer, select and run the applications that you want to configure and for which you want to create the primary feature block.

Note We do not recommend that you start Microsoft OneNote, Microsoft Outlook, or Microsoft SharePoint. If you do not start these applications, the customization settings are better preserved.

b. Click Next to end the monitoring. The sequencer starts collecting system changes.

Step 6: Review the installation report

Click Next.

Step 7: Create a basic package or customize more

a. If you want to customize the package more, select Customize. Otherwise, select Stop Now, and then go to step 10.

b. Click Next

Step 8 (optional): Prepare for streaming

Note We do not recommend that you start Microsoft OneNote, Microsoft Outlook, or Microsoft SharePoint. If you do not start these applications, the customization settings are better preserved.

a. Run the applications that you want to optimize to run over slow networks.

b. Click Next.

Step 9 (optional): Restrict the operating systems for the package

Select the operating systems on which the package will be run.

Step 10: Document the package, and select output options

(Skip for Non-Integration scenario) If the package that is being created is intended to have integration features enabled, follow these steps:

a. Select Continue to modify package without saving using the package editor.

b. Click Next.

Otherwise, follow these steps:

a. Select Save the Package Now.

b. Click Create.

Step 11: Complete the package

a. Click Close.

b. If the package that is being created is intended to have integration features enabled, go to the next step. Otherwise, final package creation is completed. Therefore, skip all additional steps.

Step 12 (skip for a non-integration scenario)

a. On the Package Files tab, right-click the Package\Scripts folder, and then select Add.

b. Browse to select the Integrator.exe file from the directory to which the Office 2010 sequencing kit was extracted, and then click OK.

c. At an elevated command prompt, go to the directory to which the Office 2010 sequencing kit was extracted, and then run the following command:

manifestUpdater.exe LICENSE="[licensing flags]"

Examples are as follows:

manifestUpdater.exe LICENSE="PROPLUS=1 USEROPERATIONS=1"

manifestUpdater.exe LICENSE="PROPLUS=1 PROJECTPRO=1 KMSSERVICENAME=”kms.contoso.com” KMSSERVICEPORT=1689"

Step 13: (skip for a non-integration scenario): Save the package

a. On the File menu, select Save As, and then type a file name under which to save the package. The Office 2010 integrated package is now successfully sequenced. 

b. Restart the Windows Update service.

Deploying the Office 2010 package on App-V 5.0

After you build an Office 2010 package, you can deploy it to your App-V 5.0 clients by following the documentation that is available here:

http://technet.microsoft.com/en-us/library/jj713487.aspx

Note Only a single Office 2010 App-V 5.0 package can be deployed to a client computer. Scenarios that involve multiple App-V 5.0 Office 2010 packages that are deployed on a client are not supported.

If you sequenced with integration, you do not have to install the Office deployment kit on the App-V clients because the package publishing process will take care of that. Otherwise, install the Office deployment kit on all App-V clients before you publish the package.

If you sequenced with integration, the package must be published globally.

Before you deploy the package, please make sure that you enable scripting on the App-V 5.0 clients. You can do this through Windows PowerShell by opening an elevated PowerShell command prompt on the App-V 5.0 client and then running the following command:

Set-AppvClientConfiguration -EnablePackageScripts 1

If you sequenced without integration, Shortcuts Enabled in the DeploymentConfig.xml file should be set to True to avoid creating shortcuts.

To add a package together with the Deploymentconfig.xml file, that file should be specified as a part of the command:

Add-AppVClientPackage –Path \\path_of_the_package –DynamicDeploymentConfiguration \\path_of_the_deploymentconfigfile

Upgrading the Office 2010 package on App-V 5.0

The Office 2010 package can be updated with new hotfixes or updates to Office 2010. You have to upgrade the package on the same platform as the one on which you created the original package. To upgrade an existing Office 2010 package, follow these steps.

Setting up the reference computer for sequencing

Repeat steps 2, 3 and 4 to set up the App-V 5.0 sequencer computer, and then install the App-V 5.0 sequencer. Please make sure that the sequencing computer is used only for this upgrade operation and is not used for more sequencing after the upgrade process is complete.

Upgrading the package

1. Copy the package that has to be upgraded to the sequencer computer.

2. Grant access permissions to the WinSxS folder on the sequencing computer.

a. Change the owner of the folder %Windir%\WinSxS (typically C:\Windows\WinSxS) to the user who is performing the upgrade operation (or the group including that user). This includes subcontainers and objects. To do this, right-click %Windir%\WinSxS, and then select Properties. Click Security -> Advanced. On the Owner tab, click Edit, and then select Replace owner on subcontainers and objects.

b. Grant full control permissions of the folder %Windir%\WinSxS to that user. This includes its subfolders. (You may have to reopen Properties after you change ownership, as was stated earlier.) To do this, right-click %Windir%\WinSxS, and then select Properties. Click Security -> Advanced. On the Permissions tab, select the user or group, and then click Change Permissions. Select the user or group again, select “Replace all child object permissions with inheritable permissions from this object, and then click Edit. Select Full Control, select This folder, subfolders and files, and then click OK.

3. Start the App-V 5.0 sequencer, select Modify an Existing Virtual Application Package, and then select Update Application in Existing Package to start the wizard.

4. Select the existing Office 2010 App-V package.

5. Select Perform a Custom Installation, and then click Next.

6. The sequencer is now in the monitoring stage. Install the hotfixes or updates that you have to install.

7. Select I am finished installing, and then click Next.

8. (Optional) Run each program.

Note We do not recommend that you start Microsoft OneNote, Microsoft Outlook, or Microsoft SharePoint. If you do not start these applications, the customization settings are better preserved.

9. Continue to modify the package by using package editor.

a. On the Package Files tab, right-click the Package\Scripts folder, and then select Add.

b. Browse to select the Integrator.exe file from the directory where the Office 2010 sequencing kit was extracted, and then click OK.

d. At an elevated command prompt, go to the directory where the Office 2010 sequencing kit was extracted, and then run the following command:

manifestUpdater.exe LICENSE="[licensing flags]"

Examples are as follows:

manifestUpdater.exe LICENSE="PROPLUS=1 USEROPERATIONS=1"

manifestUpdater.exe LICENSE="PROPLUS=1 PROJECTPRO=1 KMSSERVICENAME=”kms.contoso.com” KMSSERVICEPORT=1689"

Licensing flags

Learn more about Office 2010 volume activation by using the instructions that are given in the "How to sequence Office 2010" section in the following resource to determine which activation and licensing flags to use: 

http://support.microsoft.com/kb/983462

See also http://blogs.technet.com/office2010/archive/2009/08/24/volume-activation.aspx.

10. Save the package.

On the File menu, select Save As, and then type a file name under which to save the package.

The Office 2010 App-V package is now updated. 

Note Office 2010 sequencing relies on a primary virtual application directory being set. As of App-V 5.0 SP3, this feature is disabled for creating sequenced packages. To enable this feature, take one of the following actions:

 Start the App-V 5.0 sequencer with the EnablePVADControl flag Sequencer.exe -EnablePVADControl.

Create the DWORD registry entry EnablePVADControl = 1 in HKLM\Software\Microsoft\AppV\Sequencer\Compatibility, and then start the App-V 5.0 sequencer as usual.

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.
Properties

Article ID: 2830069 - Last Review: 07/28/2015 15:44:00 - Revision: 8.0

Microsoft Application Virtualization 5.0 for Remote Desktop Services, Microsoft Application Virtualization 5.0 for Windows Desktops

  • KB2830069
Feedback
/html>f?DI=4050&did=1&t=">/html>/html>