![]() ![]() If you are using C2R, and want some form of update control, you can modify the "branch", or configure the C2R updater so that it doesn't pull "builds" from the MSFT CDN instead point it to your own fileshare or webserver where you hostĭocumentation for C2R update management here:ĭon Non-C2R versions of Office 2010/2013/2016, use traditional setup.exe/MSI, and each update can be controlled individually via WSUS etc. So, for C2R, you can't exclude specific/individual "updates" because you get a bunch of updates within that single "blob". So if a particular update breaks functionality in Office (like the last set of updates did for me), how do I know what update did the breaking so I can exclude it from my WSUS deployment at work?Ĭ2R uses an auto-update mechanism by default, which streams the "new build" down to the machine from the MSFT CDN (Content Delivery Network), this is not a part of WindowsUpdate/MicrosoftUpdate.Ĭ2R updates (builds)(streams) come down as a single "blob" which is then unpacked as a whole.
0 Comments
Leave a Reply. |