-
Title
RUM stops processing computers and status remains at "Pending" -
Description
The RUM console may stop processing computers, and the computer status may stay at pending indefinitely.
-
Cause
This may occur if you have multiple replicating ADAM instances. In particular if you have two ADAM instances that are replicating with each other, and a separate RUM console connects to each instance, there is a possibility that Domain information can be duplicated in ADAM. This occurs if you enter credentials under Manage Agent Credentials at the same time on both consoles. If credentials are entered for the same domain on each console in between ADAM replication cycles, this domains information will exist twice in the ADAM database, which causes the RUM console to fail.
If you intend to use multiple RUM consoles (and associated ADAM replicas), ensure that the configuration of Controller and Agent Service credentials is handled on the first console and that sufficient time is allowed for ADAM to replicate PRIOR to installation of the additional RUM consoles.
Here is the example of process to be followed:1.Enter the RUM Controller Service and domain-specific Agent Service credential(s) on your first RUM console2.Wait some time for ADAM to replicate (Please see Microsoft documentation on the topic of ADAM / LDS replication and its management)3.Setup the additional console(s) the required credentials will be automatically present on launch. -
Resolution
To repair this issue:
-Close all but one RUM console.
-Open Manage Agent Credentials and remove all entries from the list.
-Wait for ADAM replication to complete, and then open the other RUM consoles and check each ADAM instance to be sure these deletions have replicated.
-Close all but one RUM console again.
-In the open RUM console, open Manage Agent Credentials again and enter in credentials for all domains involved in resource updating.
-To prevent the issue from recurring, make sure to designate a single console for using the Manage Agent Credentials section.