Skip to Main Content
Patch My PC Feature and Application Request

A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:

118 VOTE
Status SUBMITTED
Categories Application Request
Created by Guest
Created on Feb 12, 2021

Add Office 365 Apps

Office 365 Apps for Business and Enterprise are one of the most common failures for Windows Autopilot deployment failures that are reported. Differences in the CDN’s have shown that packaging the app as a Win32 app provides a more consistent experience, but that requires maintenance.

So it would be great if PMPC could take care of the maintenance side of things!

  • Attach files
  • Claudio Mendes
    Oct 27, 2022

    inbuilt intune or configmgr for 365 deployment really isnt that great

  • Claudio Mendes
    Oct 27, 2022

    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

  • Claudio Mendes
    Oct 24, 2022

    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

  • Claudio Mendes
    Sep 16, 2022

    +1

  • Andrew Fogg
    Sep 2, 2022

    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

  • Claudio Mendes
    Aug 22, 2022

    tesla incoming :P

  • Guest
    Jul 6, 2022

    i recommand

  • Claudio Mendes
    May 29, 2022

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

  • Justin Blocksom
    May 12, 2022

    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

  • Nick Wiley
    Apr 15, 2022

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

  • Claudio Mendes
    Apr 5, 2022

    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>
  • Claudio Mendes
    Apr 1, 2022

    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.

  • Admin
    Adam Cook
    Apr 1, 2022

    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!

  • Claudio Mendes
    Mar 31, 2022

    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" />

  • Claudio Mendes
    Mar 31, 2022

    please start with current channel/latest version

  • Claudio Mendes
    Mar 18, 2022

    any news? :D

  • Guest
    Feb 23, 2022

    This would be amazing!

  • Chris Kibble
    Feb 1, 2022

    @Adam - If there were entries for each channel and the latest version, couldn't the detection script just look at the registry for the channel and the VersionToReport key for the applicable version? This probably still requires you to have multi-file application support though, which I think I saw in another thread isn't yet supported.


    I would definitely use this if it became a thing in PMPC.

  • Claudio Mendes
    Nov 2, 2021

    +999

  • Load older comments
  • +52