Customizing with NOIDMIF Files
NOIDMIF files must be stored in the following folder on Advanced Clients:
%Windir%\System32\CCM\Inventory\Noidmifs
NOIDMIF files must be stored in the following folder on Legacy Clients:
%Windir%\MS\SMS\Noidmifs
The safest method on both clients is to use the folder that the following registry subkey points to:
HKLM\Software\Microsoft\SMS\Client\Configuration\Client Properties\ NOIDMIF Directory
If the classes defined in the NOIDMIF files do not already exist on the primary site server, the site server's Inventory Data Loader creates the new classes on the existing architectures. After that, inventory for that client includes the new classes by processing the NOIDMIF file each time inventory is run. For example, if a NOIDMIF file creates a class called Asset Number, that custom MIF file causes the Inventory Data Loader to create the class Asset Number. Each time inventory is run, the Hardware Inventory Client Agent processes the NOIDMIF file again and replaces any values that have changed. If the NOIDMIF file is removed from the destination folder, all the classes and properties are deleted the next time hardware inventory runs, except from the history.
To customize a single client by using a NOIDMIF file
Prepare the NOIDMIF file by performing the steps listed in the "To create a NOIDMIF file to add the Wide World Asset Numbers class" procedure later in this section.
Place the NOIDMIF file in the NOIDMIF folder. For example, on a Legacy Client:
copy test.mif %windir%\MS\SMS\Noidmifs
The next time hardware inventory runs, the NOIDMIF file is included in the process, and the new properties and classes are added to the SMS site database.
For More Information
Did you find this information useful? Please send your suggestions and comments about the documentation to smsdocs@microsoft.com.