How to sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0

Article ID: 2830069 - View products that this article applies to.
Expand all | Collapse all

Summary

This document describes one 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 leveraging the Package Accelerators issued by Microsoft, check here:

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 in the recipe that begin with Skip for non-Integration scenario.

Sequencing with Integration

The OSPP service would automatically be 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 machines.

Sequencing without Integration

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

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 SP1.
  • Microsoft Office 2010 Sequencing Kit for Application Virtualization 5.0: The sequencing kit enables the 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

1. Prepare the sequencing computer by following the guidelines that are provided in the "App-V 5.0 Sequencing Guide.docx" 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.

2. Set the Windows Update service to Disabled.

3. Install the App-V 5.0 sequencer if you have not already done so.

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

1. Download, extract and install the Office Deployment Kit for App-V, available at Microsoft Office 2010 Deployment Kit for App-V. Please make sure to 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 where you extracted the x86 and x64 versions, this recipe will refer to the x86 folder as DEPLOYMENT_KIT_32_FOLDER and to the x64 folder as DEPLOYMENT_KIT_64_FOLDER going forward.

2. Open an elevated command prompt.

3. If you are sequencing on an x64 machine, browse to the DEPLOYMENT_KIT_64_FOLDER directory, else browse to the DEPLOYMENT_KIT_32_FOLDER directory.

4. 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 (not required if KMS host is registered on DNS and port = 1688.)

KMSSERVICEPORT

[Port]

Not required if KMS host is registered on 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 activate 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 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 (e.g. C:\SequencingKit). This folder will be referred to as SEQUENCING_KIT_FOLDER going forward in this recipe.

Step 4: Sequence Office 2010

1. Start the App-V 5.0 Sequencer.

2. Click on Tools -> Options...

3. Open the "Exclusion Items" tab and add the following:

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

With Mapping Type = “VFS”

4. Click “Create a New Application Package”.

5. (Skip for Non-Integration scenario) Launch Windows Services and Start the "Windows Search" Service if it's not already running.

6. Take care of any warnings shown by the Sequencer before you move forward (Ignore the warning about Windows Search running).

7. On the screen titled Types of Application, choose "Standard Application (Default).

8. On the "Select Installer" screen, choose "Select the installer for the application".

9. Browse to your Office 2010 installer directory, choose setup.exe and click Next.

10. Provide a name for the Office 2010 package.

11. For the Primary Virtual Application Directory, install to a new directory (e.g.  C:\Office2010) and then click Next. The Office installation directory will be referred to as OFFICE_INSTALL_DIR going forward in this recepie.

Note: We cannot use the default file path. Please choose a path without spaces in it since the sequencing kit doesn't support a path with spaces.

12. The Sequencer begins monitoring and launches the Office 2010 installer.

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

a. Within the Sequencer, choose a custom installation.

b. When prompted, choose Run...

c. Open a command prompt with Administrative rights and locate the setup executable for Visio 2010.

d. Open Notepad, and enter the following text:

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

e. 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 http://technet.microsoft.com/en-us/library/ee624355.aspx.

f. For further guidance with these parameters, see http://technet.microsoft.com/en-us/library/cc179195.aspx#BKMK_PIDKEY_MAK.

g. Save the file as config.xml in the same directory as the Visio setup executable.

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

setup.exe /config <absolute file path to config.xml>

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

14. Click the File Location tab and change the path to OFFICE_INSTALL_DIR so that it matches the directory that you selected for installation when you started monitoring (e.g. C:\Office2010).

15. Click Install Now.

16. After the installation is complete click "Close".

NOTE: The Office 2010 Installer may prompt for a reboot, in which case you should select the option to reboot the machine WITHOUT exiting the Sequencer.  Once the reboot is completed, navigate to the desktop and the Sequencer will autolaunch to resume execution (a UAC prompt will appear) from where it left off and you can proceed on to the next sub-step in this recipe.

17. (Skip for Non-Integration scenario) Keep the Sequencer running on the "Installation" step and open an elevated command prompt.

18. (Skip for Non-Integration scenario) Go to the location where you extracted the Office 2010 Sequencing kit for App-V 5.0 and run the command below from an elevated prompt:

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

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

19. (Skip for Non-Integration scenario) Go to OFFICE_INSTALL_DIR\Integration and you will find "X86" and "X64" subfolders.

Target machine 32-bit: If your target client machines are 32-bit windows, copy the 32-bit version of OffVirt.msi from DEPLOYMNT_KIT_32_FOLDER into the OFFICE_INSTALL_DIR\Integration\X86 subfolder.

Target machine 64-bit: If your target client machines are 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 need to do both if your deployment target machines are a mix of both platforms.

20. Go back to the Open Sequencer dialog box and check "I am finished installing" and click "Next". The Sequencer will start collecting system changes.

Step 5 (optional): To configure first-start users settings, while you are still in monitoring mode, start the virtual applications

