1. After image copy distribution has been performed in the environment with CT installed, client (CT) will not be registered.
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 copying the environment that has been installed, the only identification ID set in every PC through Systemwalker Desktop Keeper will be copied. Therefore, it will be recognized as the same client (CT) on the Management Server.
[Resolution]
Resolution after occurrence of phenomenon.
Execute the following command for re-registration after deleting the main client (CT) on the Management Console.
fsw11ej7 [Password] /R
[Password]: Enter the password specified during installation of CT.
Countermeasures for preventing the phenomenon.
Take out the LAN Cable before installing CT, and the copying image.
2. When installing CT, in the terminals within the same network segment, some entries to server can be performed and some cannot.
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
An error may exist in the setting of "NetBIOS over TCP/IP" defined by Internet properties.
[Resolution]
Modify the setting of "NetBIOS over TCP/IP" defined by Internet properties to "Enable NetBIOS over TCP/IP".
3. During silent installation of CT, an error of "Stop uninstallation" is output.
Error message
"[I402-ERR105] The parameter format specified in the command line is incorrect. Record in the correct format. The uninstallation is cancelled."
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
Error exists in the parameters set during silent installation.
Under the environment that Systemwalker Desktop Keeper has been installed, it will be judged whether to install with overwriting or uninstall when Installer is started. However, according to specified parameters, an error will be indicated when the system cannot judge whether to install with overwriting or uninstall.
[Resolution]
Set the parameters of overwriting installation and execute again.
[Version V13.0.0 or later]
D:\win32\DTKClient\Setup.exe /Silent "C:\Dtk\InstConf.ini"
[Version V12.0L20 or earlier]
D:\win32\DTKClient\Setup.exe /z"Reboot:<Parameter 1>,PrinterMode:< Parameter 2>"
< Parameter 1>:
Specify to restart after installation.
"0": when not to restart;
"1": when displaying dialog
"2": when restarting by force.
< Parameter 2>:
Printing auditing mode.
"0": input when collecting the printing operation logs of every CT.
Printing operation logs will be collected from every CT."1": Same as the printer server, input when the printing operation configured on CT under Master Management Server or Management Server is implemented by printer server. CT should also be installed to the printer server. When printing is not performed through the CT of the printer server, printing operation logs will not be collected.
Printing operation logs are collected from the printer server.
4. CT installation fails and error message is output. (1)
Error message
"[I401-ERR106] The previous installation/uninstallation is not completed. Reinstall after restarting. The installation is cancelled."
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 following may be the causes of installation failure.
Generally, when it is expected to update the file being used at the startup of Windows, after Windows has been restarted, set the following values in the registry to replace the file.
[Key]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
[Value Name]
PendingFileRenameOperations
When some value is set in the registry, it will be judged as the file that has not been updated exists. The installer of Systemwalker Desktop Keeper will stop processing, and the message indicating the restart of Windows will be displayed. Usually, the content in the registry will disappear due to the restart of Windows, but sometimes it may remain after the restart of Windows if the modified file name or the deletion operation is remained.
http://support.microsoft.com/default.aspx?scid=kb;en-us;310335
[Resolution 1]
Install CT after restarting Windows.
If the same error occurs after restarting, execution [Resolution 2].
[Resolution 2]
This problem can be avoided by temporarily modifying the name of PendingFileRenameOperations.
Install Systemwalker Desktop Keeper and restore the registry after restarting.
5. CT installation fails and error message is output. (2)
Error message
"Error occurred in execution of setup (-5003: 0x5)"
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
Error occurs because the initialization of Install Shield engine fails.
[Resolution]
Process according to the following order.
Rename the following underlined parts to any folder name.
C:\Program Files\Common Files\InstallShield\Engine
C:\Program Files\Common Files\InstallShield\professional\Runtime
Install CT. Sometimes uninstallation is required according to the previous installation status. Then, uninstall first before installing again.
6. CT installation fails and error message is output. (4)
Error message
"C:\WINNT\system32\swgstring.dll class is not registered."
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
Phenomenon occurs when the required DLL file is not registered in Windows.
In order to enable swgstring.dll to run, the atl.dll file should be set to be usable in Windows (called as COM registration). Usually, COM registration has been implemented for atl.dll on Windows, but such phenomenon will occur when registration disappears.
[Resolution]
Execute the following command and implement COM registration of atl.dll, then perform installation.
regsvr32 C:\WINNT\system32\atl.dll
7. After VPN software has been installed, it will not be able to connect to network when installing Desktop Keeper.
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
Conflict occurs between VPN (Virtual Private Network) software and the drive of Systemwalker Desktop Keeper, so it is unable to connect to the network.
Now, confirm that it is the following software that cannot be connected to network.
Netscreen Remote
Cisco VPN Adapter
Nortel VPN Client
[Resolution]
If the software mentioned above has been installed, it cannot co-exist with Systemwalker Desktop Keeper.
However, if Netscreen Remote has been installed, when Virtual Adapter function is not used, it can co-exist after uninstalling Virtual Adapter.
8. After CT has been installed on the PC with Symantec AntiVirus Corporate Edition installed, blue screen will occur and OS window will be frozen.
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 |
Error message
"STOP error STOP 0x0000007f (0x00000008, 0x00000000, 0x00000000, 0x00000000) UNEXPECTED_KERNEL_MODE_TRAP"
Cause
In Symantec AntiVirus Corporate Edition, the function that enables Auto-Protect exists before starting the service of Symantec (it is the situation in which the startup option of Auto-Protect is set to [At System Startup]. Therefore, the load of driver of Systemwalker Desktop Keeper is blocked.
[Resolution]
After the service of Symantec has started, modify the setting to enable Auto-Protect.
In Symantec AntiVirus Corporate Edition, the startup option of Auto-Protect is set to [At Startup of Symantec Anti Virus].
For information on how to set, refer to the Manual of Symantec AntiVirus Corporate Edition.
9. After Systemwalker Desktop Keeper has been installed, blue screen will occur (STOP CODE: 0x35).
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 existence of known defects has been proved in Windows XP SP2 or later as well as Windows 2003 Server SP1 (including Windows 2003 Server R2) or later.
http://support.microsoft.com/kb/906866/en-us/
Because the Mup.sys that has distributed file system does not take situation with over four filter drive into consideration, it lead to insufficient IRP memory when the four filter drives are imported.
[Resolution]
After downloading modification module from the above URL, the registry will be updated and the available IRP Stack Capacity of the Mup.sys file will be increased. The above URL also records how to edit the registry.
10. When upgrading from XP to Vista, it will be impossible to connect the network. Afterwards, LAN card will not be recognized after uninstalling CT.
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 reason is the upgrading OS to Windows Vista(R) or Windows(R) 7 after CT has been installed on WindowsXP.
[Resolution]
Install the CT again after restore the PC to clean status by restoration DISK .etc,