Hi Charles,Patch management currently addresses all office packages, so you can't change anything. But BCM only download what the assigned devices report as need. So if you create a PatchJob that contains "Office" and only assigns this job to devices that have Office 365 installed, then only Office 365 Patches will be downloaded. BCM only download it because the devices also request it.
The installation folder is otherwise irrelevant to patch management. You wouldn't have to specify that if you update Office by hand (especially since this is not even possible with Office 365).
Otherwise, you could still use patch groups because you can choose which patch you want to deploy. You would then select only the Monthly Update and nothing else.
The third variant would be to distribute the patches via software deployment.Kind Regards,Philipp
Charles is looking for applying the Office updates from a local repository (eg : relay or master).
i found this in the KB :https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=kA33n000000Xg8CCAS&type=FAQ
The noop.exe file is a Microsoft file that they release to be used with 3rd party patching solutions for ex. BCM .
When run against Office 365 or Office Click-to-Run versions, the noop is calling the clicktorunupdate DLL which then ultimately kicks in the updates to reach out directly within the Office application to Microsoft and pull down the necessary updates.
Once the updates are downloaded, they are then installed using the built in Office update components.
After the update is installed successfully, it will report back its status to the noop.exe file and that's the status you'll ultimately see in the deployment tracker.
The endpoints reach out directly whit the Microsfot servers, Is there any solution to force the endpoints to connect the update path in the xml config file ?
Thanks for your help.