This describes how to upgrade the version based on the version upgrade by using self version management function as Systemwalker Desktop Keeper function.
Note
Notes before using Self Version Management Function
The correspondent PC should be logged onto when operating the self version management function. If not, it cannot operate.
In the case of operating version upgrade through self version management, after enabling the Windows firewall function, the window for confirming version upgrade cannot be displayed in the Client. After disabling the Windows firewall function on the Client terminal temporarily and rebooting OS, the window for confirming version upgrade will be displayed. Enable the Windows firewall function after completing version upgrade.
Through the self version management function, the initial value of the number of terminals that can be applied simultaneously is 5. When modify this number of terminals, modify it in Simultaneous Downloading Number (Maximum) in the "Folder/CT Version auto-upgrade Settings" window of server settings tool. The terminal that exceeded this configuration value will execute the self version management function again when starting up next time.
When using the self version management function in the environment of Windows Vista(R), Windows(R) 7, Windows(R) 8 and Windows(R) 10, do not use the remote logon through Windows terminal service such as Windows "Remote Desktop Connection".
Assume that you are using Windows(R) 8 and Windows(R) 10 the fast startup feature is enabled, and you shut down before you have logged on. In this case, the transfer target information file and CT operation parameter information file update operations, the CT Policy request operation, and the self version upgrade check that are normally performed when a PC starts may not work. To ensure that these operations are performed properly, restart the operating system without shutting down.
After using the self version management feature to upgrade a client (CT), restart the operating system. If you install other software without restarting the operating system, the client (CT) may not upgrade properly.
To receive self version management requests from a client (CT) of V14.3.1 or earlier, switch the communication security settings. You can use the security enhancement command to switch the communication security settings. Refer to "DTKSETCN.exe (Security Enhancement)" in the Systemwalker Desktop Keeper Reference Manual for details on how to use the security enhancement command.
When registering a client (CT) earlier than V15.1.0 to a Management Server of V15.1.0 or later, you cannot use verification during registration of client (CT) devices. Cancel the client management password. Refer to "Perform Terminal Operation Settings" in the Systemwalker Desktop Keeper User's Guide for Administrator for details.
Communications between the Management Server or the Master Management Server and a client (CT) are encrypted.
Therefore, there are restrictions on unencrypted communications, such as communication with a client (CT) of V14.3.1 or earlier to which the communication encryption update has not been applied.
Clients of V13.3.0 - V14.3.1 must be upgraded to V15.1, or the urgent updates released in September 2014 or later must be applied to the clients.
Clients of V13.2.1 or earlier cannot be used. They must be upgraded to V15.1.0.
After the Management Server is upgraded to V15.1.0, only a client of V15.0.0 or V15.1.0 can be installed.
A client (CT) of V14.3.1 or earlier to which the communication encryption update has not been applied, cannot be upgraded because communication with the new Management Server for registering management information is restricted. For this reason, the urgent updates released in September 2014 or later must be applied to clients (CT) beforehand.
Note
Notes when installing Client (CT) on (Master) Management Server
In the case of installing the Client (CT) on a (Master) Management Server, when setting version upgrade based on the self version management function of the Client (CT), whether to perform self-version upgrade through common self version management function will be requested. Because the server is required to restart after self-version upgrade, consider the application status of other Clients(CTs) such as connection status and determine whether to apply.
Behavior when confirmation windows and completion windows are hidden
Even when Display self version upgrade confirming window and Display the reboot confirming window are not selected in the client operation settings, the dialog box about copying modules from the server will be displayed on the client side.
Note
Behavior when confirmation windows and completion windows are hidden
Even when Display self version upgrade confirming window and Display the reboot confirming window are not selected in the client operation settings, the dialog box about copying modules from the server will be displayed on the client side.
Point
By specifying the IP address or computer name, self-version upgrade can be performed to the specified Client (CT).
Not all Clients (CTs) should perform self-version upgrade collectively; only the specified Client (CT) should perform the upgrade.
For example, use in the following cases:
When trying to test the specific section before performing version upgrade completely
When trying to perform according to the section and working place
When trying to perform according to certain number of sets (CTs) in order to disperse the load
This function can be performed by creating "CT file (SWCTVerUpIP.txt) that can perform self-version upgrade".
The setting method is as follows: perform this procedure before performing the after-mentioned procedures for version upgrade.
Copy (or rename) "SWCTVerUpIP_sample.txt" as "SWCTVerUpIP.txt". Save "SWCTVerUpIP_sample.txt" to the following folder.
In the case of any server other than Windows Server(R) 2008 and Windows Server(R) 2012:
[OS Installation Drive] \Document and Settings\All Users\Application Data\Fujitsu\Systemwalker Desktop Keeper
In the case of Windows Server(R) 2008 and Windows Server(R) 2012:
[OS Installation Drive] \ProgramData\Fujitsu\Systemwalker Desktop Keeper
Open "SWCTVerUpIP.txt" through text editors such as Notepad.
Record the IP address or computer name of CT that can be performed self-version upgrade.
Save "SWCTVerUpIP.txt". (Do not move from the folder above.)
For file details and how to specify the IP address or computer name, refer to "Settings File of Self Version Upgradable of CT " in Systemwalker Desktop Keeper Reference Manual.
The procedures for version upgrade based on the self version management function are as follows. The file saving target indicated in the following procedures is different from the installation target when modifying the OS.
Set Server
Perform the following settings on the subordinate Management Server/Master Management Server to the Client (CT).
In the Management Server/Master Management Server, select Control Panel > Network Connection.
Select "Local Area Connection" and disable the local area connection. Wait for 1 minute after disabling before performing the following procedures.
The Windows service window is displayed on the Management Server/Master Management Server. Select each of the following services and select "Stop" from the "Operation" menu". It will take 30 seconds to 1 minute to stop. In addition, immediately after you restart SWServerService or after the date has changed (00:00), available space in the database will be checked. This check operation takes about 15 minutes, and services may not stop during this time. Wait a while and then check if the services have stopped.
SWLevelControlService
SWServerService
After the above services are stopped, enable "Local Connection".
On the Management Server/Master Management Server, save the file "SWCTVerSettings2.ini" under Setup folder "win32\DTKUpdate" to the following folder:
In Windows Server(R) 2008: "C:\Windows\System32"
In Windows Server(R) 2003: "C:\Windows\system32"
In Windows Server(R) 2003, 2003 R2 x64 Edition, Windows Server(R) 2008 64-bit Edition, Windows Server(R) 2008 R2 or Windows Server(R) 2012: "C:\Windows\SYSWOW64"
For the file "SWCTVerSettings2.ini", open the file properties, cancel the selection of "Read Only" check box, click the OK button.
On the Management Server/Master Management Server, save the following folder to the location recorded in DistModuleDir of file "SWCTVerSettings.ini".
Ver4.9.0.1 folder in the win32\DTKUpdate folder on the setup disk
Save the file "SWCTVerSettings.ini" to the following folder:
In Windows Server(R) 2008: "C:\Windows\System32"
In Windows Server(R) 2003: "C:\Windows\system32"
In Windows Server(R) 2003, 2003 R2 x64 Edition, Windows Server(R) 2008 64-bit Edition, Windows Server(R) 2008 R2 or Windows Server(R) 2012: "C:\Windows\SYSWOW64"
Perform the CT self version upgrade settings by using the server settings tool.
Click the Folder/CT Self Version Upgrade Settings button in the server settings tool menu.
The Folder/CT Self Version Upgrade Settings window is displayed.
Perform "Management Server settings" and "Client operation settings" displayed in CT self version upgrade settings.
(No need to set Folder settings here. For the settings, refer to "2.3.6.9 Set Saving Target Folder".)
Item Name | Descriptions |
Version | When the ini file (SWCTVerSettings2.ini) for CT self-version upgrade exists, the version specified in the ini file for CT self-version upgrade is displayed. It is not displayed when the ini file for CT self-version upgrade does not exist. |
Module saving target on CT | The target folder for saving Client (CT) self-version upgrade module is specified. The specifying method is as follows:
A maximum of 96 halfwidth characters (48 fullwidth characters) can be entered in the specified full path. The followings symbols are not allowed in the folder name: |
Number of simultaneous download (maximum) | Multiplicity of Client (CT) self-version upgrade is set. The value that can be set is within 0-25. When specified as 0, self-version upgrade processing cannot be performed. When INI file for CT self-version upgrade does not exist, it cannot be displayed and set. |
Item Name | Descriptions |
Display self version upgrade confirming window | Settings to confirm whether to perform self-version upgrade in Client (CT) with the user. However, when performing self-version upgrade from V13.2.0 or earlier, no matter whether Display the Window for Confirming Version Auto-upgrade is selected or not, the window for confirming self-version upgrade will be displayed. (This will be valid if selected when executing Edition upgrading of the same version) If this option is selected, the following information will be displayed after starting the Client (CT) terminal, and the user can select whether to execute self-version upgrade. (Operation in V13.2.0 or earlier). ---------------------------------------------------------------------- S101-ASK002 provides with the latest version. When updating to the latest module, click "Yes". Not to update, click "No". Reboot OS after selecting "Yes" and completing the update, thus end the application. ---------------------------------------------------------------------- Selecting Yes will execute self-version upgrade. Selecting No will not execute self-version upgrade. |
Display the error sent when the self version is upgrading | Settings whether to display the error window if errors occurred when performing self-version upgrade in the Client (CT). If this option is selected, if errors occur during self-version upgrade, the following error information will be displayed and the processing will be cancelled. The user needs to close the error window manually, or self-version upgrade will not stop (up to the action of V13.2.0 or earlier). ----------------------------------------------------------------------
[I401-ERR011] Failed to install Systemwalker Desktop Keeper Client.
Please confirm the errors in the installation log file.
Installation log file:[Name of Installation Log File].
Cancel installation
---------------------------------------------------------------------- |
Display the reboot confirming window | Settings whether to display the restart window after performing self-version upgrading in the client (CT). This item is valid only when Reboot by force is not selected. When Reboot by force is selected, this option will be grayed out. If this option is selected, after the installation based on self-version upgrade is completed, the restart window is displayed. Select either "Yes, restart the computer immediately." or "No, restart the computer later". If this option is not selected, after the installation based on self-version upgrade, no window will be displayed. Restart after completing modification through "Reboot by force" settings of the following item. Also, operate the Client (CT) of the version before applying self-version upgrade before rebooting. |
Reboot by force | Settings whether to restart by force after performing self-version upgrade in Client (CT). This item is valid only when Reboot confirming window is not selected. When Reboot confirming window is selected, this option will be grayed out. If this option is selected, reboot automatically after the installation based on self-version upgrade has been completed. When the file is opened, because it will be ended without being saved, content might be lost. If this option is not selected, the processing will be ended after the installation based on self-version upgrade has been completed. If Display the reboot confirming window is not selected, the restart confirmation window will not be displayed and the operation system will not be restarted. The user should restart it manually. |
Note
In case of Windows Vista(R), the window for reboot confirmation will not be displayed
When the OS is Windows Vista(R) and the environment self-version upgrade of V13.2.0/V13.2.1 Client (CT) has been installed, even if "Display Reboot Confirmation Window" is selected, the window for reboot confirmation will not be displayed. Although the window for reboot confirmation is not displayed, the version upgrade will take effect after PC is rebooted because the installation has been completed. If the installation version is V13.3.0 Client (CT), this case will not occur.
Create the CT silent installation file by using server settings tool. For details on how to use the setting tool, refer to "Create installation settings file".
Point
Items viewed during version upgrade by using self version management function
Only the following items specified during creation of the CT silent installation file are referenced during a version upgrade using the self version management feature. Other items will not be referenced.
Printing monitoring mode
E-mail attachment prohibition
Creation Settings of File Export Utility Icon
Port number (for E-mail attachment prohibition)
Port number (for E-mail attachment prohibition 2)
Port number (for E-mail sending monitoring)
Apply policy immediately after logging on Windows
Save the CT silent installation file created in Procedure 10. to the following folder of the recorded location in DistModuleDir confirmed in Procedure 7.
"Ver4.9.0.1"
On the Management Server/Master Management Server, the Windows service window is displayed, select the services to be cancelled ("SWLevelControlService" and "SWServerService") and select Start from the Operation menu.
Operations of Client (CT)
Start and log on to the Client (CT) of version upgrade.
The following message is displayed:
[S101-ASK002] provides with the latest module. When updating to the latest version, please click "Yes". When not to update, please click "No". If selecting "Yes" and OS should be restarted after the update is completed, please end the application.
Note
Select Yes.
Make sure to click the Yes button in the message window above. When clicking the No button, the "E-mail sending log obtaining " and "E-mail file attachment prohibition" cannot be operated before rebooting.
After clicking the Yes button, the "Update Completed" window will be displayed.
Note
Prohibition and log collection cannot be operated well if the system is not rebooted
Make sure to restart in the following window. If not, the "E-mail Sending Log Acquisition Function" cannot operate.
Notes when setting E-mail attachment prohibition mode
When using Windows Vista(R), Windows Server(R) 2008, Windows(R) 7, Windows(R) 8, Windows(R) 10 or Windows Server(R) 2012, only the port monitoring mode can be selected as E-mail attachment prohibition mode.
For the port for E-mail attachment prohibition, make sure to specify a port not used in other processing and communication.
When performing version/edition upgrade from the following versions to V15.1.0, after installing "E-mail sending log obtaining" and "E-mail file attachment prohibition ", these functions cannot operate before rebooting.
- BEV12.0L20
- SEV12.0L20
- BEV13.0.0 /SEV13.0.0
When upgrading from the following versions to V15.1.0, before rebooting, the version before upgrade operates well.
- BEV13.2.0 /SEV13.2.0
- V14.2.0
Click the Finish button.
Client (CT) is restarted.
