Why is the GPG standalone 2.0 collector not forwarding events to the Group Policy Guadian Server fol (NETIQKB47618)

  • 7747618
  • 02-Feb-2007
  • 15-Mar-2013

Environment

NetIQ Group Policy Guardian 2.0

Resolution

goal
Why is the GPG standalone 2.0 collector not forwarding events to the Group Policy Guadian Server following upgrade?

goal
How do I upgrade to GPG standalone 2.0 collector without generating errors following the upgrade?

goal
How do I ensure the GPG standalone 2.0 collector queue ID is correct?

fact
NetIQ Group Policy Guardian 2.0

symptom
Uninstalling the GPG 1.6 stand-alone Collector and then performing a clean install of the GPG standalone 2.0 collector causes GPO changes to not be detected.

symptom
Uninstalling the GPG 1.6 stand-alone Collector and then performing a clean install of the GPG standalone 2.0 collector causes events to not be forwarded to the Group Policy Guadian Server.

cause
The collector queue ID on the stand-alone collector does not match the newly assigned collector ID that is registered on the GPG server. 

fix

If you uninstall the old version 1.6 collector and install a new version 2.0 collector without removing the collector from the GPG console, the standalone console retains its collector ID.  If you upgrade GPG 1.6 directly to GPG 2.0, there is no issue.

When you install a version 2.0 stand-alone collector and rescan and then assign it to domain controllers, the server assigns a new collector ID to this collector, from the perspective of the GPG server.  However from the point of view of the standalone collector, the collector still has the old ID.  This difference causes update messages to be sent with the old collector ID to the GPG server. The GPG server drops the messages, since the ID does not match.

However, if you uninstalled the GPG 1.6 standalone collector and then performed a clean install of the GPG 2.0 collector the message-dropping problem occurs.

To resolve the dropped message issue, perform the following procedure:

  1. Open the NetIQ Group Policy Guardian (GPG) Console, and then expand Enterprise Configuration > Collectors.

  2. Right-click the GPG 1.6 standalone collector and select Remove Collector. This removes the standalone collect from the list.

  3. On the standalone collector computer, click Start >Control Panel> Administrative Tools, and then click the Computer Management console.

  4. Expand Services and Applications> Message Queuing> Private Queues.

  5. Expand each of the following nodes: fagpgcollectorconfig_xq, fagpgcollectorconfigbad_xq, and fagpgreq.

  6. For each node specified in the previous Step, right-click Queue messages, select All Tasks, and select Purge.

  7. Note: When clearing the faggprreq queue, you may receive a message: "The queue cannot be purged. Error: Access is denied." Right-click the faggprreq node and select Properties. Click the Security tab and add your logged-on user account to the security ACL.

  8. In the GPG (NetIQ Group Policy Guardian) Console, expand the Enterprise Configuration node.

  9. Right-click the Collectors node and select Scan.

  10. Ensure the new 2.0 standalone collector is added to the list.

  11. In the GPG Console, assign a DC to the stand alone collector by expanding the Domains > Domain_name> Configuration node.

  12. Select the Domain Controllers node.

  13. Right-click a domain controller and select Enable Event Monitoring for This DC.

  14. Select the stand alone collector and click OK.

  15. Wait at least five minutes for the collector configuration to be updated.



Additional Information

Formerly known as NETIQKB47618

Feedback service temporarily unavailable. For content questions or problems, please contact Support.