Instead of having a hundred different command line switches, there is one XML to rule them all. This file (which can be named anything) is the “database” that the setup engine uses to know how to configure office. If you have the desire to do it standalone or are unfortunate and don’t have access to ConfigMgr, the process is still pretty simple to come by the installer package.īefore I go much further, I’m going to explain the Configuration.XML file. While Configuration Manager isn’t required to create and deploy Office 365, they have done a very nice job of making it simple. In this Deployment and Maintenance of Office 365 using Microsoft’s Endpoint Manager, Configuration Manager (MEMCM / SCCM) post, we’re going to get familiar with the Office 365 App Creation process that comes built into Configuration Manager. For more details, see Use the Office Deployment Tool to install volume licensed editions of Visio 2016 and Project 2016ĭownload the latest version of the Office 2016 Deployment Tool here.Office 365 Deployment Series with MEMCM – Pt.
The new Office Deployment Tool supports four new ProductIDs that allow the customers to download and install the standard or Professional versions of Project 2016 and/or Visio 2016. ResolutionĬustomers that are based on the scenario described above are now able to use the latest version of Office Deployment Tool (2016) to download and install click-to-run based Project 2016 and Visio 2016 that can be activated using their volume license (KMS or MAK).
This blocks customers from upgrading their versions of Project and Visio to 2016. While migrating the enterprise to Microsoft 365 Apps for enterprise (2016) they find out that the 2016 version of Microsoft 365 Apps for enterprise, which uses click-to-run, cannot be installed side by side with the 2016 version of Project and Visio that are MSI-based.
A customer has purchased Volume-Licensed perpetual copies of Project 2016 and Visio 2016.
0 kommentar(er)
