Join David M. Franklyn for an in-depth discussion in this video Hardware and software inventory, part of Microsoft System Center Configuration Manager Essential Training.
- [Instructor] Both the hardware and software inventories are run in the client. However, inventories are not run until we configure and prescribe them as policies. Once we can configure the inventories to collect the data we're looking for, we can assign them across the hierarchy or to particular collections of devices. There are a variety of uses for the inventory data to include such things as, building queries, building collections, creating detailed reports, maintaining corporate standards about who has what on their computers or not, troubleshooting client problems and also, if you're doing software inventory, you can collect files, although this can add to disk space that gets consumed in this case.
Hardware inventory data when refreshed, is put into a history area that can be accessed and checked and compared against the latest hardware inventory. This means, that we can have multiple versions of a hardware inventory, for example, in the beginning of a month, the person didn't have a CD ROM drive and later, two weeks later, they had one and two weeks later, we'll see a new inventory port where they had a DVD drive, so it will build a list of history of that hardware.
Now while we can collect software information, even details about the software such as version and publisher, configuration manager does not keep a history of software inventory data. In either case, do understand that the entirety of this data will consume database space. Inventories are normally scheduled to take place every 7 days, while you can decrease this length of time, you will wind up consuming more database space, it's not recommended to do so, unless you have very specific reasons.
In this demonstration, we'll create both a hardware and software inventory for our client one device and pull that information back up to the side servers.
- 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