This describes how to upgrade the versions of a Management Server/Master Management Server on the same server.
Issues to consider before version upgrade
Version upgrade on Windows Server(R) 2003 is not supported. Construct the server on the supported operating system and perform version upgrade. For supported operating systems, refer to "OS" of Systemwalker Desktop Keeper User's Guide. For version upgrade on different servers, refer to "4.3.2 Upgrading on Different Servers".
When performing version upgrade, usage of the Management Server/Master Management Server should be stopped. Thus, execute in the time frame when there are less users so as to not affect business.
When modifying the communication port of the Management Server, add the port number after modification to the list of allowed ports in the firewall.
Data should be transferred when version upgrade. It takes some time to operate according to the database capacity. The time for backing up user assets from the current database, the time for defining a new database, and the time for restoring the user assets to the database must be taken into account. In addition, if using the Log Viewing Database, the time for defining the new Log Viewing Database and the time for restoring the data to be referenced must also be taken into account.
In the environment where a large amount of attached data and command logs exist, when executing the overwriting installation of a Management Server/Master Management Server, access authority confirmation/modification of the attached data and command log will take longer time. (Time standard for overwriting installation: it takes about 30 minutes for the attached data and command log of 100,000 files.)
The available functions are different for the primary administrator created by Systemwalker Desktop Keeper V12 and the primary administrator created by Systemwalker Desktop Keeper V13 or later.
The primary administrator of V13 or later can use the server settings tool, backup tool, restore tool, and restore command.
When upgrading from V12.0.0L20 or earlier to V15.1.0, the primary administrator of V12.0.0L20 or earlier will be transferred as the administrator and can therefore continue using the Management Console and Log Viewer. However, the administrator will not become the primary administrator of V15.1.0. To use the same primary administrator (secureadmin) from V12.0.0L20 or earlier in V15.1.0, specify the password of the primary administrator in the following login windows as explained below:
Server settings tool, backup tool, restore tool, and restore command
When starting as the primary administrator user, specify the password for the primary administrator indicated in "Overwriting Install Management Server/Master Management Server".
Management Console and Log Viewer
When starting as the primary administrator (secureadmin) user from V12.0.0L20 or earlier, specify the password set in V12.0.0L20 or earlier.
When upgrading from V14.0.0 or later with Allow specified in All Unknown ISAPI Extensions for IIS, you will not need to configure the IIS setting again when installing the Management Server or Master Management Server. The web console will run with Allow specified in All Unknown ISAPI Extensions as is.
When upgrading from V14.0.1 or earlier, status window aggregation runs using the initial value of 1:00. The Level Control Service must be running during status window aggregation, so ensure that the processes for stopping status window aggregation and the Level Control Service (such as backup and restore, and data transfer) are not duplicated. If these processes are duplicated, change the status window aggregation schedule after upgrading. Refer to "Prepare for Using Status Window" in the Systemwalker Desktop Keeper User's Guide for Administrator for details on how to change the schedule.
If you are using the Log Viewing Database at the time of upgrade from V14.2.0 or V14.3.0, delete it before upgrading and re-create it afterwards.
In the Confirm Number of Tables window of the Backup Tool, check the number of records in each table.
Calculate the required disk space based on the displayed number. The size depends on the contents of the table logs, but calculate the size assuming the average of 1 KB/record.
Note that it may not be possible to back up a large volume of records at one time. In this case, split the backup period using a maximum of 20 million per table as a guide when calculating the required disk space.
In Windows Server 2012, due to enhancements to UAC security, the network drive cannot be specified if the backup tool is not started by the built-in Administrator.
Before performing backup as any user other than the built-in Administrator, assign the network drive from the elevated command prompt.
Systemwalker Desktop Keeper V15.1.0 does not allow migration of a database of an older version, so backing up and restoring the necessary data requires additional time.
The standard time for backup and restore is as shown below.
Measurement result
Data backup
Calculate using the number of logs to be backed up - the standard is as follows:
7,000 logs/second (Xeon, 2.0 GHz, 2 GB memory, RAID 1 configuration)
Note: More time may be required depending on server performance and the RAID configuration.
Deletion of databases handled by an older version of Systemwalker Desktop Keeper
Takes just minutes, even with very large databases.
Database construction with Systemwalker Desktop Keeper V15.1.0
Takes approximately 1 minute (Xeon, 2.0 GHz, 2 GB memory, RAID 1 configuration)
Note: More time may be required depending on server performance and the RAID configuration.
Data restore
Calculate using the number of logs to be restored - the standard is as follows:
5,000 logs/second (Xeon, 2.0 GHz, 2 GB memory, RAID 1 configuration)
Note: More time may be required depending on server performance and the RAID configuration.
If upgrading Systemwalker Desktop Keeper in an environment where Systemwalker Desktop Patrol is already installed, services that manage iOS devices will automatically stop.
In this case, the services that manage iOS devices cannot be used until the operating system is restarted.
When performing verification during client (CT) device registration, set a client management password in the Terminal Operation Settings window of Management Console. Refer to "Perform Terminal Operation Settings" in the Systemwalker Desktop Keeper User's Guide for Administrator for details.
The procedures for version upgrade of a Management Server/Master Management Server are as follows: execute the following procedure according to "4.2 Upgrade Procedures".
When IIS has not been installed here, it should be installed before version upgrade of a Management Server/Master Management Server. For IIS installation, refer to "2.3.1 Installation and Settings of IIS
Logon to Management Server/Master Management Server
Log on to Windows with an Administrators group affiliated user or Domain Admins group affiliated user. When other applications are in use, end these applications.
Stop Level Control Service and Server Service
Select Control Panel > Network Connection.
Select "Local Area Connection" and disable local connection. Wait for 1 minute after disabling before continuing to the following procedures.
When the Windows service window is displayed, 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 restarting SWServerService or after the date has changed (00:00), available space in the database will be checked. This check takes approximately 15 minutes, and services may not stop during this time. Wait for a few moments and then check if the services have stopped.
SWLevelControlService
SWServerService
After the services above have been stopped, enable "Local Service".
Install and set IIS (when upgrading from V12 or V13)
The procedures for installing and setting IIS are the same as 2.3.1 Installation and Settings of IIS" during the new installation. Refer to these procedures.
Back up Management Information and Log Information
In the environment before version upgrade, back up the management information, log information and command log by using the backup command or backup tool of Systemwalker Desktop Keeper. Back up (by copying the file) the V12 command logs to a log file.
When backing up by directly using the batch file in the backup command installation folder, the batch file itself should be backed up because it will be overwritten during version upgrade.
Back up the batch file before version upgrade, and reflect the settings to the new batch file after version upgrade. However, because of the format change, do not restore through direct replacement.
Note
Notes on backup
Make sure to back up management information. If not, the system cannot be restored. When not transferring log information, there is no need to back it up.
Back up management information and log information at the same time. Data backed up not at the same time cannot be transferred normally.
See that take the data in all periods as the backup target of log information.
V14.2.0 and V14.3.0 do not provide any function that enables the Log Viewing Database to back up management information or log information. Therefore, if you are using the Log Viewing Database, check the scope of stored data before migrating to these versions, and prepare in advance the data to be stored in the Log Viewing Database after the upgrade.
Command log cannot be backed up through V12 backup command.
In V12, back up the command log.
Back up all files in Prompt Log folder of V12 to arbitrary backup folder. Files to be backed up need not to be restored in the operation of self-version upgrade, but should be restored when restoring log information.
PromptLog folder of V12 is the folder specified as the log file saving target when executing "Installation of Management Server/Master Management Server". (Example: C:\DTK\PromptLog)
Back up all management information and log information.
Use the backup tool (V13.0 or later) or the backup command to back up all periods of management information and log information for the Management Server and Master Management Server.
If it is not necessary to restore the logs for all periods to the Operation Database, or if storing them in the Log Viewing Database, it is recommended that you back up the log information for each period to be referenced. In this case, preparing a batch process is useful for performing backup while splitting the periods by using the backup command.
Use the backup command provided in each version or the backup tool to perform backup. Refer to the manual for the applicable version for details on how to perform backup using the backup command or backup tool.
Check the backup execution result.
It checks the backup execution result for management information and log information, and confirms that backup has been completed normally.
Back up the batch file for backup. However, when the batch file is not in use, or it is moved to the user's arbitrary folder that is not the installation target of Systemwalker Desktop Keeper for use, there is no need to back it up.
For the installation target of the batch file for backup, refer to the manual of each version.
Note
When upgrading from V13 or V14, the batch file for backup should also be backed up
When upgrading from V13 or V14, the backup procedures of the batch file for backup above will also be required. Confirm the conditions required for the backup above and Procedure 4.
Deleting the Log Viewing Database (when upgrading from V14.2.0)
If using the Log Viewing Database, use the Operating Environment Maintenance Wizard (Construct/Delete Environment) feature to delete the Log Viewing Database.
Deleting the Operation Database (when upgrading from V13.0 to V15.0)
The older version database must be deleted.
Use the Operating Environment Maintenance Wizard (Construct/Delete Environment) tool to delete it.
If the Management Server installer is run in an environment where there is an older version database (Symfoware RDB SWDTK, Symfoware RDB SWDTK2), the following message will be displayed and upgrade will fail.
Systemwalker Desktop Keeper Management Server cannot be upgraded. The following database system was not deleted. %1 %2
Note: Variable information will show Symfoware RDB SWDTK, Symfoware RDB SWDTK2, or both.
After deleting the older version database, run the Management Server installer.
Deleting the Operation Database (when upgrading from V12)
The older version database must be deleted.
Follow the procedure below to delete the data area from the database:
Click Start > All Programs > Microsoft SQL Server > Enterprise Manager.
The SQL Server Enterprise Manager window will be displayed.
In the tree view on the left side of the window, click Console root > Microsoft SQL Servers > SQL Server group > (LOCAL)(Windows NT) > Database.
Right-click DTKDB on the right side of the window and click Remove.
A message prompting you to confirm deletion of the database will be displayed. Click Yes.
Uninstalling the database when upgrading from V13 or V14)
Note
If the database remains in the installation folder of database-related files in the Management Server or Master Management Server (because another application is using it, for example), do not delete the folder. Otherwise, the database management system can no longer run.
Installation folder of database-related file: C:\DTK (default path)
Uninstall the database (in this example we use Symfoware Server).
Check if any other application is using the database (do not uninstall the database if an application is using it).
Follow the procedure below to uninstall the database:
Log on using the Windows account (administrator authority) used when installing the Management Server.
Click Control Panel > Add or Remove Programs or Add/Remove Programs.
Select "Symfoware Client" and click Remove.
Note
Message when Symfoware Client is uninstalled
When uninstalling Symfoware Client, the message of "Symfoware .NET Data Provider Installer" may be displayed. Click OK to proceed.
Select "Symfoware Server Enterprise Edition" and click Remove.
Overwriting Install Management Server/Master Management Server
Note
In a 3-level structure, perform version upgrade on the Master Management Server first. After that, perform version upgrade on the Management Server.
Besides, to avoid accidents in the process of version upgrade, before completing version upgrade on all Management Serves and the Master Management Server, do not view the subordinate Management Server information through the Master Management Server.
If the Management Console coexists with the Management Server or Master Management Server, it will be upgraded at the same time.
When coexisting with the Log Analyzer Server, perform version upgrade as follows:
Delete database of older version Log Analyzer Server and Uninstall Log Analyzer Server
Refer to "5.6 Uninstall Log Analyzer Server" for details.
Upgrade Management Server
Install this version Log Analyzer Server and construct database
Refer to "2.7 Construct Log Analyzer Server" for details.
When using the Log Analyzer regardless of coexisting with the Log Analyzer Server, set the Log Analyzer after upgrading the Management Server.
Refer to "2.7.3.1 Set Log Analyzer Environment on Management Server/Master Management Server" for details.
The procedures for overwriting installation Management Server/Master Management Server are as follows:
After inserting DVD-ROM of Systemwalker Desktop Keeper into PC, the installer window is displayed.
Select Management Server/Management Console Installation.
When the Setup has not been started, start "swsetup.exe" of DVD-ROM drive.
After the "Welcome to Systemwalker Desktop Keeper Server Setup" window is displayed, click the Next button.
When upgrading from V12.0.0L20 or earlier, the "Select the installation target" window of the server function will be displayed. (Not displayed when upgrading from V13.0.0 or later to V14.3.0. Access the next procedure.)
When not to modify the displayed installation target, click the Next button.
To modify the displayed installation target, click the [View] button of the folder to be modified, and click the Next button after the folder is modified.
When upgrading from V12.0.0L20 or earlier, the installation destination of the database-related files will be the folder containing the database at the same level as the installation destination of the Management Server.
Example: Setting the following folder as the installation destination of the Management Server
C:\Program Files\Fujitsu\Systemwalker Desktop Keeper\Server
The database-related files will be installed in the following folder:
C:\Program Files\Fujitsu\Systemwalker Desktop Keeper\DB
Note
The maximum length of the path to be specified for destination folder is 96 bytes.
When the old Log Viewer has been installed on the Management Server/Master Management Server, the following message will appear. After click the OK button in the message window, the old Log Viewer will be uninstalled before installation.
When the old Log Viewer has not been installed, continue to install.
Log Viewer V13.2.0 or earlier has been installed. Functions of Log Viewer V14.2.0 or later are contained in Management Server already, Log Viewer will be uninstalled.
Note
Do not delete the folder, or the database cannot be transferred
When uninstalling the Log Viewer, the following message for deleting the folder will appear, but do not delete the folder. Continue installing the Management Server directly.
The following folder might be reserved after uninstallation, please delete it manually. -Trace Log Saving Folder: [%1] %1 : Folder path of trace log saving folder
Do not restart here
A message prompting you to restart the operating system will appear after the Log Viewer uninstallation is completed, but do not restart and continue installing the Management Server.
If you restart the operating system by mistake, the overwriting installation of the Management Server will be interrupted, so reinstall it again. In this case, because the uninstallation of Log Viewer has been completed, the message above will not appear.
When the log linkage adapter of the Systemwalker Desktop Log Analyzer has been installed on the Management Server/Master Management Server, the following message will appear and the Log Viewer will be uninstalled. After clicking the [OK] button in the message window, linkage adapter will be uninstalled before installation. Also, the configuration value of the log linkage adapter in Systemwalker Desktop Log Analyzer will be adopted.
When the log linkage adapter has not been installed, continue to install.
Systemwalker Desktop Log Analyzer log linkage adapter V13.2.0 or earlier has been installed. Functions of log linkage adapter V14.2.0 or later are contained in Systemwalker Desktop Keeper Management Server already, the log linkage adapter will be uninstalled.
Note
Do not restart here
A message prompting you to restart the operating system will be displayed after you complete the uninstallation of the log linkage adapter; however, do not restart and continue installing the Management Server.
If you restart the operating system by mistake, the overwriting installation of the Management Server will be interrupted. If this happens, reinstall again. In this case, the message above will not appear because the uninstallation of the log linkage adapter has been completed.
The message below will be displayed. Click OK and continue with the installation process.
Upon completion, a window informing that the installation completed successfully will be displayed. Installation will continue until the window is displayed, so wait until completion.
The "I121-WRN001" message will be displayed.
The message below will be displayed. Click Finish.
The installation of Systemwalker Desktop Keeper management server was completed.
Upon successful completion, the confirmation window will be displayed.
To use the program, click Yes. The operating system will restart.
During version upgrade, the following error will be displayed in the event log, but there will be no problem:
[Type] Error
[Source] SWDTK
[Event ID] 3014
[Descriptions] Database structure of non current version. Confirm the database environment.
Construct the Operation Database
The procedures for constructing the Operation Database are the same as "2.3.3 Construct Database". Refer to that for details.
Restore management information and log information
When overwriting the installation of the management information and log information of the old version backed up by Management Server/Master Management Server previously, restore them by using the restoration tool of Systemwalker Desktop Keeper.
In the Administrator Information Settings window of the Server Settings Tool, add a user ID that has access privileges for backup and restore.
Restore management information and log information by using the restoration tool V15.1.0.
After the restoration, data will be transferred and the newly created information in V15.1.0 will be added automatically. For details on how to use the restoration tool, refer to "3.1.3 Restoring User Assets".
If upgrading from V12, copy the log file where the command logs are saved.
Set IIS
IIS settings will be performed automatically. However, when upgrading from V12 or V13, refer to "2.3.4 IIS Settings", and create the Systemwalker Desktop Keeper specified application pool as required.
Register the license key
About the registration of the license key, refer to "2.3.5 Register the license key"
Set Environment of Server
When the version is upgraded to V15.1.0, the configuration value in the previous version is still valid.
However, when upgrading from V13.0.0 or earlier, the detailed authority of user information set in the Administrator Information Settings of server settings tool will be transferred under the status of possessing all authorities. To modify, perform after completing transfer.
Also, for USB Device Registration/Update/Delete and E-mail Content Viewing in the Administrator Information Settings window, because not all administrators are authorized, authorize them after transfer if necessarily.
When upgrading from V13.2.0 or earlier, because the status window settings are not performed, set the conditions for aggregation in the environment setup. For how to set, refer to "Prepare for Using Status Window" of Systemwalker Desktop Keeper User's Guide for Administrator.
Also, perform server settings if the server environment is modified. The procedures for server settings are the same as "2.3.6 Set Environment of Management Server/Master Management Server" during the initial installation. Refer to that guide for details.
If upgrading from V15.0.1 or earlier, the range for the threshold value for database depletion monitoring is "5 to 20".
If the specified value is lower than 5% when upgrading, it will be overwritten to "5%".
Construct the Log Viewing Database (when upgrading from V14.2.0)
If you were using the Log Viewing Database, click Server settings tool > Build, delete, or show information of database in V15.1.0, and define the new Log Viewing Database.
The procedure for constructing the Log Viewing Database is the same as that in "2.3.3 Construct Database", so refer to that section.
In the Log Viewing Database, store the management information and log information you want to view. Use the Systemwalker Desktop Keeper Restoration Tool or restore command to perform restore. Refer to "3.1.3.1 Using the Restoration Tool" or "DTKTBLRESTOR.EXE (Restore Database)" in the Systemwalker Desktop Keeper Reference Manual.
