Subtitles of the Movie

The next Object that we see in the list is the Inventory Database on the same Database Server, obviously, it's the only Server in our lab. If we look at the properties of this it is identical to the Desktop Management Database. This is because the Database Objects in ConsoleOne are generic database objects that can be used for whatever kind of database you happen to install and use with ZDM7. Since the settings are the same I won't bore you with going through all of them again. And the third object we'll look at is the Inventory Service. We'll right-click this and choose Properties. This policy package determines exactly how Workstation Inventory will take place. You can change the type of server from Standalone to Root, Intermediate, or Leaf and again, a lot of these settings we're glossing over for now and we'll get more in-depth with them when we cover this particular section in the Title. You can set the Scan Directory Path where the scan input files get written to by the Inventory Service on the workstations. If you have more than one inventory server you can set the schedule when the inventory is rolled up across the various inventory servers; this way you're not replicating inventory information across slow RAM links during the middle of the day when your branch offices are trying to conduct business. You can roll those changes up at night, which means your data is a little stale but it supports the business flow better. On this tab you can get a status on the Inventory Roll-up; again, since we have a single server configuration there is no roll-up and so there's no information on the screen. You can also get a report on the server itself. You'll notice that our Server has some errors on it. If you double-click one of these lines it gives you the date and time and it gives you the message: The database location policy is not configured. Basically that just means that we've not defined the policy package for the Inventory Service so that the Inventory Service knows where to write its inventory information. It sees an inventory database out there, but it doesn't know am I supposed to write to this one or this one or this one. The database location policy tells this particular inventory service you write to this database. And again, we'll set up that policy when we discuss Workstation Inventory. The Inventory Service Object is also where you would change the software inventory configuration. You can set up File Software Mapping, Multiple Software Version Detection, Disk Usage, et cetera. This is so you only collect and report on the information that is relevant to your software deployment. So, we'll Cancel out of this. And the last Service we'll look at is the Wake-on-Lan Service. I click and choose Properties. This service is very simple. It just wants to know when does this service kick off. Obviously Wake-on-Lan is something you would use if you wanted to do unattended imaging of workstations. What a lot of organizations do is set an application object to run at a certain time after hours, say, ten-thirty p.m. that forcibly shuts down all of the workstations on the segment that's going to be re-imaged. Again, computer labs in an educational environment is the most common use for this. You'll then have a Wake-on-Lan service that boots the machine up at 11 o'clock p.m. for example, and since it is doing an initial boot it will grab the pre-boot execution environment, or PXE information from the PXE Server, and pull down an image based upon the machine type. Again, we'll go through all of that elsewhere in the Title. I just wanted to show you the Wake-on-Lan service in all of its glory here. So, we'll hit Cancel. And this will conclude our discussion of ZENworks Objects in eDirectory.