Display progress of Office 365 Client Updates into WUAHandler log
When deploying the Office 365 Client Updates with ConfigMgr, there is no information currently written into the WUAHandler.log. All other software updates (including Office 2016) appear in the WUAHandler.log with an entry showing they are missing and once installed, an entry showing the install was finished, the exit code, and whether or not a reboot is required.
1) 1. Update (Missing): Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4015217) (4a4cfa3f-337e-496e-9d32-a143afcb27f4, 200)
2) Update 1 (4a4cfa3f-337e-496e-9d32-a143afcb27f4) finished installing (0x00000000), Reboot Required? Yes
There is currently no such information displayed for any Office 365 updates. If the WUAHandler.log contains information about all other updates deployed by ConfigMgr, it should also have information about Office 365 Updates.
Randy Diel commented
To add to this thread and revive:
The Office 365 Patches are logged to the alternatehandler.log, but the information is way too obscure, and the link to the activities occurring in the smsts.log and wuahandler.log should be far more clear and verbose than they are. For instance, a hand-off entry for the alternatehandler.log should be noted succinctly in the wuahandler.log so that it is clear that the work has been directed to occur from elsewhere, and that it is being recorded elsewhere. I would think it would be best if the language used when applying updates (o365 or otherwise) should be similar, if not exactly the same in alternatehandler.log as it is in the wuahandler.log, or at least similarly usable/readable.
this would be nice to see in the wuahandler i concur
Rather old thread but this is still the case. Office 365 updates from SUP is not logged in WUAHandler.log like all other patches.