To prevent installation failure if Windows NT Domain controller is not present.
Originally Published: 2001-07-09
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
DNS External Service Interaction in RSA Authentication Manager 8.x - False Positive 68Number of Views RSA SecurID Authenticator 4.1 for iOS and Android Quick Start Guide (Italian) 8Number of Views Inconsistent or failed DNS name resolution by RSA SecurID Access Identity Router 118Number of Views SAML 2.0 Requirements for Service Providers - AuthnRequest 48Number of Views Identity Router DNS Requirements 262Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?