1. When policy is updated immediately, the message of "0 case in 1 case has finished normally" is displayed.
Error message
"[MGCM-INF002]Immediate update has finished. (%d cases in %d cases has finished normally).
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
It is likely that the power supply of the client (CT) is not connected or it is not connected to the network.
[Resolution]
Connect the power supply of the client (CT). Or connect to the network.
Cause 2
It is likely that the communication port of the client (CT) or the port used for name analysis (V12 version) is not opened.
137 - 138 (BE V12.0L10, BE V12.0L20, SE V12.0L20)
10010 (initial value at installation)
[Confirmation Points]
Confirm if the above port has been opened when the following command is executed on the Management Server. telnet [IP Address of CT] port number
If it is unable to connect, an error will be disabled.
If it is able to connect, words on the window will disappear, and only the flashing cursor will be displayed.
[Resolution]
Open the following ports in the setting of firewall.
137 - 138 (BE V12.0L10, BE V12.0L20, SE V12.0L20)
10010 (initial value at installation)
Cause 3
It is likely that name analysis of the client (CT) has not been performed.
(However, name analysis is not required in V13.0.0 or later.)
[Resolution]
Record IP address and host name to the hosts and Imhosts of the client (CT).
Confirm if reverse analysis on DNS server has been set on client (CT).
Cause 4
It is likely to be operated under NAT environment.
[Resolution]
Systemwalker Desktop Keeper does not support target the operation in NAT environment.
Cause 5
It is likely that the IP address of Management Server connected by client (CT) is incorrect.
[Confirmation Points]
Execute the following command through the command prompt of the client (CT) that requires modification of IP address of the connected (Master) Management Server, and confirm the IP address of the (Master) Management Server is correct.
fsw11ej7.exe <Password> /D /D
[Resolution]
Correctly set the IP address of the Management Server connected to the target client according to the following procedure.
Execute the following command through the command prompt of the client (CT) that requires modification of the IP address of the connected (Master) Management Server.
fsw11ej7.exe <Password> /C /I <IP Address of Modified (Master) Management Server >
Execute the following command through the command prompt of the client (CT), so that CT information will be notified to (Master) Management Server that is connected with the client (CT).
fsw11ej7.exe <Password> /R
Restart the client (CT).
2. The priority of user policy and CT policy is unknown.
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
For the repeated items in user policy and CT policy, user policy is in priority and effective.
However, when item only exists in CT policy, the CT policy is effective.
In addition, in the versions after V13.2.0, the user policy that has already been registered can be set to invalid, and CT policy is set as in priority.
[Resolution]
None
3. The user policy has been set to the Master Management Server, so it cannot be applied to the client (CT) under each 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
The user policy set in Master Management Server is only effective to the client (CT) under the root directory of Master Management Server.
When applying policy to the client (CT) under each Management Server, user policy should be set on each Management Server.
However, in V13.2.0 or later, collective unified management of user policy will be performed.
[Resolution 1]
Set user policy for each Management Server.
[Resolution 2]
In V13.2.0 or later, unified management can be outperformed for user policy on Master Management Server. To modify settings, refer to "Perform System Settings" in the "Systemwalker Desktop Keeper Installation Guidance" to set the [User Information Management] to "Collective Management in Master Management Server (Recommended)".
4. Logon prohibition is cancelled on the client (CT) with logon prohibition and "Update at Next Startup" is set, but it is still logon prohibited after restart.
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
After restarting the OS of the client (CT), the service of Systemwalker Desktop Keeper will be started. It will take some time for client (CT) to receive policy from the Management Server.
During logon, before the policy receiving has completed, the pervious terminal policy will still be effective, so it will be logon prohibited.
[Resolution]
After OS is restarted, it will take several minutes for client (CT) to receive policy from the Management Server. Log on again after this time.
Or, restart twice.
5. Client (CT) has been started but policy is not reflected.
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
Service of Management Server may have been stopped.
[Resolution]
Start the service of Management Server.
Start [Server Settings Tool] and select [Start Service] from the [Service] menu.
Cause 2
It is likely that the communication port of the client (CT) or the following ports used for name analysis is not opened.
137 - 139
445
10010 (initial value at installation)
[Resolution]
Execute the following command on the Management Server to confirm if the above port has been opened.
telnet [IP Address of Management Server Connected] Port number
If it is unable to connect, 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]
Open the following ports in the setting window of firewall (including personal firewall).
137 -139
445
10010 (initial value at installation)
Cause 3
In the Installer of Systemwalker Desktop Keeper, only the port used for profile that has logged in will be opened. Therefore, when another profile is used to login after installation, the port used by Systemwalker Desktop Keeper will be closed. Communication from the Management Server to the client will not be performed, and policy cannot be reflected.
Cause 4
In versions earlier than SE V12.0L20, it is likely that no name analysis has been performed for the Management Server (Master Management Server) and client (CT).
In Systemwalker Desktop Keeper, during the reflection of policy, the following communications should be used to perform name analysis (analyze computer name from IP address (reverse analysis)).
Communication between Master Management Server and Management Server.
Communication between Management Server and client (CT)
Communication between Master Management Server and client (CT)
[Resolution]
Record IP address and host name to the hosts and Imhosts of Management Server and client (CT).
Confirm if reverse analysis on DNS server has been set on the Management Server and client (CT).
Cause 5
It is likely that the operation is performed in NAT environment (the environment under which communication from the Management Server to the client (CT) cannot be performed).
[Resolution]
Systemwalker Desktop Keeper does not support target the operation on NAT environment.
Cause 6
It is likely that the IP address of the Management Server connected with the client (CT) is incorrect.
[Resolution]
Set a correct IP address of Management Server connected to the target client (CT).
For detailed procedure, refer to "Modify the Connected Management Server/Master Management Server" in Systemwalker Desktop Keeper User's Guide for Administrator.
Cause 7
In CT policy and user policy, the user policy is applied in priority. Therefore, it is likely that CT policy has not been reflected.
[Confirmation Points]
Confirm if user policy has been set on client (CT).
[Resolution]
If it is the user policy that is reflected, perform the following operations.
Delete this user.
Set user policy to invalid for V13.2.0 or later.
Set the same content for user policy and CT policy.
Modify the user that logs on to the client (CT).
Cause 8
In BE V12.0L10 version, PG38786 may occur.
[Resolution]
Apply the content of emergency correction of BE V12.0L10 (after TP07761).
Cause 9
Group policy might have been applied. CT policy and user policy have their own group policy respectively. Therefore, the policy intended to be applied is not reflected.
[Resolution]
In V13.2.0-V14.2.0, start Management Console and confirm the policies applied to this client (CT) and the user.
When the [Applied Policy] of the client (CT) or user is [Group], the group policy will be applied in priority.
When group policy is being applied, confirm the intended policy.
6. Terminal operation settings has not been applied.
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
When performing [Terminal Operation Settings], the settings of the client (CT) after policy has been applied will only be effective after restarting.
[Resolution]
When it is set to update immediately, restart the client (CT) after policy has been applied.
When it is set to apply at next startup, restart the client (CT) twice.
