Cool Solutions

Configure Multiple and Multilevel Inventory Scan Schedules Using the Bundles Feature


October 6, 2009 12:06 pm





Author: Ravella Raghunadh

In an organization, administrators need to maintain different inventory scan schedules based on the device hierarchy or device categories. Thus, the administrators prefer the following use cases:

  1. Different scan schedules for servers and workstations.
  2. Different scan schedules for different folders and device groups based on the user working hours and geographic locations.
  3. Multiple scan schedules for different devices in a Management Zone.

Currently, ZENworks Configuration Management allows you to configure a single inventory scan schedule for the devices either at the zone or device levels. However, using the Bundles features of ZENworks Configuration Management, you can still configure multiple and multilevel inventory schedules for device folders, device (server/workstation) groups and dynamic device groups. This enables an enterprise zone with large-scale device deployment to schedule device inventory scan in groups and reduce the load on their Primary Server.

This article provides information on how to configure inventory scan schedules based on the above use cases preferred by the administrators.

Creating Device Groups and Folders:

Steps to be performed:

  1. Categorize the devices to be organized based on the architecture, geographic locations, and user working hours.
  2. Prepare the hierarchy of the devices.
  3. Log in to ZENworks Control Center.
  4. Create server or workstation groups and folders.
  5. For more information on creating folders and groups, see the Novell ZENworks 10 Configuration Management Documentation link:

Configuring the Inventory Scan Bundle:

Steps to be performed:

  1. Login to ZENworks Control Center.
  2. Create a new Directive Bundle.
  3. For more information on creating directive bundles, see the Novell ZENworks 10 Configuration Management Documentation link:

  4. Add a Run Script action to the bundle.

    Figure 1 – Add Actions window – Run Script action selection

    Click to view.

    For more information on adding the Run Script action, see:

  5. Select Define Your Own Script to run the script.
  6. Type the following command as the script content:
    zac inv scannow
  7. Proceed to finish the Bundle Creation Wizard.

Assigning a Bundle to the Device Groups:

Steps to be performed:

  1. Decide the scan schedules to be configured for all Device groups or Device folders as per your business requirement.
  2. Login to ZENworks Control Center.
  3. Select the directive bundle created in the section “Configuring the Inventory Scan Bundle”.
  4. Assign a bundle to ZENworks Configuration Management devices (workstations/servers), device groups, device dynamic groups and device folders based on the hierarchy decided earlier.

    For more information on assigning bundles to the devices and users, see
  5. Configure the bundle launch schedule to match with the inventory scan schedule decided in Step 1.
  6. Assign a bundle to all the device groups and folders with a different launch schedule.
  7. Refresh all the devices in the Management Zone.
  8. In the Relationships tab, verify the bundle assignment details and launch schedule (which works Inventory scan schedule for the device category assigned).

Figure 2 – Bundle Relationships

Click to view.

Figure 3 – Bundle Assignment Details – Launch Schedule ~ Inventory Scan Schedule

Click to view.

Note: For easy reference, create different bundles for each device category or inventory scan schedule and provide a suitable name for each of them. For example: INV_Scan_XPDevices_Daily.

I would like to thank Binika Kumar for reviewing this Appnote and providing valuable feedback.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.