You must enable shared computer activation. You must publish the Office package globally, not to the user.ĭeploying Microsoft 365 Apps for enterprise, Visio Pro for Office 365, or Project Pro for Office 365 to a shared computer using Remote Desktop Services. You can only publish one Office package per client computer. For more information, see Deploying Visio 2013 and Project 2013 with Office. If you're deploying Microsoft Visio 2013 and Microsoft Project 2013 along with Office, you must include them in the same package with Office. The Sequencer doesn't support package creation. In App-V and later, you must use the Office Deployment Tool to create packages. TaskĪll Office applications you wish to deploy to users must be in a single package. Packaging, publishing, and deployment requirementsīefore you deploy Office with App-V, review the following requirements. Planning for using App-V with coexisting versions of OfficeĬonsiderations for installing different versions of Office on the same computer. Supported deployment types like desktop, personal Virtual Desktop Infrastructure (VDI), and pooled VDI The following table will direct you to more information about which versions of Office App-V supports and how to run App-V with coexisting versions of Office. Supported Office versions and Office coexistence What to know before you startīefore you deploy Office 2013 with App-V, review the following planning information.

To successfully deploy Office 2013 with App-V, you need to be familiar with Office 2013 and App-V. For information about using App-V to deliver Office 2010, see Deploying Microsoft Office 2010 by Using App-V.

Use the information in this article to use Application Virtualization (App-V) to deliver Microsoft Office 2013 as a virtualized application to computers in your organization. Deploying Microsoft Office 2013 by Using App-V

Endnote word 2013 plugin