When you enable hardware inventory for a site, SMS installs Hardware Inventory Agent on clients in the site and compiles the SMS_def.mof file (in the %windir%\MS\SMS\Clicomp\Hinv directory). The agent collects the first client hardware inventory approximately 15 minutes after it is installed.
Hardware Inventory Agent reads the SMS_def.mof file for the classes to inventory. The agent then queries the CIM Object Manager on 32-bit clients or DOS-based providers on 16-bit clients for the data. On 32-bit clients, the CIM Object Manager starts the appropriate provider for each class, retrieves the current value, and then transfers it to Hardware Inventory Client Agent. The agent then creates a complete inventory file (Hinvdat.hic for 32-bit clients, .raw for 16-bit clients) with this data.
Subsequent inventory cycles are initiated by the client service, which signals an event to start Hardware Inventory Agent according to the schedule specified for that site (by default, every 7 days). The agent then reads SMS_def.mof and queries the CIM Object Manager or the DOS-based providers. On 32-bit clients, the agent compares the inventory information with that of the most recently stored inventory. If there are any changes, the agent generates a delta inventory file (Hinvdat.hid) for 32-bit clients. The agent generates a complete inventory file (.raw) for 16-bit clients.
Hardware Inventory Agent copies the inventory file to the client Outbox, where SMS retrieves it and copies it to the client access point (CAP). SMS then moves all inventory files from the CAP to the site server. If the site server is not a primary site server, SMS passes the inventory files to the parent primary site server. On the primary site server, Data Loader processes the files and updates the information in the SMS site database.
Note If a hardware inventory file is corrupted, SMS copies the file to the SMS\Inboxes\Dataldr.box\Badmifs directory on the site server, and the hardware inventory process stops for that file. Corrupted inventory files are not processed by SMS.
If the primary site server is not the central site server, SMS forwards the inventory file to its parent. The parent processes the file and stores the information in its SMS site database. This process continues until the inventory data reaches the central site database.
After client inventory has been added to the SMS site database, you can use Resource Explorer to view hardware inventory for a client.
Related Topics
32-Bit Client Hardware Inventory Flow Diagram
About Hardware Inventory of 16-Bit Clients
Normal MIF Processing Flow Diagram
Collecting Hardware Inventory Overview