- This topic has 1 reply, 2 voices, and was last updated 1 year ago by .
-
Posts
-
Hi,
BatchPatch is our great tool to do so many things. But his main primary goal when we purchase it was “patching” our sytem (install Microsoft Update). It still make the job perfectly for the products are receiving their update from Microsoft Update/WSUS mechanism !
Since several months we started our migration from Office 2016 (MSI) to Office 2021 LTSC or Microsoft 365 (C2R) where the update mechanism is totally different. Office updates are no longer received from Microsoft Update or WSUS, but from the Office CDN… And the trigger to launch detection is also independant from Windows Update now (no more possible to use wuauclt and usoclient)
It still possible for Office C2R versions to force manually update verification, it’s also possible for us to create manually a Remote Command inside BatchPatch, but could you improve your tool to natively include a new action section “Office updates” where it could be possible to:
– Validate if computer have Office C2R version installed
– Launch Office Update
– Set some extra options related to the update mechanism
– Easly return the result of the update process
– Return the Office version (before/after update)Regards
Thank you for the suggestion. We’ll consider this for a future build.
- You must be logged in to reply to this topic.