R
Roger_H
Guest
I've use the Office 2016 Deployment Tool to deploy Office 365 with System Center Configuration Manager, and set it to Exclude Access and Outlook. Below is the configuration.xml file I used for this -
<Configuration>
<Add OfficeClientEdition="32">
<Product ID="O365ProPlusRetail">
<Language ID="en-us"/>
<ExcludeApp ID="Access"/>
<ExcludeApp ID="Outlook"/>
</Product>
</Add>
<Display Level="None" AcceptEULA="TRUE"/>
<Logging Level="Standard" Path="C:\Temp\"/>
<Updates Enabled="FALSE" Channel="Deferred"/>
</Configuration>
This install works fine with Configuration Manager. I was wondering how I would now go about creating another Application in SCCM to add the Access (or Outlook) components to an existing install. In other words, we want to deploy Office 365 Pro Plus as standard to all machines without Access or Outlook, and when users request it, we will then deploy another SCCM application to their machines that adds the Access / Outlook component.
I was thinking that the way to do this would be to create 2 new configuration.xml files, one which no longer excluded Access and the other that no longer excluded Outlook (but did exclude Access). If I then created 2 new SCCM Applications that used these new XML files (one for Access and another for Outlook) then we could deploy the relevant application to machine, depending on which feature the user wanted added.
However, if I deploy the Application for Outlook to a machine that already had Access added, then the fact that Access was excluded in the XML file for Outlook means that Access would be removed when Outlook was added.
If my thinking above correct ? If so, then how do I go about achieving what I want to achieve ? Is there another way to add a component to an existing Office 35 ProPlus installation ?
Continue reading...
<Configuration>
<Add OfficeClientEdition="32">
<Product ID="O365ProPlusRetail">
<Language ID="en-us"/>
<ExcludeApp ID="Access"/>
<ExcludeApp ID="Outlook"/>
</Product>
</Add>
<Display Level="None" AcceptEULA="TRUE"/>
<Logging Level="Standard" Path="C:\Temp\"/>
<Updates Enabled="FALSE" Channel="Deferred"/>
</Configuration>
This install works fine with Configuration Manager. I was wondering how I would now go about creating another Application in SCCM to add the Access (or Outlook) components to an existing install. In other words, we want to deploy Office 365 Pro Plus as standard to all machines without Access or Outlook, and when users request it, we will then deploy another SCCM application to their machines that adds the Access / Outlook component.
I was thinking that the way to do this would be to create 2 new configuration.xml files, one which no longer excluded Access and the other that no longer excluded Outlook (but did exclude Access). If I then created 2 new SCCM Applications that used these new XML files (one for Access and another for Outlook) then we could deploy the relevant application to machine, depending on which feature the user wanted added.
However, if I deploy the Application for Outlook to a machine that already had Access added, then the fact that Access was excluded in the XML file for Outlook means that Access would be removed when Outlook was added.
If my thinking above correct ? If so, then how do I go about achieving what I want to achieve ? Is there another way to add a component to an existing Office 35 ProPlus installation ?
Continue reading...