Join David M. Franklyn for an in-depth discussion in this video Gathering hardware and software inventory, part of Microsoft System Center Configuration Manager Essential Training.
- [Instructor] So in this demonstration we're going to go ahead and set up a hardware inventory, and then a software inventory for our CLIENT1 computer. So this starts out by us going to the CENTRAL CFG1 computer, and in the Administration workspace we want to go to the Client Settings node in the console tree, double click that. And the just double click Client Settings, Default Client Settings or you can go to Properties. And you'll note that there's a Hardware Inventory page or tab within the pages associated with this, in it's console tree we click that.
And we can see that the Hardware Inventory by default is actually enabled. So there it is, it's enabled, we can schedule it, and it's scheduled to run every seven days. Again if you make this a shorter period, you'll be collecting more data and using more disc space, so be careful there. So we can say OK to that, and then OK to the Default Client Settings. And now let's go to our client computer, CLIENT1. Now we are in CLIENT1, and let's go over to the Control Panel.
So we'll right click the Start Menu, choose Control Panel, in the Control Panel, the System and Security node. We'll scroll down and we see Configuration Manager. So click on that. Now a couple of things in the Configuration Manager Properties that we have. First, the components. And as you see the Hardware Inventory Agent in enabled. In fact if we look and find the Software Inventory Agent that too is enabled, because those are defaults that are set up there. If we go to the Actions pane, then we'll see the Hardware Inventory Cycle.
Now one note about this, there have been instances where it just didn't appear. In other words the Hardware Inventory Cycle wasn't there. And so what you might wish to do is go back to your Configuration Manager Console and actually change that YES to collect hardware inventory in the default Client Settings to NO and then save it. Come back here and refresh the Machine Policy & Evaluation Cycle as I'm doing now. So select it and say Run Now, and then say OK close it, and then come back and you should see the component now showing up as disabled.
We didn't of course turn off the policy on CENTRAL CFG1. So that's not going to happen, but that's how you can fix that. Any case we're going back to Actions here, we're going to select the Hardware Inventory Cycle in Actions and say Run Now. And then OK. And then OK again. And let's now return to the Configuration Manager Console on North AM-CFG2. So one reason why we started this out in CENTRAL, we can manage a lot stuff in CENTRAL.
It's almost like a central console by doing it on the Configuration Manager Console on that central administration site. But we can still set things up for all the clients that are part of our primary site. In this case it's the NA1 primary site. So what we want to do now because the client is set to first report its hardware information up to its primary site, once that's done it's going to propagate up to the central site. So it could well be that it's not yet there at the central site.
So let's see if we can see our Hardware Inventory data that we just started on the North America 1 primary site. So in this case we're going to go to Assets and Compliance, and we're going to select our client computer, CLIENT1 within the Devices node. And now we're going to go to our Start button up here, to start utilities. And one of the utilities we have is the Resource Explorer. And this will show us our hardware inventory.
So let's go ahead and click Resource Explorer, and notice that we have Hardware and Hardware History. If I expand Hardware, there it is. So this is the inventory that just collected. We now have all the data. Let's go ahead and close that. 'Cause we only have one, let's go to the CENTRAL-CFG1 central administration site. And we're now at the CENTRAL-CFG1 site. Let's go to Assets and Compliance and then Devices. Let's take our device, highlight it in the Details pane, go to Start, go to Resource Explorer, and check to see whether we have a Hardware Inventory.
And we do. Now we don't have Hardware History this time, and the reason for that is simply we haven't done more than one hardware inventory. But if we were to do more of these and as the weeks go on, and we run it every week, then we'll see Hardware History data. So now we're going to go and set up a software inventory, and that's almost the same thing. We simply go into Administration, go then to Default Client Settings, in the Client Settings node.
Go to the Properties. Go to now Software Inventory, and make sure it's running. And as we see here it already is set to run, it's scheduled to go every seven days, we're not going to collect any files, we're just going to say OK to that. And then we're going to go back to our client and run the Software Inventory Cycle. And now back in the Client where we still have the Control Panel System and Security up, we can go back to the Configuration Manager applet.
And again as we saw earlier, we have the Software Inventory Agent enabled. And in Actions you will see the Software Inventory Cycle action. So let's go ahead and run that now. We'll say Run Now, and then OK. And then OK. Now unlike the hardware inventory, which populates the database pretty quickly for any client, it sometimes takes a long time for the software inventory data to appear. Let's go now back to North AM CFG2, and see if there's anything for us.
And here we are back now in North AM CFG2, right where we left off. So we're in the Assets and Compliance workspace. In the Devices node we've selected our device. And I can tell you it's only been a few seconds since we did this, so we shouldn't expect to see any information now. But let's go to the Start button or the Start icon in the ribbon, click on it and click Resource Explorer. And if we expand then, we have our Hardware Inventory of course. The software side we'll look for their four sub nodes to it.
Collected Files, we see nothing here. File Details, we see nothing here. The one that you should perhaps see something would be Last Software Scan to give you a date time, and then we see nothing in Product Details. So it will be awhile before we have data in this. And since we're going to move right into the next chapter, which means we're going to look at the replicated data that's exchanged from the different databases on the different sites, especially the central site.
We're going to end the demonstration at this time, and we'll look at it at that point. Give it some time to run.
- Planning and deploying a standalone primary site
- Ensuring domain and site server prerequisites
- Planning and expanding a standalone primary site
- Planning and deploying a multiple-site hierarchy
- Planning resource discovery and client deployment
- Managing content and replicating data in Configuration Manager
- Configuring Internet and cloud-based client management
- Advanced monitoring
- Upgrading to Configuration Manager current branch