Alternative to running RSA ACE/Server 5.1 patch installer for installation issues on hardened systems
Originally Published: 2003-09-18
Last Modified: 2023-09-25
Article Number
Applies To
Microsoft Windows 2000
System hardened using Templates
Issue
Procedure for manually patching RSA ACE/Server 5.1
Resolution
In brief, you would run the patch install against an ACE/Server installation on a test-bed that has not been hardened. Then copy the installation files to the production system.
There are some Windows Registry settings which are updated with the Patch, which will need to be updated manually.
Make sure the pathing to /ace is the same on both systems, as scripts have the path assigned to them during the installation. The test-bed does not need to have the same hostname or IP Address as the production system.
INSTRUCTIONS:
1. Patch the test-bed system
2. Preserve the /ace/data directory from the production system. You can do this simply by stopping the ACE/Server and renaming /ace directory (Preserving the entire installation directory structure).
3. Copy the entire installation from the test-bed to the production system into the same path so your new /ace is where your old /ace used to be. Do not overwrite the original files, you may wish to roll back if you encounter any issues, and you will need the contents of the /data directory whether you roll back or not.
4. Copy the Production /ace/data directory which you preserved and it's entire contents to the new /ace/data directory (replacing only the files in /ace/data)
5. Rename the /WINNT/system32/sdsrvmsg.dll file on the production server
6. Copy the sdsrvmsg.dll file from the /WINNT/system32 directory of the test-bed to the same directory on the production server
7. Using a Registry Editor such as Regedit, go to the following:
HKEY_LOCAL_MACHINE > SOFTWARE > SDTI > ACESERVER > CurrentVersion >
8. Change the following keys to these values:
Version = 5.1.1
Revision = 35
Patch = 1
9. Restart the Production server
Related Articles
Security Best Practices for RSA Authentication Manager Self-Service Console Number of Views Best Practices for backup and restoration of FIM configuration and secrets files Number of Views Best practices for installing, configuring and using the RSA MFA Agent 9.x for PAM/Unix Number of Views Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Number of Views RSA MFA Agent for Windows will not run due to error "This module is blocked from loading into the Local Security Authority" Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Unable to login to RSA Authentication Manager Security Console as super admin RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory
Don't see what you're looking for?
