Submit a ticketCall us

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.

 

 

 

 

Home > Success Center > Patch Manager > Automation Server fails to perform work even with correct rules

Automation Server fails to perform work even with correct rules

Table of contents
Created by Geoffrey Layton, last modified by MindTouch on Jun 23, 2016

Views: 657 Votes: 0 Revisions: 5

Overview

This article describes the issue when the Automation Server fails to perform work even though the rules are set correctly. 

Environment

Patch Manager version 1.85

Steps

Create outing rules for the subnets:
  1. Go to Patch Manager System Configuration > Management Groups > select your Managed Enterprise.
  2. Select Automation Server Routing Rules.
  3. In the Actions Pane, select Add Subnet Routing Rule.
  4. Type in the info on each subnet or see step 5.
  5. If you have many subnets to add, you can browse your AD by clicking Browse and your subnets is displayed for you to select when you click on your AD, and selecting the site on the right.
  6. Double-click the Subnets to add them to them to the bottom half of the right pane.
  7. Click OK.
  8. Once your subnets have been added, click OK until you get to the Set Automation Server for routing rule and rule type.
  9. Put a check in the box for the corresponding Automation Server and in Absolute Rule.
  10. Click OK.

 

If the above steps do not work, try removing the AS and reinstalling it:

  1. Uninstall Patch Manager on the Automation Server.
  2. Delete the Eminent ware registry key: Hkey_Local_Machine/Software/EminentWare
  3. Delete any remaning patch manager files in program files.
  4. Run SQL Management Studio and clear record for PAS from dbo.gc_device and dbo.device (do it for both DB: Primary and Automation).

 

Last modified
00:59, 23 Jun 2016

Tags

Classifications

Public