Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
Scenarios that warrant deploying additional Automation role servers are the most common when implementing Patch Manager in large or distributed networks. Patch Manager uses Automation role servers to initiate RPC/WMI connections to remote systems. When you deploy additional Automation role servers, Patch Manager can target more systems simultaneously. Furthermore, when you deploy Automation role servers closer to the remote systems they manage, the RPC/WMI connection has to travel a lesser distance.
Patch Manager uses Automation Server routing rules to manage what tasks go to what Automation role server. Furthermore, Automation Server routing rules define whether or not to assign a task to the default round-robin pool if the assigned server(s) is/are unavailable. In this way, Automation Server routing rules result in one of four general rule definitions:
In any case, you can define specific Worker Process Settings to limit the capacity of each Automation role server. For additional information, see "Automation Server Settings".
To define Automation server routing rules:
The following two scenarios illustrate a use case for additional Automation role servers, and then describe how to create the appropriate Automation server routing rules to address them.