The Management Agent on Windows did not connect to the Management Server
If this is the first installation of the Management Agent, check that there is a valid
icb.datfile in the directory where
ssh-mgmt-sysmonitor.exeis installed. By default, this is
C:\Program Files\SSH Communications Security\SSH Tectia Manager. If there is no
icb.datfile in this directory, obtain a valid ICB file and copy it there. The agent will connect automatically within a couple of minutes. Once the
icb.dathas been used successfully, Management Agent creates a
If you want to connect immediately, restart the Management Agent from the services control panel. Note that you have to have administrator privileges on the host to successfully restart the Management Agent.
If there is an
icb.datfile in the directory, check that it is valid and intact by viewing it in a text editor. You might need to generate and download a new
icb.datfile and follow step 1.
If the connection has been working in the past, but does not work now, try the following. Stop the Management Agent from the services control panel. Delete
icb.dat, if it exists, from this directory. Download a host specific
icb.datfile from the server and start the Management Agent. Using host specific ICB downloaded from the host details view will not create a new entry for the host on the Management Server, instead the existing identity of the host is preserved.
The Management Agent needs to connect to a new server
Stop the Management Agent.
Copy a new
icb.datfile to the location where SSH Tectia Manager is installed.
Wait until the new ICB is automatically loaded, or restart the Management Agent to connect immediately.
The Management Agent recreates manually deleted SSH Tectia Client connection profile desktop shortcuts
The Management Agent service is responsible for creating the desktop icons, and it does so when it notices changes in certain directories or at specific time intervals.
The Management Agent service checks the
%ALLUSERSPROFILE%\Application Data\SSH directory and the
%USERPROFILE%\Application Data\SSH directory of the current user for SSH Tectia Client connection profiles, and reads comment lines in the connection profile itself, checking for flags that indicate whether a desktop icon should be created. If these flags are found, it checks for the appropriate shortcuts, and if they are not found, it creates them. It does the same thing for startup shortcuts.
If you "uninstall" yourself from an SSH Tectia Server and want to delete the SSH Tectia Manager -managed profiles, desktop icons, and so on, do the following:
Delete the profiles from
%ALLUSERSPROFILE%path will normally be either
C:\Documents and Settings\All Usersor
Delete the corresponding profile from your
%USERSPROFILE%path will normally be either
C:\Documents and Settings\<username>or
Delete the corresponding shortcut from your desktop.
Check also Start → Programs → Startup for shortcuts to that profile.
Note on pop-up messages
The Management Agent currently uses the Windows Messenger Service to send pop-up messages to all users logged onto the system. If the Messenger service is stopped, SSH Tectia Manager tries to start it before sending the message. After the message is sent, the service is stopped. If the service had already been running, it is left running. If the service cannot be started, the message is not sent.
To avoid receiving pop-up messages from the Management Agent, set the Messenger service to Disabled via the Control Panel. On Windows NT, this can be done under Start → Settings → Control Panel → Services. On Windows 2000 and XP, this can be done under Start → Settings → Control Panel → Administrative Tools → Services.
The service name is Messenger. To disable the service, double-click it and select Disabled in the Startup Type.
Problems with Management Agent remote deployment on Unix
During Management Agent remote installation, file transfer is done over the terminal connection (
telnet) or by the
scp2 secure file copy application (
If there are problems with the remote agent deployment, try using the selected connection method manually from Management Server to the managed host with the
sshmgmt user account:
mgmt-server$ su -l sshmgmt mgmt-server# rlogin -l remoteuser remotehost
mgmt-server$ su -l sshmgmt mgmt-server# telnet remotehost
mgmt-server$ su -l sshmgmt mgmt-server$ touch tempfile mgmt-server# scp2 tempfile remoteuser@remotehost: <check that the file was transferred correctly> mgmt-server# ssh2 remoteuser@remotehost