Using PowerShell to Update Registry Keys for the MFA Agent for Microsoft Windows
Originally Published: 2024-05-30
Article Number
Applies To
Version(s): 2.x
Issue
If Group Policy Objects are locally applied on the machine rather than being pushed from the Domain Controller, PowerShell commands offer a method to update the agent's GPOs.
Resolution
- Log in to the Windows Core server.
- Open Powershell by pressing 'Win + X', then select "Windows PowerShell".
- Run the below PowerShell command to update the Reserve Password value:
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\RSA\RSA Desktop\Local Authentication Settings" -Name "ReservePasswordHashedValue" -Value "<enter the Reserve Password Value>"
- After running the command, you can verify if the registry key was updated successfully:
Get-ItemProperty -Path "HKLM:\SOFTWARE\Policies\RSA\RSA Desktop\Local Authentication Settings" -Name "ReservePasswordHashedValue"
Here's a demonstration of how to update the Reserve Password value and confirm the change using the provided PowerShell commands:
Notes
For example:
Set-ItemProperty -Path "<RegistryPath>" -Name "<KeyName>" -Value "<NewValue>"
Related Articles
Capture the reserve password from the current RSA ACE/Agent 5.6 for Windows installation is grayed out 62Number of Views How to make reserved user attributes RSA Access Manager User Properties 62Number of Views Agent C API 8.x: How to enable debug/trace logging for 32-bit API running on 64-bit Windows OS 83Number of Views Installation hangs at 'Configuring System Settings' and the installation log has an 'ORA-01017: invalid username/password;… 226Number of Views Increase the maximum length of a reserve password hash for the RSA Authentication Agent 7.x for Windows 214Number 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?