Add Office 365 Apps

Very important. This would help alot

bump

inbuilt intune or configmgr for 365 deployment really isnt that great

https://brookspeppin.com/2020/03/20/how-to-deploy-office-365-with-ws1/

Would really be nice to have this. Using Pmpc to create the package and maintain the odt updated we really would just need to create the xml. Eventually storing and maintaining a share with the bits for a completely offline full installer and as a sources for updating clients

https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/Software_Distribution/GUID-A00E59E6-29E3-4098-84AB-0753AC1DB960.html

interresting https://msendpointmgr.com/2022/10/23/installing-m365-apps-as-win32-app-in-intune/ but are still hoping pmpc will add this killer feature

+1

Would also be interesting in seeing this! Built-in 365 for Intune messes up ESP and using Win32 creates issues if office is already running.

To accommodate different instances could have multiple applications available?

• M365 Apps 1

• M365 Apps 2

• M365 Apps 3

• ...

Admins could then specify a different XML for each.

Custom detection methods would also be a nice-to-have for this app, due to all the varying configurations peoples might use. https://ideas.patchmypc.com/ideas/PATCHMYPC-I-2049

tesla incoming :P

i recommand

we are now also testing the intune integration… we need this now ^^

We would love to have a way to "get inbetween" O365 trying to go to the internet for these updates (which is traffic we don't want in our facilities internet pipes) and a way we can also better control approval. This would be AWESOME to do this in a more controlled manner via this channel

Yes please! Standard 365 Apps in Intune is flaky, to say the least.

maybe also add a sample base pmpc xml? i'm available for testing purposes ^^

<Configuration>

<Add SourcePath="\\patchmypc\Applications\Microsoft\Office 2019\x64" OfficeClientEdition="64" Channel="PerpetualVL2019" AllowCdnFallback="TRUE" ForceUpgrade="TRUE">

<Product ID="ProPlus2019Volume">

<Language ID="en-us" />

<Language ID="fr-fr" />

<Language ID="de-de" />

<Language ID="lb-lu" />

</Product>

<Product ID="VisioStd2019Volume">

<Language ID="en-us" />

<Language ID="fr-fr" />

<Language ID="de-de" />

<Language ID="lb-lu" />

</Product>

<Product ID="ProjectStd2019Volume">

<Language ID="en-us" />

<Language ID="fr-fr" />

<Language ID="de-de" />

<Language ID="lb-lu" />

</Product>

<Product ID="LanguagePack">

<Language ID="en-us" />

<Language ID="fr-fr" />

<Language ID="de-de" />

<Language ID="lb-lu" />

</Product>

<Product ID="ProofingTools">

<Language ID="en-us" />

<Language ID="fr-fr" />

<Language ID="de-de" />

<Language ID="lb-lu" />

</Product>

</Add>

<Property Name="PinIconsToTaskbar" Value="FALSE" />

<Updates Enabled="TRUE" />

<RemoveMSI />

<AppSettings>

<Setup Name="Company" Value="Patch My PC" />

</AppSettings>

<Display Level="None" AcceptEULA="TRUE" />

<Logging Level="Standard" Path="%temp%" />

<Property Name="FORCEAPPSHUTDOWN" Value="True" />

<Property Name="AUTOACTIVATE" Value="1" />

</Configuration>

Thats exactly how i supposed it to be implemented. Provide the odt binaries and we use our own custom xml configuration file with it. For starting i would already appreciate to have the possibility to only publish the base m365 apps configuration but yes the possibility to have multiple “configuration” available would be also neat but for now i think we can workaround it as you said with scripting. Yes i also dont see a need to check for specific versions for now.

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.

Customers 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.

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.

At this time, this is not natively possible via the Publisher's UI until this idea is implemented: https://ideas.patchmypc.com/ideas/PATCHMYPC-I-631 - 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

As for detection, it could be non-version dependent - just detect whether or not M365 apps are on system, regardless of specific versions.

I plan to hopefully at least test this idea soon. I would appreciate all your feedback on the idea above!

and also please add
<Product ID="LanguagePack">

<Language ID="en-us" />

<Language ID="fr-fr" />

<Language ID="de-de" />

<Language ID="lb-lu" />

</Product>

<Product ID="ProofingTools">

<Language ID="en-us" />

<Language ID="fr-fr" />

<Language ID="de-de" />

<Language ID="lb-lu" />

please start with current channel/latest version

any news? :D

This would be amazing!