Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Supported scenarios for deploying Microsoft Office as an App-V package


Summary

The deployment of Microsoft Office as a sequenced Microsoft Application Virtualization (App-V) package is a common request. This article describes the supported scenarios for various versions of Microsoft Office and Microsoft App-V.

The following product versions are included in this article:

  • Microsoft App-V 5.0 Service Pack 2 (SP2) and earlier versions, Microsoft App-V 4.6
  • Microsoft Office 2013, Microsoft Office 2010, Microsoft 2007 Office

↑ Back to the top


More Information

Supported versions of Microsoft Office on App-V 

App-V 5.0 supports Microsoft Office 2013, Microsoft Office 2010, and Microsoft 2007 Office. Before you deploy Microsoft Office, the software must first be packaged into the App-V file format. The packaging process can be done by using several different methods, depending on the version of Office and App-V that you use. The table in this section lists the supported Office versions on App-V, their package creation methods, and supported licensing and deployment information. The following package creation methods are used to package Office in the App-V format:

  • Sequencing by using prescriptive guidance: This is a text document that describes specific steps that a sequencing engineer requires to create an App-V package. For 2007 office, prescriptive guidance is the only available package creation method. This method is an option to sequence Office 2010 App-V packages.
  • Sequencing by using Package Accelerator: Package Accelerator was introduced in App-V 4.6 Service Pack 1 (SP1). It provides an easy method to generate an App-V package. You can use Package Accelerator to generate Office 2010 App-V 4.6 packages. To access Package Accelerator, see the "References" section.
  • Office Deployment Tool (ODT): The Office Deployment tool lets administrators create an Office 2013 App-V package. In fact, it is  the only way to do this. Office 2013 App-V packages that are created by using the ODT are ready for deployment in the same manner as any other App-V packages that are created by using the sequencer. 

Supported Office version

Supported App-V version

Package creation method 

Supported licensing

Supported deployments

Office 2013 App-V Package

5.0 SP2

Office Deployment Tool

Subscription

 

Desktop
Personal VDI  

Office 2013 App-V Package

5.0 SP2

Office Deployment Tool

Volume Licensing

Desktop
Personal VDI
Pooled VDI
RDS

Office 2010

5.0 SP2 and earlier versions, 4.6

Sequencing by using prescriptive guidance

Sequencing by using Package Accelerator

Volume Licensing

Desktop
Personal VDI
RDS 

Office 2007

5.0 SP2 and earlier versions, 4.6

Sequencing by using prescriptive guidance

Volume Licensing

Desktop
Personal VDI
RDS

 

References

 

Office 2013 App-V 5.0 packages

How to deploy and manage Office 2013 on App-V 5.0

Virtualizing Microsoft Office for Application Virtualization (App-V) 5.0

Office Deployment Tool for Click-to-Run


Office 2010 App-V 5.0 packages

Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0

Known issues when you create or use an App-V 5.0 Office 2010 package

How to sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0

 

Office 2010 App-V 5.0 Package Accelerator

App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 8

App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 7


2007 Office App-V packages

Prescriptive guidance for sequencing Office 2007 programs in Microsoft App-V (SoftGrid)

 

↑ Back to the top


Keywords: kb, vkball

↑ Back to the top

Article Info
Article ID : 2772509
Revision : 2
Created on : 3/27/2020
Published on : 3/27/2020
Exists online : False
Views : 69