|Applies To||Microsoft Windows 98|
Microsoft Windows 95
Microsoft Windows NT 4.0
Microsoft Windows 2000
UNIX (AIX, HP-UX, Solaris)
|Issue||After installation of Remote Administration there is no ACE/Server listed to choose from when starting Remote administration.|
|Cause||Corrupted sdconf.rec file. If ftp is used to transfer the sdconf.rec file it must be done in binary mode (bin) to avoid corrupting the file.|
|Resolution||Make new copies of sdconf.rec and server.cer from the ACE/Server's ACEDATA directory and use them to reinstall Remote Administration.|
Note: It may be possible to bypass reinstallation of Remote Administration by creating a directory named for the Primary or Master server and copying the sdconf.rec and server.cer to that directory. For this procedure, see: Remote Administration does not have server name to administer
1. Uninstall Remote Administration
2. On the ACE/Server master Server, copy C:\ace\data\sdconf.rec and server.cer to a diskette.
3. Insert the ACE/Server installation media and run <drive>:\aceserv\nt_i386\setup.exe.
4. When prompted for license files, point to the diskette or directory containing the master sdconf.rec and server.cer files.
5. Select Remote Administration Software as the component to be installed.
6. Change the installation top-level directory to the intended mapped network drive.
7. Create an entry in the local machine host file (see format below), for
Windows NT->\winnt\system32\drivers\etc\, for Windows 95/98->\windows\
"10.X.X.X <ACE/Server hostname> # Comment"
8. Ensure that sdadmind services is running on the ACE/Server and that the user has administrative privileges.
9. Optional: create a shortcut on the desktop: <mapped drive>\ace\prog\sdadmlch.exe remote.
If the above instructions do not get your Remote Administration working, see also: Troubleshooting ACE/Server and RSA Authentication Manager Remote Administration - A Handy Guide
|Legacy Article ID||a3732|