4.6.5 Analyzing management options required in a multi-server configuration
This section describes some points to be considered before you operate JP1/IT Desktop Management 2 in a multi-server configuration.
- Analysing a hierarchical structure
-
In view of departments and network configurations of the system you want to manage, analyze the following items regarding a hierarchical structure of the multi-server configuration:
-
The number of management relay servers to be installed
-
To which server each management relay server is connected
-
The range of computers managed by each management server
-
Whether to provide a relay system
Note that if you operate a JP1/IT Desktop Management 2 system in a NAT environment, you need to provide a management relay server under the NAT device.
For details on multi-server configurations, see 4.4.3 Multi-server configuration.
-
- Analyzing license holding options for each management server and the range of shared licenses
-
If you want to use each management server to manage the number of product licenses of JP1/IT Desktop Management 2 that are held by or remaining in each management server, consider the license holding options of each management server and the ranges of shared licenses. If you want to limit the number of devices that can be managed by each management server, distribute the product licenses on the primary management server to each management relay server. If you want to register a product license (purchased under a contract different from the one on the primary management server) on a management relay server, authorize product license registration for the management relay server.
For details on how to manage product licenses in a multi-server configuration, see 3.3 Managing product licenses in a multi-server configuration.
- Analyzing which management server manages operation logs
-
Consider which management server collects operation logs and which management server stores operation logs to accommodate multi-server configuration system operations. Also consider whether the operation logs collected by each management server are to be reported to the higher management server.
For details on how to manage operation logs in a multi-server configuration, see 2.18.11 Managing operation logs in a multi-server configuration.
- Analyzing which management server manages the revision history
-
Consider which management server in the multi-server configuration manages the revision history. Based on the decision, consider whether each management server collects the revision history for devices that are not directly under the server. We recommend that you do not collect revision history for those devices if the management server is operated under a NAT environment without the attendance of an administrator, or if you want to distribute loads among the management servers.
For details on how to manage revision history in a multi-server configuration, see (6) Collecting revision history of the devices managed by management relay servers under the local server.
- Analyzing which management server manages asset information
-
Consider which management server in the multi-server configuration manages the asset information.
For details on how to manage asset information in a multi-server configuration, see 2.18.12 Managing assets in a multi-server configuration.