Balancing server patching with maintaining the availability of the services that run on these servers can be a difficult task for an IT Pro, with lots of repetitive, time-consuming, and error-prone steps. Luckily, Orchestrator has emerged as an effective automation tool to help IT Pros manage the patching process. But what about when the Orchestrator service itself needs to be patched? How can an IT Pro ensure their enterprise automation continues to function despite the patching of the servers running Orchestrator components?
Joe Levy has published an interesting post to expose all steps to follow to be able to maintain high availability when patching Runbook Servers.
This posting is provided "AS IS" with no warranties.
No comments:
Post a Comment