![]() ![]() The XML file can be a bit overwhelming at first, but as you break down each section, you can see how it can be quite simple, and how you can then modify each section to fit your individual needs. Let’s first look at an XML file and go over the sections: Please note, that the options you have for channels have now changed, for more info see the updated docs As long as you know what you want to install, what you want to exclude, and how you want to control your installation process, you can build the XML during the deployment. If you understand these elements, you can treat them like “LEGO” bricks. In this post, we’re going to go over the magic of PowerShell and creating an XML file on the fly.īasically, when you break down the XML, you get different elements that control the way Office is installed. We also touched on the crazy amount of variations you might have to support. In the previous post on Deployment and Maintenance of Office 365 using Microsoft’s Endpoint Manager, Configuration Manager (SCCM), I walked you through the generic process to create an Office Installer Application using Configuration Manager. Office 365 Deployment with ConfigMgr Post 3: Creating the Office Installer (advanced)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |