- #Volume licensing microsoft office 2013 how to
- #Volume licensing microsoft office 2013 pro
- #Volume licensing microsoft office 2013 plus
Create Office 2013 App-V packages using Office Deployment Tool In this topic, the term “Office 2013 App-V package” refers to subscription licensing and volume licensing. Review prerequisites for using the Office Deployment Toolīefore you start, ensure that the computer on which you're installing the Office Deployment Tool has the following prerequisites fulfilled: Prerequisite You cannot use the Sequencer to create packages. In App-V and later, you must the Office Deployment Tool to create a package. This file contains the default package settings for all users on a computer running the App-V Client.įor more information, see Disabling Office 2013 applications.Ĭreating an Office 2013 package for App-V with the Office Deployment ToolĬomplete the following steps to create an Office 2013 package for App-V or later. Modify the DeploymentConfig.xml file after creating the package. For example, you can use this setting to create a package that contains only Microsoft Word.įor more information, see ExcludeApp element. Use the ExcludeApp setting when you create the package by using the Office Deployment Tool.Įnables you to exclude specific Office applications from the package when the Office Deployment Tool creates the package. The following table describes the recommended methods for excluding specific Office applications from a package.
#Volume licensing microsoft office 2013 plus
You don’t need to use shared computer activation if you’re deploying a volume licensed product, such as Office Professional Plus 2013, Visio Professional 2013, or Project Professional 2013.Įxcluding Office applications from a package You must enable shared computer activation.
#Volume licensing microsoft office 2013 pro
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
#Volume licensing microsoft office 2013 how to
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