How to report on ZENworks Patch Management Patch Policy Compliance with ZENworks Reporting

How to report on ZENworks Patch Management Patch Policy Compliance with ZENworks Reporting

One of the most requested ZENworks Patch Management features we have is the ability to report on the patch policy compliance status. Basically you want to know which devices in the zone have all of the patches they are supposed to and which don't. While ZENworks Patch Management gives you an out of the box Compliance Dashlet that shows you the overall compliance status, it doesn't currently provide an easy way to do that based on a device's assigned policies.

This article is my solution to this request. It uses ZENworks Reporting to provide the requested capabilities using Ad Hoc Reporting topics. For more information on what a ZENworks Reporting Topic is I recommend you check out this article. In the past I had created another solution that described how to use JasperStudio to create similar reports, but with the flexibility of Topics I've decided this will provide a much better solution. So without further adieu, here's how you can use ZENworks Reporting to figure out your Patch Policy Compliance Status as shown in the screen shot below:

ComplianceDashboard.png

IMPORTANT: The SQL queries behind these topics are specifically crafted for Microsoft SQL Server, although they probably work with Sybase as well. If you take a look at the queries you will see they aren't pretty and they have lots of joins because it's the only way to get the data. As such, I do not recommend building or running these reports during peak business hours as there is a potential that you will cause utilization on the database servers to spike. Instead either build these and then schedule them to run in off-peak hours OR create a copy of the DB that gets sync'd regularly and have ZRS report against that instance.

Import the JRXML topics to your ZENworks Reporting Server

When you unzip the attachment to this article you will find two .jrxml files. These files are the Ad Hoc Topic definitions that need to be imported into your ZENworks Reporting Server in order for you to generate patch policy compliance reports. To import them you'll need to do the following:

  1. Download and install the latest version of JasperStudio from the ZENworks download page. This makes it much easier to trust the SSL certificate of your JasperServer when establishing the connection.
  2. Launch JasperStudio.
  3. Add your ZENworks Reporting Server to JasperStudio so that when you are done creating the topic you can easily push it to your ZENworks Reporting Server.
    1. In the Repository Explorer pane, right-click Servers and click Create JasperReports Server Connection.
    2. In the Name field, enter ZENworks Reporting
    3. In the URL field, enter the URL to your ZENworks Reporting server, including “/jasperserver-pro”
    4. In the User field, enter the name of a user with rights to create reports.
    5. In the Password field, enter the password for the user.
    6. Click Test Connection and verify the connection works.
    7. Click Finish.
  4. Add a Data Adapter so that JasperStudio can connect to your ZENworks database or whatever other Endpoint Management product backend you want to run reports against. (Remember legally you can only use ZENworks to report against the Endpoint Management family of products).
    1. In the Repository Explorer pane, right-click Data Adapters and click Create Data Adapter.
    2. Select Database JDBC Connection from the list, then click Next.
    3. Give the adapter a name, something like ZENworks JDBC.
    4. Pick the database driver type your ZENworks server is using.
    5. Enter the JDBC URL. This might take a little Googling to figure out. You can see the one I used for SQL. jsadapter-450x402.png
      Here's a Sybase example: jdbc:sybase:Tds:10.1.10.1:2638?ServiceName=zenworks_ZENGURU.
    6. Click Test to make sure you can connect.
    7. Once you've verified you can connect, click Finish to save the change.
  5. Now open up each of the JRXML files that are included with this solution. They are:
    • PatchCompliance.jrxml – This one gives you the big picture fields.
    • Patchpolicycompliancedetails.jrxml – This one dives into the details about each device and patch assigned to the patch policy.
  6. Repeat the following steps for each of the JRXML files to publish the reports and their input controls to your ZRS server.
    1. Select Project > Publish the file on JasperReports Server.
    2. Expand Ad Hoc Components and click Topics.
    3. Check the Create Report Unit checkbox.
    4. Enter a name that you want the Ad Hoc user to see when he attempts to create the report.
    5. Click Next.
    6. On the Datasource tab, select Datasource from Repository.
    7. Click ... and browse to the Data Sources and pick the ZENworks Reporting data source that corresponds to your ZENworks database, usually ZENworks Datasource.
    8. Click Finish to publish the report.

Build Patch Policy Compliance Reports and Dashboards

Now that you’ve got the topics imported you can build some reports and possibly even a dashboard. For your summary reports you’re probably going to want to create 1 custom field and 1 custom measure in the ad hoc editor. Here’s what they are:

Custom Measure: Compliance Percent
Field Definition: ("Patches Applied Count" / "Total Applicable Patches") * 100
Description: This gives you the % of compliance to the policy.

Custom Field: Compliance State
Field Definition: IF("Compliance Percent" == 100, 'Compliant', 'Not Compliant')
Description: This displays compliant if the device is at 100% else it displays non-compliant.

Below are a handful of videos that show you how you can build out reports and a dashboard that use these topics. Hope you find these useful!

Creating the custom fields and a compliance overview chart:

Creating a tabular report that shows compliance details:

Creating a tabular report with the details of patch policy per device:

Create a patch policy compliance dashboard:

Scheduling the execution of your reports and dashboard:

 

Attachments

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
11 of 11
Last update:
‎2019-06-11 22:42
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.