I plan to hopefully at least test this idea soon. This would create drawbacks where some customers have indicated they wanted multiple configurations of the Office app in their environment/tenant one with base M365 apps, another with base apps + Project, another with base apps + Visio, another with base apps + Project + Visio.Īt this time, this is not natively possible via the Publisher's UI until this idea is implemented: - however if you executed a script client side (bundled as pre script via the right click option Add pre/post custom scripts) to determine the conditions as to whether the client should install with an alternate configuration XML, you can rename the XML on the fly to the file name specified Modify command lineĪs for detection, it could be non-version dependent - just detect whether or not M365 apps are on system, regardless of specific versions.

So, for example, instead of your users getting a bunch of Microsoft updates once a month followed by a reboot, they now get a bunch of Microsoft and third party updates once a month, followed by a reboot. The more I think about this, the more I foresee needing to let customers define their own XML for the ODT (to configure their own preferences for things like channel, language, products to be installed, etc) and we'll simply include the ODT as the binary in the catalogue.Ĭustomers would add their XML via the Add additional file(s) (in Add custom pre/post scripts), and then change Modify command line to specify the name of the XML file. Take your existing patching strategy, schedule, etc, and add the third-party updates to the Microsoft stuff you're already doing. Maybe also add a sample base pmpc xml? i'm available for testing purposes ^^

Patchmypc alternative