3 ms·
>Updates are excruciatingly painful and there is no technical reason I can fathom Technical reason is they don't really want to do them and they are difficult
by stackskipton 2y ago
>Updates are excruciatingly painful and there is no technical reason I can fathom
Technical reason is they don't really want to do them and they are difficult to get right. Office365 does not run Exchange updates, so they don't get properly exercised. The only reason they haven't dropped support for in place updates is customer screaming but trust me, Exchange team would love to.
Proper Office365 way to update Exchange is build new machines, patch them fully, install new Exchange version and move all the mailboxes over.
- p_ing 2y agoIs that the proper way in EXO? SPO had individual file replacements. SharePoint stamps were not pave-and-build.
- stackskipton 2y agoFor Exchange it is. Microsoft officially puts out patches for Exchange and technically patching is supported, it's just Exchange Online does not do it so it's poorly tested and when working with Microsoft 8+ years ago, they told us to rinse and replace. I developed a bunch of Powershell scripts to do it before I stopped being Exchange admin.
- p_ing 2y agoAh I thought you were referring to EXO the service, not Exchange Server. Yes, Exchange Server has been a full ISO deployment for many years, now.