Synchronize Agent Authentication Records on the Primary Instance
You can configure the number of agents that can be queued for auto-registration. Consider using this feature to increase the queue size if you need to auto-register a large number of agents (more than 1000) simultaneously.
The RSA Authentication Manager primary instance checks log records at regular intervals for new authentication records and information on the authentication agents that are installed in your deployment. You can use these collected records to run the List All Installed Agents report. Authentication Manager looks for timestamps that are later than the last time that it checked the log files, unless you define an offset value to collect earlier records that were delayed by replication. By default, the offset value is 0 hours.
For example, suppose that a replica instance authenticates a user at 10:59 AM. The primary instance checks the log files for authentication records at 11:00 AM, and the replica instance sends data to the primary instance at 11:10 AM. When the primary instance checks the log files again, at 11:00 PM, it looks for authentication records with a timestamp that is 11:00 AM or later. If you set the offset value to 1 hour, then the primary instance looks for records with timestamps that are later than 10:00 AM, and it collects the replicated authentication record from 10:59 AM.
Before you begin
You must be an Operations Console administrator.
Obtain the rsaadmin operating system password for the primary instance.