13.5 dcmgpmnt.exe (applying policies to all hosts in a host group)
This section describes the dcmgpmnt command, which applies policies to all the hosts in a host group.
Function
This command connects to the managing server (JP1/IT Desktop Management 2 - Manager) on the local host, and adds all the registered hosts to a host group according to created policies.
Format
dcmgpmnt.exe [processing-key] [/LC {ON|OFF}]
Arguments
-
processing-key
This argument specifies the type of policy to be applied to all hosts in a host group. Specify one or more processing keys among those listed below immediately after the command name. When this argument is omitted, specification of ALLGROUP is assumed.
-
ALLGROUP
When the processing key is ALLGROUP, this command applies all policies to all hosts in a host group.
-
IPSCOPE
When the processing key is IPSCOPE, this command applies the policy whose type is IP address to all hosts in a host group.
-
OSTYPE
When the processing key is OSTYPE, this command applies the policy whose type is OS type to all hosts in a host group.
-
HWASSETFIELD
When the processing key is HWASSETFIELD, this command applies the policy whose type is Custom Fields (Hardware Assets) to all hosts in a host group.
-
DEPARTMENT
When the processing key is DEPARTMENT, this command applies the policy whose type is department to all hosts in a host group.
-
LOCATION
When the processing key is LOCATION, this command applies the policy whose type is location to all hosts in a host group.
You can specify IPSCOPE, OSTYPE, HWASSETFIELD, DEPARTMENT, and LOCATION in any combination. When you specify a combination of processing keys, separate them by a space. Note that specifying processing keys in one of the following ways results in an error indicated by the return code 2.
-
Specifying ALLGROUP together with any other processing key
-
Specifying the same processing key multiple times
-
-
/LC
In the argument /LC, write ON or OFF to specify whether to continue command processing even if you log off from Windows while executing this command as a background service by using the Task Scheduler or JP1/AJS.
-
ON
Continues command processing even when you log off from Windows.
-
OFF
Forcibly ends command processing when you log off from Windows.
This argument is effective when this command is executed from a service on the following OS:
-
Windows Server 2003
When you enter this command from the command prompt, this command is executed as a foreground program. Therefore, in such cases, do not specify /LC ON.
You can also use a registry to set whether to continue command processing even if you log off from Windows.
Note that the command operation differs depending on the combination of the specification of the argument /LC and the setting in the registry. For details, see 13.20 Command operation at logoff according to registry setting and logoff option.
-
Return codes
The following table lists the return codes that are output when the dcmgpmnt command is executed:
Code |
Meaning |
Action to be taken |
---|---|---|
0 |
Processing ended normally, or no target host was found. |
None |
2 |
An invalid value was set in a command argument. |
Check the values set in command arguments. |
3 |
Connection to the database failed. |
Check database settings in the setup of the managing server. |
5 |
Connection to the JP1/IT Desktop Management 2 service failed. |
Check whether the service of JP1/IT Desktop Management 2 - Manager has started. |
12 |
Restoration of one or more archive files failed. |
Reference the event log. |
15 |
Another process is updating the database. |
Wait awhile, and then re-execute the command, or check the process that is updating the database. |
Example
The following example shows use of this command to apply the policies whose types areIP address and OS type to the hosts in a host group.
dcmgpmnt.exe IPSCOPE OSTYPE
Notes
-
The time required for the batch maintenance of a host group increases in proportion to the number of hosts and the number of policies.
-
While batch maintenance is being executed, host group automatic maintenance (executed when device information is updated) does not work. Therefore, we recommend that you execute host group batch maintenance during a period when less device information is updated.