Novell Cool Solutions

Populating data in ZAM



By:

January 24, 2007 2:35 am

Reads:4,470

Comments:2

Score:Unrated

Print/PDF

Every time I work on ZENworks Asset Management (ZAM), one of the first things that is requested is “How can I get more meaningful information about my business into the system?” Out-of-the-box reports can be grouped by items such as Domain, Default Gateway and Inventory Type, but customers normally want to see their Sites and Departments in reports.

Well, one option is to enter the data manually into the database using the ZAM Manager. This is not a popular approach for obvious reasons. 😀

Another approach is to use the Collection Editor to display during a scan and ask the user to provide the information. Again this method is not popular as administrators tend to avoid using pop-ups on their users and users aren’t generally trusted enough to provide accurate data. So how can we automate this with ZENworks?

The Collection Editor can be configured to run silently to populate database fields with registry values stored on the device being scanned. In the example below, I am using two registry keys to populate the Site and Department fields.
Collection Editor

Another important point to note; if you set the “Run Collection Editor” option to “Never” as shown below, the Collection Editor will still run silently to collect the values.
Running the Collection Editor

Now all I need to do is ensure that the registry keys exist on each and every device I want to scan. If your eDirectory is structured geographically and you are running ZENworks Desktop Management, you can create simple Application Objects to deploy the registry keys. If a workstation object moves to a new site, the local application will run and ZAM will update itself during the next scan.

I was at a customer last week that stores department, site and owner in the registry for every device as part of their standard build process. ZAM was able to pick up these values automatically allowing the customer to group reports exactly how they wanted to.

Do you run site based reports? How do you maintain your fields in your ZAM database?

Written at: Frankfurt, Germany

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.
Loading...Loading...

Categories: Uncategorized

2

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.

2 Comments

  1. By:Jared

    Usually registry keys, although I am thinking of using IDM for one customer.
    A while back, I wrote a Cool Solution about this very topic.
    https://www.novell.com/coolsolutions/feature/18296.html

  2. By:Andy Philp

    Excellent document, didn’t see that. I’ve been doing this for quite a while now, it’s a simple process but very effective. Keep us posted on the IDM front.

Comment

RSS