Management Information Format (MIF) files enable you to extend SMS inventory by adding custom objects or custom groups to hardware inventory. SMS supports two types of custom MIF files, as described in the following table.
| Type of MIF | Used for |
|---|---|
| NOIDMIF | Client-specific custom groups in hardware inventory. Clients can be grouped by attributes such as asset number and physical location. NOIDMIF files are processed on clients. |
| IDMIF | Custom architectures or attribute classes not specific to a client, such as user names and job titles. IDMIF files can be processed on clients or on site systems. |
If you use a custom tool to generate a MIF file, make sure that your tool places the MIF files on clients as follows:
Hardware Inventory Client Agent searches both locations during an inventory cycle and verifies that:
Any MIF files that do not meet these criteria are placed in the %windir%\MS\SMS\Noidmifs\Badmifs directory on the client.
Hardware Inventory Client Agent then appends any NOIDMIFs to the end of the collected inventory file (.hic, .hid, or .raw). On the site server, Inventory Data Loader updates the SMS site database with the information from the MIF file when it processes the hardware inventory file. IDMIFS are sent to the site server for processing.
A custom group added with NOIDMIFs appears as a class under Hardware in Resource Explorer. A custom architecture added with an IDMIF appears in the SMS Administrator console (if it is in the System architecture) and can be used in queries. However, you cannot use custom architectures in collection membership rules.
Note If the Hardware Inventory Client Agent is not installed on clients, the custom inventory files will not be propagated to the site server.
Related Topics
Normal MIF Processing Flow Diagram
How SMS Collects Hardware Inventory
Extending the Inventory Overview
Collecting Hardware Inventory Overview