Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Overview of the patching process for Microsoft Windows

BMC Server Automation patch management for Microsoft Windows starts with the creation of a catalog of patches. After you create and update a patch catalog, you run a Patching Job to identify missing patches on your servers.The next step is a Remediation Job, which creates software packages containing the patch payloads. The Remediation Job also creates Deploy Jobs for the servers that you want to remediate. You run the Deploy Jobs to apply the patches to the servers. 

In each phase of the patch management process, you control the scope of the jobs. You also monitor and verify each stage before moving to the next stage. You have complete control over when each job runs. Patch downloads can occur directly from vendor websites over the Internet (online mode) or in a separate operation previous to the patching process (offline mode).

The following figure illustrates the sequence of jobs in the BMC Server Automation patch management process. Some tasks can be accomplished at several points in the process depending on the options you select. This figure shows the process as it occurs using the recommendations in the topics that follow.

The procedures and examples in these topics assume that you have a:

  • BMC Server Automation environment that is configured and operational
  • Basic understanding of the BMC Server Automation Console (the console)
  • Basic understanding of BMC Server Automation patching concepts.
    Although the examples show a Windows environment, you can use the same general procedures for other server environments. For information about operating system (OS) specific differences, particularly in the catalog creation and Patching Job phases, see Patch management.
Was this page helpful? Yes No Submitting... Thank you