Job Management Partner 1/Software Distribution Administrator's Guide Volume 2
In the JOB_DESTINATION tag, you can specify the destination for a job. This tag can be used in the dcmcoll, dcminst, and dcmsusp commands.
The following shows the contents of specifiable parameters and the correspondence between parameters and command arguments:
Parameter |
Description |
Command argument |
directory_com#1, #2 |
Directory information (computer hierarchy) |
/dc computer-hierarchy |
directory_group#1, #2 |
Directory information (group hierarchy) |
/dg group-hierarchy |
directory_ou#1, #2 |
Directory information (organizational unit (OU) hierarchy) |
/do OU-hierarchy |
group |
Group name |
/g group-name |
host_name |
Host name |
/h host-name |
lower_clients |
Whether to specify all lower clients |
-- |
- Legend:
- --: Cannot be specified in a command argument.
- #1
- Cannot be used with the dcmsusp command.
- #2
- You cannot specify group or host_name together with directory_com, directory_group, or directory_ou. However, you can specify group and host_name together. You can also specify any combination of directory_com, directory_group, and directory_ou.
- Organization of this subsection
- (1) Format
- (2) Explanation
- (3) Notes
(1) Format
JOB_DESTINATION{
directory_com=computer-hierarchy
directory_group=group-hierarchy
directory_ou=OU-hierarchy
group=group-name
host_name=host-name
lower_clients=whether-to-specify-all-lower-clients
}
(2) Explanation
- directory_com=computer-hierarchy
Specify a computer hierarchy for the directory information acquired by the managing server. The following is an example of a computer hierarchy specification:
directory_com=CN=COM001,OU=Hitachi,DC=Domain001,DC=xx,DC=jp
To specify multiple computer hierarchies, use the semi-colon (;) to delimit the computer hierarchies. You can also code directory_com on multiple lines to specify multiple computer hierarchies. Combined, you can specify directory_com, directory_group, and directory_ou a maximum of 200 times.
- directory_group=group-hierarchy
Specify a group hierarchy for the directory information acquired by the managing server. The following is an example of a group hierarchy specification:
directory_group=XX=Group001,OU=Hitachi,DC=Domain001,DC=xx,DC=jp
To specify multiple group hierarchies, use the semi-colon (;) to delimit the group hierarchies. You can also code directory_group on multiple lines to specify multiple group hierarchies. Combined, you can specify directory_group, directory_com, and directory_ou a maximum of 200 times.
- directory_ou=OU-hierarchy
Specify an organizational unit (OU) hierarchy for the directory information acquired by the managing server. The following is an example of an OU hierarchy specification:
directory_ou=OU=Hitachi,DC=Domain001,DC=xx,DC=jp
To specify multiple organizational unit (OU) hierarchies, use the semi-colon (;) to delimit the OU hierarchies. You can also code directory_ou on multiple lines to specify multiple OU hierarchies. Combined, you can specify directory_ou, directory_com, and directory_group a maximum of 200 times.
- group=group-name
Specify the group name defined in the managing server in terms of a path beginning with the root directory. The following is an example of a group name specification:
group=\group1\group2\group
When specifying multiple groups, use semicolons (;) to separate the groups. You can also code group= in multiple lines to specify multiple group names. A total of 200 groups and host names can be specified.
- host_name=host-name
Specify the host name of the client defined in the managing server. When not using a host ID, you can specify the host name of the destination client to execute the job. When using a host ID, specify host ID or a path including the target client for the destination. (Do not specify only a host name.) Regardless of whether a host ID is used, when specifying a destination in terms of a path including the target client, begin with a \ and separate the relay systems with \ characters, shown as follows:
host_name=\Submanager1\Submanager2\Submanager3\host1
When specifying a destination path in a job specifying a relay system as a destination, specify the name of the relay system in both the path and the destination, shown as follows:
host_name=\Submanager1\Submanager1
When specifying multiple hosts, use semicolons (;) to separate the hosts. You can also code host_name= in multiple lines to specify multiple host names. A total of 200 host names and groups can be specified.
When managing clients in terms of IP addresses, you should specify IP addresses.
When specifying the Y parameter in the lower_clients parameter, specify the relay manager in the host_name parameter.
- lower_clients=whether-to-specify-all-lower-clients
Indicate either Y or N to specify whether all clients subordinate to the relay manager are to be the destination.
- Y
- This specifies that all clients specified in host_name subordinate to the managing server are to be destinations.
- Although more than one host can be specified in host_name, only relay managers can be specified. If you specify a group parameter, the group parameter is ignored.
- N
- Hosts specified in host_name and destination groups specified in group are to be destinations for the job.
If you do not specify this parameter, lower_clients=N is used by default.
This parameter is ignored in any command other than dcminst. Also, this parameter is ignored if it is specified in JP1/Software Distribution Client (relay system).
- The JOB_DESTINATION and JOB_DESTINATION_ID tags are mutually exclusive. In command-argument specifications, /h, /g, /dc, /dg, and /do cannot be specified together with /X.
- When you use host IDs and use ID keys as host names, you cannot use the host_name parameter in either of the following cases:
- In the ID Key for Operations page of the Software Distribution Manager Setup dialog box, Use Network in Windows is specified as the method used to resolve addresses, but address resolution fails.
- In the ID Key for Operations page of the Software Distribution Manager Setup dialog box, Use the system configuration of Software Distribution Manager is specified as the method used to resolve addresses.
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.