Our teams work with your existing patch management solution to ensure all critical systems have all critical security patches applied within a timeline that is aligned to the exposure of the systems. We also ensure that the patching mechanisms covers not only the standard operating system patches, but also those that might be applicable to databases and critical endpoint software such as Microsoft Office, Java, Adobe, browsers, etc.
Scheduling server patches — Patch deployment may not be necessary every month if the vulnerabilities identified do not apply to the servers. However, in the event that no patches are needed, the servers will be rebooted every month, unless there is a customer need to remain available. With the large number of patches from Microsoft, you should assume that there will be critical patches every month and that patches will need to be installed with a reboot to follow.
There is a risk that something won’t function properly after the updates. This is very rare and in most cases, a patch can be uninstalled. The patching schedule takes this risk into consideration, and patches are applied to test, development, and non-critical systems first to mitigate potential failures.