You can deploy patches using patch policies or Deploy Remediation. Since the integration of patch policies in ZENworks Patch Management, the manual process of Deploy Remediation, is generally used by exception. See Distribute and Apply Patches.
Patches are released frequently, and it is possible to automate the entire release process by using the deployment settings. While this may suit some smaller companies, in a large organization with multiple platforms and sites, we recommend that administrators design a strategy for deployment. Each patch for each software update will behave differently, which is why it is necessary to control the process. For example, some software will require a reboot after updating, and although ZENworks can manage this process on your behalf, your team should determine the details of this, and be aware of any other software or processes which are running, or patches that are being installed concurrently. The Best Practice recommendation for controlling these processes is to used a phased approach.
Implementing patch management tools in phases allows process and user communication issues to be addressed with a small group before deploying the patch application universally. Most organizations deploy patch management tools first to standardized desktop systems and single-platform server farms of similarly configured servers. Once this has been accomplished, organizations should address the more difficult issue of integrating multi-platform environments, nonstandard desktop systems, legacy computers, and computers with unusual configurations. Manual methods may need to be used for operating systems and applications not supported by automated patching tools, as well as some computers with unusual configurations; examples include embedded systems, industrial control systems, medical devices, and experimental systems. For such computers, there should be a written and implemented procedure for the manual patching process.