1. On the "Configure Software" screen in the Sequencer, select and run the applications that you want to configure and create the primary feature block for.

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.

2. Click Next to end the monitoring. The Sequencer will start collecting System changes.

Step 6: Review the installation Report

Click "Next"

Step 7: Create your basic package or customize further

1. If you want to further customize the package, select "Customize", otherwise Select "Stop Now" and proceed to Step 10 if no further customizations of the package are necessary.

2. 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.

1. Run the Applications you want to optimize to run over slow networks.

2. Click "Next"

Step 9. (Optional) Restrict the Operating Systems for the package

Choose the Operating Systems where the package will be run.

Step 10: Document the package and select output options

(Skip for Non-Integration scenario) If the package being created is intended to have Integration Features enabled:

1. Select "Continue to modify package without saving using the package editor".

2. Click "Next"

Otherwise:

1. Select "Save the Package Now".

2. Click "Create"

Step 11: Package completed

1. Click "Close".

2. If the package being created is intended to have Integration Features enabled, proceed to Step 13. Otherwise final package creation is completed so further steps have to be skipped. 

Step 12: (Skip for Non-Integration scenario)

1. Select the "Package Files" tab.

2. Right-click the Package\Scripts folder and select "Add".

3. Browse to select "integrator.exe" from the directory where the Office 2010 sequencing kit is extracted and click "OK".

4. From an elevated command prompt, go to the directory where the Office 2010 sequencing kit is extracted and run the following command:

manifestUpdater.exe LICENSE="[licensing flags]"

Examples:

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

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

Step 13: (Skip for non-Integration scenario) Save the package

From the "File" menu, choose "Save As…" and enter the file name to save the package. The Office 2010 integrated package has been successfully sequenced.

 

Deploying the Office 2010 package on App-V 5.0

Once you have built an Office 2010 package, you can deploy it to your App-V 5.0 clients by following the documentation available here:

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

NOTE: Only a single Office 2010 App-V v.50 Package can be deployed to a client machine.  Scenarios involving multiple App-V v5.0 Office 2010 packages deployed on a client are not supported.

If you sequenced with integration, you do not need to install the Office Deployment kit on the App-V clients as 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 to enable scripting on the App-V 5.0 clients. One way of doing that via PowerShell is to open an elevated PowerShell command prompt on the App-V 5.0 client and run the following command:

Set-AppvClientConfiguration -EnablePackageScripts 1

 

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 you created the original package. To upgrade an existing Office 2010 package, follow the steps below.

Set up the reference computer for Sequencing

Repeat Steps 2, 3 and 4 above to setup the App-V 5.0 Sequencer machine and install the App-V 5.0 Sequencer. Please ensure that the Sequencing machine is used only for this upgrade operation and is disposed of (i.e. not used for further sequencing) after the upgrade process is complete.

Upgrade the package

1. Copy the package that needs 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) including subcontainers and objects to the user who is performing the upgrade operation (or the group including that user). To do this, right-click %Windir%\WinSxS and choose “Properties”. Click on Security -> Advanced. Select the “Owner” tab and click on “Edit”. Select “Replace owner on subcontainers and objects”.

b. Grant full control permissions of the folder %Windir%\WinSxS (including its subfolders) to that user. (You may need to reopen “Properties” after changing ownership as stated above). to do this, right-click %Windir%\WinSxS and choose “Properties”. Click on Security -> Advanced. From the “Permissions” tab, select the user or group and click “Change Permissions”. Select the user or group again, select “Replace all child object permissions with inheritable permissions from this object” and click “Edit”. Select “Full Control”, Apply to “This folder, subfolders and files” and click “OK”.

3. Launch the App-V 5.0 Sequencer and choose "Modify an Existing Virtual Application Package". Choose "Update Application in Existing Package" to start the wizard.

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

5. Choose "Perform a Custom Installation" and click "Next".

6. Now the Sequencer is in the monitoring stage. Install the hotfixes or updates you need to install.

7. When you are done, check "I am finished installing" and 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 using package editor.

a. Select "Package Files" tab.

b. Right-click the Package\Scripts folder and select "Add".

c. Browse to select the "integrator.exe" file from the directory where the Office 2010 sequencing kit is extracted and click "OK".

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

manifestUpdater.exe LICENSE="[licensing flags]

Examples:

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 using the instructions given in the “Sequence Microsoft Office 2010” section in http://support.microsoft.com/kb/983462 (http://blogs.technet.com/office2010/archive/2009/08/24/volume-activation.aspx) to determine which activation and licensing flags to use.

10. Save the package.

a. From the "File" menu, choose "Save As…" and enter the file name to save the package.

The Office 2010 App-V package has now been updated.

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: September 26, 2013 - Revision: 4.0
Applies to
  • Microsoft Application Virtualization 5.0 for Remote Desktop Services
  • Microsoft Application Virtualization 5.0 for Windows Desktops
Keywords: 
KB2830069

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