To prevent installation failure if Windows NT Domain controller is not present.
Originally Published: 2001-07-09
Last Modified: 2023-10-06
Article Number
Applies To
Microsoft Windows NT 4.0
TechNote 0213
Issue
If you are installing to a computer on a network using a Windows NT Domain Controller, and you attempt to perform an installation when the network is down, the installation may fail if the user is using an account controlled by the NT Domain Controller. This installation failure occurs during the configuration of the Install Directory Server (IDS).
Cause
Resolution
To perform an installation of Sentry CA when the network is down:
1. Run the NT 4.0 User Manager program located at: \winnt\system32\usrmgr.exe
2. Select the menu item: User -> Select Domain
3. Enter the name of the local computer. From this local domain user listing, create an account and profile that has local Administrative access.
4. Log out and log in locally to Windows NT using the new user account.
5. Begin the installation procedure as described in the Sentry CA Administrator's guide.
6. On the second page of the web-based phase of the installation (where the ports and mail server are specified) clear the checkbox with the title: Confirm that SMTP server is reachable.
7. To make this installation available from the normal Network Domain User Account, when the Domain Controller is again available, you must export the Client Administrative Certificate from the browser to a file.
8. When the Domain Controller is available, log in using the normal account and import the Client Administrative Certificate into the browser to gain administrative access to the installation. When Domain Controller network access can be established, the installation is made available to anyone who has access to the Client Administrative Certificate file stored on the hard disk.
Related Articles
Listing multiple Domain Controllers in ipmap_conf.txt Number of Views Access Manager is unable to connect to Active Directory even after expired Domain Controller certificate is replaced Number of Views 'Request could not be handled' error reverting a Role that has been moved to a different Role Set in RSA Identity Governan… Number of Views Troubleshooting tips on testing and configuring NTP for time synchronization on RSA Identity Governance & Lifecycle servers Number of Views Users cannot authenticate with login name in domain\sAMAccountName format using MFA Agent 2.0.1 Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update How to Forward RSA Authentication Manager 8.4 or Later Logs to Multiple Syslog Servers Using rsyslog RSA Authentication Manager 8.9 Patches and Hotfixes Readme
Don't see what you're looking for?
