Bruce is a 45-year-old IT manager, with twenty years experience working for ACME Power. Bruce has three photos on his desk – one of his wife, Linda; one of his kids - Davy and Wendy; and one of Microsoft CEO Satya Nadella. Apart from his laptop, Bruce’s desk is pristine. He walked into the office this morning with a big smile on his face and passed out donuts to his colleagues.
Today has been highlighted in Bruce’s Outlook calendar for weeks. It’s day one of a thorough compliance audit of ACME Power’s application and server infrastructure.
In a world where we have self-driving cars, cures for complex diseases, and where we’re building houses with 3D printers, some enterprise organizations still manually patch servers which run their mission-critical applications.
Enterprise data center management can fray the nerves of even the most experienced administrators. “To err is human”, as the saying goes, and errors can happen during patching, even with the powerful toolset in Microsoft System Center. A server admin could spend hours struggling with a single patch and cause productivity delays the next day for the systems which don’t get addressed.
There are effective ways of automating these tasks, which come with price tags both directly and indirectly related to patching itself.
Automated patching server application patching can alleviate a lot of work for IT management teams. It shifts the patching and updating process outside of business hours. In an ideal world, Microsoft’s System Center Configuration Manager (SCCM) would flawlessly execute server application patches.
However, there are some gaps in SCCM patching functionality, especially when it comes to orchestration, validation, and report logs. These can cause issues with QA and risk mitigation and can drive frustrations among your IT staff.
Why do companies do this with software?
The concept sounds crazy. Logic says that you lease a car, start to drive it immediately, and continue to drive it for the lease term. Yet with Microsoft software, even cloud-based software like Azure, O365, Dynamics CRM, and Windows 10, companies continue to buy SaaS offerings on their traditional Enterprise Agreements (EAs) and pay for them before they start to use them.
With any migration or upgrade, challenges will arise. Windows 10 migration is no different – so be prepared.