Prevent or specify the auto-registration utility for selected subnets in RSA authentication agent 7.4 for Microsoft windows
Originally Published: 2019-04-16
Article Number
Applies To
RSA Version/Condition: 8.x
Issue
Resolution
- On the Authentication Agent client computer, log on with an Administrator account.
- Open the Registry Editor. Click Start. Then enter regedit in the start Search prompt and click regedit from the Programs list.
- In the Registry Editor, click HKLM\ SOFTWARE\RSA\RSA Authentication Agent\AgentAutoRegistration.
- Right-click on an empty screen in the right-pane and select New > String Value.
- For the new value name, enter ExcludeNetworkMasks.
- In the right pane of the Registry Editor window, right-click ExcludeNetworkMasks, and click Modify.
- For the value name, enter a semicolon separated list of subnets in CIDR format.
Example: 192.168.3.0/24
To configure the Auto-Registration utility to use a subnet:
- In the Registry Editor, click HKLM\ SOFTWARE\RSA\RSA Authentication Agent\AgentAutoRegistration.
- In the right pane of the Registry Editor window, right-click, and then click New > String Value.
- For the new value name, enter IncludeNetworkMasks.
- In the right pane of the Registry Editor window, right-click IncludeNetworkMasks, and click Modify.
- For the value name, enter a semicolon separated list of subnets in CIDR format
Example: 192.168.2.0/24
Related Articles
Change the Auto-Registration Queue Size 18Number of Views Automatic Agent Registration 136Number of Views Device Registration Using Password Policy 291Number of Views Authenticator Registration 245Number of Views Cloud Administration Retrieve Device Registration Code API 297Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?