RusselHairy

Speaking about replication to cloud, I would consider asynchronous replication only. Something like Storage Replica in WS2016. IMO this is the only feasible way to achieve high performance and have an ability of failing-over to the cloud in case of disaster. If there is a need to deploy a highly available infrastructure on-premise, a hyper-converged approach is often the most optimal, despite the significant CapEx. For most cases, if it is possible to fit everything into two beefy servers "powered by" HPE VSA/Starwind/whatever while still having some room for future growth, I'd rather stick with it instead of buying 5+ nodes to build a capable VMware VSAN or S2D cluster. The fewer components you have, the less is a probability of shit hitting the fan.

Thanks. I think this part of footage will be the one most spectacular throughout the whole translation

By the way, does anyone have a link to the footage of a failed middle booster? All I could find was a frame-by-frame 3 sec video which shows almost nothing.

If you are using SC Configuration Manager to push updates to your client boxes, never look at the Windows Update Manager on the client machine itself, it won't show anything useful. You should just check Configmgr reports to get the status of your updates and corresponding logs.