Introduction

ZENworks Diagnostic Center (ZDC) performs a series of diagnostic tests on ZCM Primary Servers and determines the state of the Primary Servers and the Management zone. Currently, ZDC provides the following three verifiers:

ZENworks System Files Verifier: This verifier verifies the existence and consistency of critical system files required by ZENworks Configuration Management.

ZENworks Database Schema Verifier: This verifier validates the correctness of the schema (tables, indexes, database procedures, etc) of the database used by ZENworks Configuration Management.

ZENworks Content Verifier: This verifier validates the existence and consistency of the contents hosted on the current Primary Server.

Some of the verifiers compare the baseline data that is collected from known good deployments with the data of the deployment whose health has to be determined. The baseline data for each release of ZCM from version 10.2.0 onwards will be published by Novell.

Downloading and Extracting ZDC on the Primary Server

a) On the Primary Server, download the attached “zdc_0.5_beta.zip” and extract it to a temporary folder. Assume that you extracted the zip file to $ZDC_HOME
b) Depending upon the ZENworks 10 Configuration Management version that has been currently deployed on the Primary Server, download the appropriate ZDC file that contains the baseline data to the “$ZDC_HOME/data” folder.

Running ZDC

a) At Primary Server’s command prompt, go to the $ZDC_HOME folder.
b) Run the appropriate command:

On Windows:
'zdc.bat verify -b <path of the ZDC file>'

On Linux:
'bash zdc verify -b <path of the ZDC file>'

For example,
zdc.bat verify -b C:\zdc\data\zcm_10_2_0.zdc

ZDC will run the diagnostic tests and generate the reports in the HTML format at the “$ZDC_HOME/reports/<date_time>” folder. If any inconsistency is found, it will be indicated on the screen and the details will be available in the reports. To view the reports, open “index.html” from the report folder. The complete log of the diagnostic tests is stored in “$ZDC_HOME/logs/<date_time>.log”.

Note: This is the beta version of the tool. It might report false inconsistencies, especially for ZENworks system files, which may not necessarily indicate an actual problem.

Disclaimer: This content is not supported by Novell. 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.

I just downloaded the 10.2.1 version to install before upgrading to 10.2.2 however the MD5 checksum doesn’t match the one listed above (1c69ae67c7b04f60568e89e470101184). Instead I’m getting B389C723667719134CA41104F31EC08F. I’ve tried downloading on a couple of computers and clearing cache in case it got corrupted the first time but still getting B389C723667719134CA41104F31EC08F. Can anyone verify this?

The post has been updated with the ZDC version 0.6 and the baseline pattern file for ZCM 10.3.1.

The 10.3.1 pattern must be used with ZDC v 0.6.

Version 0.6 contains few bug fixes and hence can not be used with old pattern files. A new revised baseline pattern file for 10.3.0 is also posted which should be used to validate 10.3.0 zone with ZDC v 0.6.

There are two versions of ZDC tool available on this page, zdc_0.5_beta_20100113.zip and zdc_0.6_20100804.zip along with pattern files for each ZCM releases.

Version 0.5 has to be used with older ZDC pattern files (zdc_zcm_10.2.0.zip, zdc_zcm_10.2.1.zip and zdc_zcm_10.2.2.zip), while version 0.6 has to be used with newer patterns (zdc_zcm_10.3.0_zdcv0.6_0.zip and zdc_zcm_10.3.1_zdcv0.6.zip).