1. The client (CT) that has been installed cannot be displayed on the Management Console and Log Viewer.
Target Version/Edition
BE V12.0L10 | BE V12.0L20 | BE V13.0.0 | BE V13.2.0 | BE V13.3.0 | V14.0.0/V14.0.1 | |
SE V12.0L20 | SE V13.0.0 | SE V13.2.0 | SE V13.2.1 | SE V13.3.0 | V14.1.0 | |
V14.2.0 |
Cause 1
Perform image copy for the PC that has been registered on the Management Server, and take image as master to construct the client (CT). Even if the PC has been registered once in Systemwalker Desktop Keeper Management Server as master and the image copy is distributed, Management Server will consider it as the same client (CT), so the client (CT) cannot be registered.
[Resolution]
After deleting the client (CT) as master from the Management Console, execute the re-registration command in the PC.
fsw11ej7 [Password] /R
[Password]: Enter the password specified at installation of CT.
Remove the LAN cable, install CT, and copy the image.
Cause 2
Use the authority of department administrator to confirm the cause of the client (CT) under the root directory.
Department administrator can only confirm the clients in the group that has department administrator authority. Right after the registration of the client (CT), the client (CT) will be configured into the root directory. Department administrator cannot confirm the client (CT) under root directory, so the client (CT) that is newly registered cannot be confirmed.
[Resolution]
System administrator is required to login to the Management Console and move the client (CT) to the group of department administrator authority.
Afterwards, login to the Management Console as a department administrator.
Cause 3
The confirmation location on the Management Console may be incorrect. Confirm on the Management Console again according to the following description.
New registration:
Client (CT) is registered to the root directory.
Re-registration:
Register as follows according to the version of Management Server of Systemwalker Desktop Keeper.
V12.0L10:
It is registered to the root directory.
Version of V12.0L20 and later:
It is displayed in the group registered before re-registration.
Version V13.2.0 and later, and linked with Active Directory:
It is displayed in the root directory of the local group.
[Confirmation Points]
Confirm the location recorded in Cause 3.
* Search can be performed through the search function on the Management Console of Systemwalker Desktop Keeper V12.0L20 or later.
[Resolution]
No resolution is required.
Cause 4
IP address connected during installation of CT may contain mistakes.
[Confirmation Points]
Execute the following command through command prompt, and confirm the IP address of the target to be connected.
fsw11ej7 [Password] /D /D
[Password]: enter the Password specified at the installation of CT
IP address of Master Management Server or Management Server connected to the client (CT) will be displayed.
[Resolution]
Correctly enter the IP address of (Master) Management Server connected.
For detailed procedure, refer to "Modify the Settings of Management Server/Master Management Server Connected" in Systemwalker Desktop Keeper User's Guide for Administrator.
Cause 6
It is also likely that the firewall of Management Server has closed the communication port used by Systemwalker Desktop Keeper, so it is unable to connect with Management Server.
[Confirmation Points]
Execute the following command on the client (CT), and confirm if communication between client (CT) and Management Server can be performed through the port (initial value 10010) set at installation of CT.
telnet [IP Address of Management Server Connected] 10010
If it is unable to connect, an error will be displayed.
If it is able to connect, the words on the window will disappear, and only the flashing cursor is displayed.
[Resolution]
When it is confirmed that connection is impossible through the above procedure, open the firewall port of the Management Server side.
Cause 7
It is also possible that name cannot be analyzed between the Management Server and the client (CT), so Management Server cannot be connected.
[Resolution]
Use DNS server to perform reverse analysis, or use hosts file to perform name analysis.
(However, name analysis is not required in versions after V13.0.0).
2. The same client (CT) has been registered multiple times on the Management Console.
Target Version/Edition
BE V12.0L10 | BE V12.0L20 | BE V13.0.0 | BE V13.2.0 | BE V13.3.0 | V14.0.0/V14.0.1 | |
SE V12.0L20 | SE V13.0.0 | SE V13.2.0 | SE V13.2.1 | SE V13.3.0 | V14.1.0 | |
V14.2.0 |
Cause 1
Installation and uninstallation are performed repeatedly. The same client (CT) has been registered repeatedly. (Only exists in V12.0L10 version.)
[Resolution]
Process according to the following steps.
Use backup command to backup the log information of the old client (CT).
Delete old client (CT) on the Management Console.
Install client (CT) again.
Cause 2
The re-registration command is executed on client (CT), registration is performed repeatedly. (Only in V12.0L10)
fsw11ej7 [Password] /R
[Password]: enter the Password specified at installation of CT.
[Resolution]
Use backup command to backup the log information of the old client (CT).
Delete the old client (CT) on the Management Console.
Install the client (CT) again.
Cause 3
When port is closed due to the reason such as firewall of the client (CT) is opened, even "the client (CT) -> Management Server" can communicate, "Management Server -> client (CT)" cannot be connected. Therefore, when client (CT) is started, although it is registered to the Management Server, the registration information sent from the Management Server is not received. Therefore, every time when the client (CT) is started, it will be registered to the Management Server. Therefore, client (CT) is registered repeatedly.
[Confirmation Points]
Execute the following command on the client (CT), and confirm if communication between client (CT) and Management Server can be performed through the port (initial value 10010) set at installation of CT.
telnet [IP Address of Management Server Connected] 10010
If it is unable to connect, an error will be displayed.
If it is able to connect, words on the window will disappear, and only the flashing cursor will be displayed.
[Resolution]
Close the firewall of the client (CT) or open the port used by Systemwalker Desktop Keeper.
Cause 4
Due to reasons such as the client machine is replaced, under the status that one item in the following "judgment conditions for same CT at CT registration" is inconsistent; the registration command (fsw11ej7.exe [Password]/R) is executed again.
Judgment conditions for same CT at CT registration
- Machine name
- MAC address
- OS
- Owner's name
[Confirmation Points]
In the above judgment conditions for same CT at CT registration, it can be judged as the same CT when all the conditions are matched.
The others will be considered as different CT and will be registered again.
From V13.3, administrator can set such judgment condition as one item in it.
[Resolution]
Modify the setting through the Server Settings Tool so that the client (CT) registered at this time will be judged as the same client (CT) of last registration.
After that, execute the re-registration command.
Modification methods of Server Settings Tool are as follows.
Start the Server Settings Tool. In the [Judgment Conditions for Same CT at CT Registration] of the [System Settings] window, select [Do not Use] for the item that has different conditions between last time and this time.
3. After modifying the group on the Management Server and restarting the service, the modified information is not reflected to the Master Management Server.
Target Version/Edition
BE V12.0L10 | BE V12.0L20 | BE V13.0.0 | BE V13.2.0 | BE V13.3.0 | V14.0.0/V14.0.1 | |
SE V12.0L20 | SE V13.0.0 | SE V13.2.0 | SE V13.2.1 | SE V13.3.0 | V14.1.0 | |
V14.2.0 |
Cause
In the version earlier than V13.0, configuration information will not be sent to the Master Management Server when the service is started. Therefore, the information will not be reflected when the service is restarted.
(In V13.2 or later, configuration information will be sent to the Master Management Server when the service is started. so information will be reflected.)
[Resolution]
When the latest information under the Management Server is reflected to the Master Management Server, select [Refresh] from the [Tree Settings] menu in the Management Console of Master Management Server.
