hp-support-head-portlet

Actions
Loading...
HP Customer Support - Knowledge Base

hp-contact-secondary-navigation-portlet

Actions
Loading...

hp-share-print-widget-portlet

Actions
Loading...
  • Information

    Fix and resolve Windows 10 update issue on HP Computer or Printer. Click here

hp-concentra-wrapper-portlet

Actions
Loading...

HP Web Jetadmin - Group Policies

Policies are applied to groups for the purpose of applying a settings action (or actions) onto a device when it becomes a member of the group or when it is removed from a group.

Many combinations of policy settings can be applied to a group. Multiples of the same policy types can be applied to groups as well. A short definition for each policy type follows:

  • Enable data collection policy: If you have already defined a reports data collection template, this policy will automatically apply that template to devices when they are added to the group, when they are removed from the group, or both.

  • Subscribe to alerts or unsubscribe to alerts policy: If you have already defined an alert subscription template, this policy will automatically apply that template to devices when they are added to the group, when they are removed from the group, or both.

  • Configure devices policy: If you have already defined a device configuration template, this policy will automatically apply that template to devices when they are added to the group, when they are removed from the group, or both.

  • Add or remove devices to supply group policy: If you have already defined a supply group, this policy will automatically add devices to that supply group when they are added to the group, when they are removed from the group, or both.

Example for Group Policies

Learn more about this topic.

Following is a simple example of applying a configuration template to a group:

  • An administrator is named Pat.

  • Pat has an HP Web Jetadmin group named “Pat’s Devices”.

  • One policy setting on the group is a configuration template that sets the System Contact to “Pat” and the Device Location to “Building 3”.

Change the Order in which HP Web Jetadmin Applies Policies

You can specify the order in which HP Web Jetadmin applies policies to devices that are added or removed from a device group. When HP Web Jetadmin finishes applying one policy, it begins applying the next policy in the list.

If a device does not respond while HP Web Jetadmin is applying a policy, the policy execution task never completes. In this case, HP Web Jetadmin does not apply the remaining policies in the list to the device. To avoid this situation, HP Web Jetadmin provides a timeout setting with a default value of 450 minutes for each policy execution task. If a policy execution task does not complete within this default timeout period, HP Web Jetadmin begins executing the next policy in the list.

You can increase or decrease the timeout value, depending on the types of policies you define for device groups and the number of devices to which HP Web Jetadmin applies these policies during an execution phase. If you only define policies that do not take a long time to execute, such as installing solutions or fonts, or only add a few devices to a device group at one time, you can decrease the timeout value. If you define policies that take a long time to execute, such as firmware upgrades, or add a large number of devices to a device group at one time, you can increase the timeout value.

For example, assume that you define a firmware upgrade policy and a subscribe to alerts policy for a device group, and specify that the firmware upgrade policy is applied first and the subscribe to alerts policy is applied second. If you add 100 devices to this device group, HP Web Jetadmin begins executing the firmware upgrade task for all the devices. If HP Web Jetadmin does not finish upgrading the firmware on all 100 devices within 450 minutes, it continues executing the firmware upgrade task on the remaining devices and begins executing the subscribe to alerts task for all the devices. HP Web Jetadmin is now executing both policy tasks at the same time. In this case, it is possible for HP Web Jetadmin to execute the subscribe to alerts policy on a device before it executes the firmware upgrade policy on that device. To ensure that the policies are applied to devices in the order you specified, you can increase the timeout value to allow additional time for HP Web Jetadmin to complete the firmware upgrade task.

To change the default timeout value, perform the following steps:

  1. Use Notepad or a similar editor to open the PolicyOrdering.config.xml file. This file is available in the following directory on the HP Web Jetadmin server:

    C:\Windows\ServiceProfiles\NetworkService\AppData\Local\HP Inc\HPWebJetadmin\WjaService\config

  2. Find the following entry:

                      <ipmc:configuration xmlns:ipmc="www.hp.com/schemas/imaging/ipmc/
    config/2004/02/24">
     <property name="PolicyExecutionTaskTimeout">
      <type>HP.Imaging.Wjp.Sdk.Core.Framework.ConfigurationItemString
      </type>
      <value>450</value>
     </property>
    </ipmc:configuration>
                    
  3. Change the <value> parameter to the number of minutes that are appropriate for the types of policy execution tasks you define and the number of devices you add to a device group at one time.


hp-feedback-input-portlet

Actions
Loading...

hp-feedback-banner-portlet

Actions
Loading...

hp-country-locator-portlet

Actions
Loading...
Country/Region: Flag United States

hp-detect-load-my-device-portlet

Actions
Loading...