You must enable shared computer activation.Įxcluding Office applications from a package 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 with Remote Desktop Services. You can only publish one Office package per client computer. For more information, see Deploying Visio 2016 and Project 2016 with Office. If you're deploying Microsoft Visio 2016 and Microsoft Project 2016 at the same time as Office, you must put them all in the same package.
The Sequencer doesn't support package creation. In App-V 5.0 and later, you must use the Office Deployment Tool to create packages.
TaskĪll Office applications that you 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 versions of Office and deployment types (for example, desktop, personal Virtual Desktop Infrastructure (VDI), and pooled VDI), and Office licensing options. Use the following table to get information about supported versions of Office and running coexisting versions of Office. Supported Office versions and Office coexistence What to know before you startīefore you deploy Office 2016 with App-V, review the following planning information. For information about using App-V to deliver Office 2010, see Deploying Microsoft Office 2010 by using App-V.
For information about using App-V to deliver Office 2013, see Deploying Microsoft Office 2013 by using App-V. Use the information in this article to use Application Virtualization (App-V) to deliver Microsoft Office 2016 as a virtualized application to computers in your organization.
0 kommentar(er)
