7.6 Procedure for migrating from a single-server configuration system to a multi-server configuration system

To migrate a management server built in a single-server configuration system to a multi-server configuration system, build a new multi-server configuration system, and then migrate data in the source environment to a database server.

Important note: The version of JP1/IT Desktop Management - Manager to be installed on the destination computer and the version on the source computer must match.

Important note: You cannot upgrade JP1/IT Desktop Management - Manager while migrating a management server. Accordingly, install the upgrade before or after migration.

Important note: The operation logs on a management server will no longer be accessible after migration to a multi-server configuration system. However, the operation logs on a site server will be accessible after migration to a multi-server configuration system.

Important note

On a computer that runs Windows 8, do not specify the following folders during installation:

Folders under system-drive:\program files\WindowsApps
Folders in storage areas created by virtual provisioning

To migrate a management server from a single-server configuration system to a multi-server configuration system:

Stop the JP1/IT Desktop Management services.

From the Windows Start menu, select Administrative Tools and then Services. In the dialog box that opens, right-click a service name, and then select Stop to stop the service. Stop the following services:
- JP1_ITDM_Service
- JP1_ITDM_Agent Control
- JP1_ITDM_Web Container
Back up the database.

Use Database Manager to back up the database. Leave at least 20 gigabytes of free space on the drive containing the backup folder.
If you migrate the environment to a different computer, disconnect the source computer from the network.
If you are using the same computer before and after migration, uninstall JP1/IT Desktop Management - Manager on the computer before migration.
Build a database server.

Perform a custom installation of JP1/IT Desktop Management - Manager on the computer that will be used as the database server. After installation, start setup. In the Server Configuration Settings view, select Multi-server configuration, Database server and 16GB.

Also, set sharing in the Folder Settings view, and then specify the folder that can be accessed from a management server in Data folder.
During database server setup, set the folder specified in Data folder as a shared folder that can be accessed from the management server.
Build a management server.

On the computer that will be used as the management server, perform a custom installation of JP1/IT Desktop Management - Manager. After installation, start setup. In the Server Configuration Settings view, select Multi-server configuration and then Management Server.

Also, in the Settings for the Data Folder Shared Between view, specify the folder you specified as a shared folder in step 6 in Data folder shared between servers.
Restore the database you backed up in step 2.

Use Database Manager to restore the database.
Register the JP1/IT Desktop Management product license.
Change the connection destination of the agent.

Log in to JP1/IT Desktop Management - Manager. In Agent Basic Settings in agent setup, select Basic Settings and then Management Server to set the IP address or host name of the new computer.

Note that this procedure is required only when the IP address or host name of the management server is not the same before and after replacement.
Change the connection destination of the site server.

In the Server Configuration Settings view of the Settings module, change the value in Management Server to the management server that will be used after migration.
If necessary, change the network access control settings.

In the Network Access Control Settings view of the Settings module, delete the IP address of the management server used before migration from Exclusive Communication Destination for Access-Denied Devices, and then add the IP address of the management server that will be used after migration.
If necessary, change the IP discovery settings.

In the Configurations view of the Settings module, select IP Address Range and then Search Node Locations to change the management server segment setting to the management server network segment that will be used after replacement.
Set the storage location for the operation logs.

To manage operation logs, in the Server Configuration Settings view of the Settings module, select Server Configuration Settings and then Storage Location for Operation Logs and change the storage location from the management server to a site server group. The reason for this change is that management servers cannot be specified as the storage location for operation logs in a multi-server configuration system.
If the same computer will not be used before and after migration, uninstall JP1/IT Desktop Management - Manager on the computer used before migration.
Delete the backup you created in step 2.

Migration from a single-server configuration system to a multi-server configuration system is complete.

Tip: If necessary, delete the backup data you obtained from the source computer after the replacement finishes.

Tip: After the replacement finishes, you can check whether the agent is connected to the management server in the Device List view of the Settings module. If Last Alive Confirmation Date/Time has been updated, the agent is connected. If the agent is not connected, make sure that the connection destination was set correctly during agent setup on the user's computer.

Cautions applying to the migration procedure

Important note: If the IP address of the new computer is no longer the same as that of the old computer, and you want to change the connection destination of the agent, you need a network configuration in which the new management server and the agent can directly access each other. A network in which direct access is possible means a network in which a host name or an IP address is used for access, and in which the server and the agent can communicate with each other directly via ICMP. In addition, you must be able to pass the TCP protocol port that is used by the management server and the agent.

Important note

If you want the management server to inherit the system configuration on the old computer, the IP address of the managed device must match before and after replacement.

For example, if the IP address of the managed computer changes due to a change in the installation location during management server replacement, that computer is not connected to the new management server. If this happens, create an installation set on the new management server to reinstall the agent on the computer. This action connects the computer to the management server.

Important note: Manage the database backup on the old computer by using a user ID and password to prevent access by personnel other than the administrator. If an unintended user obtains the backup improperly and then restores it, that user can use the managed devices from the user's management server just as you protect the management server.

Important note

If you want to manage devices that were managed on the old management server on the new management server, restore the database you backed up on the old computer on the new computer. If the database is not restored, the agent installed on the managed devices will not be able to connect to the new management server.

If you want to manage new devices on the new management server, you do not need to back up and restore the database. In this case, however, if you want to manage the same devices that were managed before replacement, take either of the following actions after replacement:

For computers on which an agent is installed: Use the installation set you created on the management server after replacement to reinstall the agent.
For agentless devices: Run discovery to include devices as managed devices.

Important note

If you connect the old management server to a network without uninstalling JP1/IT Desktop Management - Manager, the agent on the new management server cannot be managed correctly.

This is because both of the servers can connect to the agent, and the agent might enter a state that the administrator did not intend because the management servers have given different instructions. In addition, information reported from the agent by connecting to the old management server is not reported to the new management server. As a result, there might be differences in the information managed by the two servers.

Related Topics:

To Page Top