Job Management Partner 1/Software Distribution Administrator's Guide Volume 1
![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
On the Destination page, specify the hosts or groups that are to be subject to execution of the job.
Figure 8-8 Destination page
![[Figure]](FIGURE/JOB0080.GIF)
First select a destination type, then select a destination and choose Add to add the destination. The Destination field displays the host, group, or ID group specified as the job execution target, or the organizational unit (OU), group, or computer managed by Active Directory. You can delete a destination or change a destination route. Note that a managing server of JP1/Software Distribution Client (relay system) can execute jobs only to the hierarchy level immediately below it.
The following describes the methods for adding destination types and destinations, and for changing a route.
- Organization of this subsection
- (1) Destination type
- (2) Procedure for adding a destination
- (3) Procedure for changing a route
- (4) Notes on specifying destinations
(1) Destination type
To specify destinations on the Destination page, first select the radio button for one of the following destination types:
- Host group
- ID group
- All lower clients
- Directory Information
(a) Host group
Select this type when you want to specify host groups, specific hosts (relay managers, relay systems, or clients), or directory information as the job destinations. If you change the destination type to Host group for a job in an ID group that has already been specified, the job is registered with its destination set to the relay system and relay manager managing the ID group or to the clients registered under the ID group. Select this type when you want to specify host groups or specific hosts (relay managers, relay systems, or clients) as the job destinations.
If the destination is host groups or specific hosts, the hosts on which the job will executed depends on the job type. The following table shows the relationship between the job type and the destination specification:
Table 8-2 Relationship between job type and destination specification
# |
Job type |
Specified destination |
Client |
Relay system |
Relay manager |
Host group |
1 |
Install package |
Host |
Host |
Host |
All |
2 |
Transfer package to relay system |
No |
Host |
Host |
Relay |
3 |
Batch delete packages on relay system |
No |
Host |
Host |
Relay |
4 |
Collect files from client |
Host |
Host |
Host |
All |
5 |
Collect files from client to relay system |
Host |
Host |
Host |
All |
6 |
Acquire collected files from relay system |
No |
Host |
Host |
Relay |
7 |
Delete collected files from relay system |
No |
Host |
Host |
Relay |
8 |
Send package, allow client to choose |
Host |
Host |
Host |
All |
9 |
Get system information from client |
Host |
Host |
Host |
All |
10 |
Get software information from client |
Host |
Host |
Host |
All |
11 |
Get user inventory information |
Host |
Host |
Host |
All |
12 |
Transfer registry collection definition |
Host |
Host |
Host |
All |
13 |
Transfer user inventory schema to client |
Host |
Host |
Host |
All |
14 |
Get system configuration information |
No |
Host#1 |
Host |
No |
15 |
Hold report |
No |
Host |
Host |
Relay |
16 |
Hold-report release |
No |
Host |
Host |
Relay |
17 |
Suspend file transfer |
No |
Host#2 |
Host#3 |
Relay#2 |
18 |
Resume file transfer |
No |
Host#2 |
Host#3 |
Relay#2 |
19 |
Report message |
Host#4 |
Host#4 |
Host#4 |
All#4 |
20 |
Set the software monitoring policy |
Host#4 |
Host#4 |
Host#4 |
All#4 |
21 |
Get software monitoring information from the client |
Host#4 |
Host#4 |
Host#4 |
All#4 |
Legend:
- Host:
- The job is executed at the specified hosts.
- No:
- The job is not executed at the specified hosts.
- Relay:
- The job is executed at the relay systems for the specified host groups, as well as at relay systems that belong to the specified host groups' lower host groups.
- All:
- The job is executed at all hosts belonging to the specified host groups, as well as at all hosts that belong to the specified host groups' lower host groups.
- #1
- The job is executed only at a relay system whose version is 05-21 or newer.
- #2
- The job is executed only at a Windows version relay system whose version is 07-00 or newer.
- #3
- Applicable only to relay managers with a JP1/Software Distribution Manager for Windows version 07-00 or later.
- #4
- Applicable only when the destination is a JP1/Software Distribution for Windows version 07-50 or later.
(b) ID group
Select this type when you want to specify ID groups as the job destinations. When an ID group is specified, JP1/Software Distribution executes the job for the clients that belong to that ID group.
If you want to execute a job for a new client to be added, specifying an ID group as the job destination works well. If the job is stored in the relay managing the ID, the job is automatically executed for the client when that job is registered in the ID group.
You can specify ID group as the destination type for the following job types:
- Install package
- Send package, allow client to choose
- Get system information from client
- Get software information from client
- Get user inventory information
- Transfer registry collection definition
- Transfer user inventory schema to client (only applicable to distribution of user-inventory items)
- Report message
- Set the software monitoring policy
- Get software monitoring information from the client
Note that if you specify a relay managing the ID that includes a route, do not specify multiple ID groups as the destination.
(c) All lower clients
Select this type when you want to execute the job for all hosts managed by relay managers.
When you select All lower clients as the destination type, you can specify as the destination only relay managers (or all lower clients as a group consisting of relay managers only). When All lower clients is specified, JP1/Software Distribution executes the corresponding job for all the hosts managed by the specified relay managers.
You can specify All lower clients as the destination type for the following job types:
- Install package
- Send package, allow client to choose
- Get system information from client
- Get software information from client
- Get user inventory information
- Transfer registry collection definition
- Transfer user inventory schema to client (applicable only to distribution of user-inventory items)
- Report message
- Set the software monitoring policy
- Get software monitoring information from the client
(d) Directory Information
Select this type when you want to specify organizational units (OU) or computers of Active Directory as the job destinations. If you specify Directory Information as the destination, you can select an OU, group, or computer of Active Directory.
You can specify Directory Information as the destination type for the following jobs:
- Install package
- Collect files from client
- Send package, allow client to choose
- Get system information from client
- Get software information from client
- Get user inventory information
- Transfer registry collection definition
- Transfer user inventory schema to client
- Report message
- Set the software monitoring policy
- Get software monitoring information from the client
When any other type of job is selected, a job execution dialog box starts with no destination specified.
To add a destination on the Destination page:
- On the Destination page, select the type of destination you want to add, and then choose Add.
The Add Destination dialog box is displayed. You can resize the Add Destination dialog box to the desired size. Once you change the size, the dialog box is displayed in that size from then on.
Figure 8-9 Add Destination dialog box
![[Figure]](FIGURE/JOB0090.GIF)
Select the host to be added to Destination from the list that is displayed in Host/Client when From or a Host group or ID group/Relay system is selected.
- From
- Select System Configuration, Destination, or Directory Information as the window to be used as the information source for adding the destination.
- Host group or ID group/Relay system
- If you selected System Configuration in the From menu, the relay managers and relay systems are displayed in a hierarchical structure. If you selected Destination, host groups or ID groups are displayed. If you selected Directory Information, the organizational units (OUs) and groups of Active Directory are displayed in a hierarchical structure.
- Host/Client
- If you selected System Configuration or Destination in the From menu, a list of relay managers, relay systems, or hosts in the host group that was selected in Host group or ID group/Relay system is displayed. To display clients immediately under the network, click Network in Host group or ID group/Relay system.
- If you selected Directory Information in the From menu, the computers belonging to the organizational unit (OU) or the members (group and computers) belonging to the group of Active Directory that was selected in Host group or ID group/Relay system are listed.
- Enter route
- To add a host that is not in the System Configuration window, specify the route to the host. Specify the route by separating each host by an exclamation mark (!) (for example, host-name-1!host-name-2!host-name-3). If you are using host IDs to manage the network, specify a host ID for the destination. If you are not using host IDs, specify a node identification key. For details about how to assign host names, see 8.1.2 Assigning host names in a JP1/Software Distribution system in the manual Setup Guide.
- For a job for which you specify a relay system as the destination, when you specify the route to the destination, specify the name of the relay system as both the route and the destination, as shown in the example below.
- Example:
- To specify dmp300 as the destination in the configuration of relay system (dmp500) - relay system (dmp300):
- dmp500!dmp300!dmp300
- To add an ID group, place a percent sign (%) at the beginning of the ID group. Note that you cannot specify a host group. Note that if you want to specify ID groups managed by a relay system, specify only one ID group.
- Example:
- To specify an ID group (ID01) used to manage dmp300 in the configuration of relay system (dmp500) - relay system (dmp300):
- dmp500!dmp300!%ID01
- To specify an ID group (IDSERVER) managed by JP1/Software Distribution:
- %IDSERVER
- In the boxes on the left, select a host, host group, ID group, or directory information that you want to add as a destination, and then click >.
The selected item is added to the Destination field on the right. Clicking >> adds all the hosts or computers displayed in the Host/Client menu to the Destination field.
To delete an item from the Destination field, click <.
If you selected Directory Information in the From menu, you can add the organizational unit (OU) of Active Directory selected in Host group or ID group/Relay system to the Destination field by clicking >>.
- Choose OK.
The Add Destination dialog box closes, and the specified destinations are displayed in the Destination field of the Destination page.
On the Destination page, choosing Change Route enables you to change a job execution route. In the event of an error in a relay system, you can use this feature to execute the job via another relay system.
You should note the following about changing a route:
- You cannot change the route for a relay manager or for a relay system or client being managed by a relay manager.
- If the job destination is a host group, ID group, or organizational unit (OU) of Active Directory, you cannot change the route.
- If you change the route for an installation job that is to be executed by a client user, the job execution results may be placed in permanent wait status. In such a case, reset the relay system or the client's target host subject to installation by the client user as the higher host on the new route.
- On the Client Control page, the Boot the client at the job destination option cannot be used.
To change a route:
- On the Destination page, select the route you want to change, and then choose Change Route.
The Change Transmission Route dialog box is displayed. The destination selected on the Destination page and all the relay systems are displayed with the route defined in the System Configuration window.
Figure 8-10 Change Transmission Route dialog box
![[Figure]](FIGURE/JOB0100.GIF)
- Select the relay system that is to be subject to route modification, and then choose Change, Move, or Add.
- Change
- Displays the Select Relay System to be Used dialog box. The relay system specified in the Change Transmission Route dialog box is moved under the relay system specified in the Select Relay System to be Used dialog box.
- Add
- Displays the Select Relay System to be Added dialog box. The relay system specified in this dialog box and all the clients under its management are moved under the relay system specified in the Change Transmission Route dialog box.
- Move
- Displays the Select Relay System to Which Client Will Move dialog box. The relay system specified in the Change Transmission Route dialog box and all the clients under its management are moved under the relay system specified in the Select Relay System to Which Client Will Move dialog box.
- Reset
- The relay system and the clients under its control in the Change Transmission Route dialog box are reset to the original order.
You can also drag and drop a client or relay system shown in the Change Transmission Route dialog box. Alternatively, you can select the icon's name part to directly enter the name.
- Choose OK.
The Change Transmission Route dialog box closes, and the new route is displayed on the Destination page.
You should note the following about specifying destinations.
(a) Limitation on the length of a destination specification
If a job destination specification exceeds 255 characters, the job execution status will not be displayed in the Job Status window. Use no more than 255 characters when specifying the destination.
(b) Changing the destination type
If you change the destination type to ID group for a job for which a host group has already been specified, all the destinations are deleted except for the ID group.
- On the other hand, if you change the destination type to Host group for a job for which an ID group has already been specified, the job is registered with its destination set to the relay system managing the ID group or to the clients registered under the ID group.
- Directory Information cannot be specified together with any other destination type. Therefore, if a destination has already been set and you change the destination type from Directory Information to another type, or from a type other than Directory Information to Directory Information, the existing destination setting is deleted.
(c) Handling of a job for which a nonexistent destination is specified
You should not create a job with any nonexistent destinations specified. Such a job may slow down Remote Installation Manager processing.
If you specify destinations that do not exist, only the actual destinations specified are used to execute the job. The job's post-execution status for a nonexistent destination depends on information specified during setup (JP1/Software Distribution Manager's or JP1/Software Distribution Client (relay system)'s ID Key for Operations page). If The job ends in error was specified for the When resolution of IP address fails item, the status would be Error; if The job starts was specified, the status would be Waiting for transmission.
(d) Job execution for a UNIX relay system
When you execute an Install package or Get system information from client job for a UNIX relay system, you must define in the system configuration a client with the same host name under the UNIX relay system. Specify this client as the destination.
(e) Specifying the name of a relay manager
When you directly enter the name of a relay manager or specify a route via a relay manager, be sure to specify the relay manager's host name, regardless of the node identification key.
(f) Using host IDs
If you select Host name as the node identification key, specify Use Network in Windows for resolving IP addresses on the ID Key for Operations page of the Software Distribution Manager Setup dialog box of Server Setup. If you select Use the system configuration of Software Distribution Manager on the ID Key for Operations page, you cannot send a request for job execution to a destination that is specified as indicated below, however, if The job starts is selected for When resolution of IP address fails option, the job is executed by polling from the destination:
- The destination is specified in Enter route of the Add Destination dialog box.
- The destination is specified by changing the route.
All Rights Reserved. Copyright (C) 2009, 2013, Hitachi, Ltd.
Copyright, patent, trademark, and other intellectual property rights related to the "TMEng.dll" file are owned exclusively by Trend Micro Incorporated.