Hitachi

JP1 Version 11 JP1/IT Desktop Management 2 Distribution Function Administration Guide


5.3.1 Using ID groups

The following figure shows an example of using ID groups in a JP1/IT Desktop Management 2 system:

Figure 5‒12: Example of using ID groups

[Figure]

The following describes the procedures associated with ID groups, how to use ID groups in a hierarchical system, and how to use ID groups in a relay system or management relay server.

Organization of this subsection

(1) Procedures associated with ID groups

(a) Creating ID groups

You can create an ID group by specifying the following information on the managing server:

  • ID group name

    The name you specify is used to select the ID group as a destination during job distribution.

  • Password (optional)

    You can specify a password that the user must provide when registering a managed computer in the ID group. Users cannot register their computers in the ID group without entering the correct password.

  • ID-management relay computer

    Specify a host (relay system or management relay server) to be used as an ID-management relay computer. You can specify multiple relay computers for a single ID group.

(b) Registering managed computers in ID groups

Use the Register ID dialog box on a managed computer to register a managed computer in an ID group. To do this, connect to the ID-management relay computer from the managed computer and then register the computer in the ID group managed by the ID-management relay computer. You can also register computers in ID groups from the managing server. There is also a process by which computers newly added to the JP1/IT Desktop Management 2 system are automatically registered in ID groups.

The ID-management relay computer for a managed computer is the higher system that is displayed on the Connection-destination settings panel when the agent is set up. For JP1/IT Desktop Management 2 - Manager, the ID-management relay computer for a managed computer is the higher system that is specified when the management relay server is set up.

(c) Executing jobs on the managing server with ID groups specified as the destination

You can execute the following jobs with an ID group specified as the destination:

  • Install package job#

  • Send package, allow client users to choose job

  • Get system information from computer (UNIX) job#

  • Get software information from computer (UNIX) job#

#

This job is also applicable to agents for Mac.

A job for which an ID group is specified as the destination (ID group job) is transferred to the ID-management relay computers managing the specified ID group. The ID-management relay computer stores the job and executes it on each computer registered in the specified ID group. If you register a computer in an ID group after executing an ID group job that specifies that ID group as a destination, the stored job is executed on the computer as soon as it joins the ID group. Therefore, you must consider the retention period of the distributed packages on the relay system when executing a job with an ID group specified as the destination. Because packages are deleted from the relay system when the retention period of the job expires, the packages will no longer be distributed to computers that join the ID group after that point.

(d) Execution results of ID group jobs

When you execute the following jobs with an ID group as the destination, you can check the results of job execution at the managed computer from the managing server. For details about how to check the execution results of ID group jobs, see 9.4.4 Displaying the job status.

  • Install package job

  • Send package, allow client users to choose job

(e) Editing ID groups

After creating an ID group, you can edit it in the following ways on the managing server:

  • Add or delete an ID-management relay computer

  • Change the password

  • Delete the ID group

  • Register managed computers in the ID group (from a file)

  • Register an ID group in an ID-management relay computer

(2) Using ID groups in a hierarchical system

The following describes the considerations that apply when using ID groups in a system that incorporates multiple managing servers in a hierarchy.

(a) Creating ID groups on a management server

When you create an ID group on a management server, you can set subordinate relay systems or management relay servers as the ID-management Relay Computer.

For details about how to set a relay system or management relay server as the ID-management relay computer, see 5.3.2 Creating ID groups.

(b) Managing ID groups on management relay servers

On a management relay server, the Destination window displays the ID group specified as an ID-management relay computer by the higher management server, as well as the ID group created on the management relay server.

On a management relay server, you can perform the following operations on an ID group created by a higher management server:

  • Deleting ID groups

  • Deleting computers registered in ID groups

(c) Managing the same ID group for multiple managing servers

As shown in the following figure, you can create a single ID group for multiple management servers.

Figure 5‒13: Managing the same ID group for multiple managing servers

[Figure]

On both the primary management server (Man00) and the management relay server (Man01), an ID group called Windows7 can be created by using the relay system (Sub00) as an ID-management relay computer.

However, Man00 cannot create an ID group called Windows7 by using Man01 as an ID-management relay computer. Because another ID group of the same name was created on Man01, that server cannot become an ID-management relay computer for Man00 with the same ID as the ID created on the local system.

If you delete an ID group or change an ID-management relay computer, the change details will be reported from the changed system and automatically reflected in the information held by its higher system.

The following figure shows an example of deleting the ID groups managed by multiple managing servers.

Figure 5‒14: Deleting the ID groups managed by multiple managing servers

[Figure]