Subtitles of the Movie

Well, now that we've seen how to run a canned report and how to do Data Export from the Inventory Database there is one final aspect of Workstation Inventory Reporting that we need to go over. So we'll go back to the Indian Springs network, we'll click on Tools, and ZENworks Inventory, and choose Inventory Query. After a few seconds of connecting to the database we are presented with this Inventory Query screen that we saw when we went over how to do a Data Export from the Inventory Database. However, this particular Inventory Query works a little differently than it did in the previous incarnation of it. We'll set a criteria; in this case we'll choose any machines that have Greater Than 128 megs of RAM, which should be most every machine on the network, and we'll add an And query Ð any machine that has Greater than 128 megs of RAM And whose Windows version Does Not Match XP, or in this case, does not have the string XP in it. This will find any machines on the network that have more than 128 megs of RAM, yet are not running Windows XP. With my luck there probably won't be any on here, but let's go ahead and hit Find. And lo and behold, there are actually some machines that have Greater Than 128 megs and are not running Windows XP, or so we think. For example, if we look at this Physics Print machine by double-clicking on the Inventory Query Results Pane, if we go look at Software and look at Operating Systems, we'll see that the version does not contain XP, but this is not where XP would be at. We would look for XP in the Caption, which is the name of the Operating System. I bring this out to be cautious that you query on the correct fields in your Inventory Query. In our case we returned every machine on the network because there are no machines that have XP in the Version field; they're all in the Caption. So, let's redo our Query to say: Caption does not contain XP, and click Find. In our case, we're in luck. There are no machines that are not running XP that have more than 128 megs of RAM. And last but not least, let's show you how to verify that your ZENworks Inventory Scan is actually taking place. To do this we can click on Tools, ZENworks Inventory, and choose Workstation Scan Log. Now what happens is this. Every time Inventory Scanning takes place on a workstation the workstation will report back either success or failure for the Inventory Scan that was kicked off at whatever time specified in the Inventory Scanning Schedule. This little utility is just a quick way to scan those result logs and tell whether or not your scan is taking place. In our case we'll choose Error or Warning and Information, and we're going to get back a whole lot of stuff. Normally you would not choose Information. You're really only interested in Error and Warning, so we'll choose that, and we'll hit OK, and you'll see that there are lots of events, I'll Sort them by the Time of Scan. In this case we'll look at this Information Event: Unable to register to DMI service layer. That simply means that this particular workstation is not running a DMI infrastructure and so the Inventory Scanner can't talk to it because it's not there. We'll probably have the same error on this machine Ð Unable to register to DMI service layer. You'll also look at this Storer Event and it'll tell you: 200, the Store has updated the database, meaning that the inventory ran like it was supposed to and I put the information in the database. If we look at some of these errors here, for example: Unable to launch inventory scanner, that may mean that this ZENworks Agent on this workstation needs to be updated. In this case it is one of the machines in the Development Office, and to be honest, the thing that fixes these errors most of the time is simply reinstalling the Agent. So now we've gone over a lot of the functions of ZENworks Workstation Inventory Reporting, and this concludes our discussion on Reporting on Workstation Inventory.