Table of Contents
Advertisement
322
Troubleshooting installation and communication problems
Troubleshooting communication problems between the management server and the console or the database
Troubleshooting communication problems between
the management server and the console or the
database
Restores the communication breakages to the client that cannot be corrected
on the management server.
Converts an unmanaged client to a managed client.
Converts a managed client to an unmanaged client.
You can use write a script with the tool to modify communication settings for
large numbers of clients.
See
About managed and unmanaged clients"
See
Troubleshooting communication problems between the management server
and the client"
on page 316.
To recover client communication settings by using the SylinkDrop tool
1
In the console, export the communication file from the group that connects
to the management server to which you want the client computer to connect.
See
Converting an unmanaged client to a managed client"
2
Deploy the communication file to the client computer.
3
On the product disc, locate the \Tools\NoSupport\SylinkDrop folder, and
open SylinkDrop.exe.
You can run the tool remotely or save it and then run it on the client computer.
If you use the tool on the command line, read the SylinkDrop.txt file for a list
of the tool's command parameters.
4
In the Sylink Drop dialog box, click Browse, and locate the .xml file you
deployed in step
2
5
Click Update Sylink.
6
If you see a confirmation dialog box, click OK.
7
In the Sylink Drop dialog box, click Exit.
If you have a connection problem with the console or the database, you may see
one of the following symptoms:
The management server service (semsrv) stops.
The management server service does not stay in a started state.
to the client computer.
on page 81.
on page 115.
Advertisement
Table of Contents
Troubleshooting
