MIF is part of the Desktop Management industry standard. The MIF standard defines how text files can be used to represent computer management information. Because MIF is an industry standard, programs that store management data in MIF files do not need to be SMS-specific. However, SMS can collect the MIFs and store them in the SMS site database, where you can use their data in the same ways that you use default SMS inventory data.
You can also create MIF files by using a text editor. When you have defined a MIF file that stores the data you require, you can use that file as a template so that similar data is defined in the same manner. For example, when you are setting up a new computer, you can copy the template file to the new computer, edit the data contained within the file to reflect the new computer, and then save the new file. SMS collects the file and stores the information in the SMS site database, along with the other inventory data for that computer.
Your MIF file might contain information about a user's phone number, job title, office number, and similar details that SMS cannot automatically determine.
For SMS, standard MIF files are called NOIDMIF files. These files do not contain a unique identifier for the data. They have no ID. SMS automatically associates NOIDMIF file data with the computer that the NOIDMIF files are collected from.
SMS also supports IDMIF MIF files. These files do contain a unique ID, and are not associated with the computer they are collected from. IDMIF files can be used to collect inventory data about devices that are in the vicinity of a computer, but not actually associated with it. For example, a shared network printer, video cassette recorder, photocopier, or similar equipment is not associated with any specific computer, but you might want to record data about it for asset management purposes. This data is stored in separate tables in the SMS site database.
IDMIF extensions (or custom DDRs) can also be used to create new tables in the SMS site database that you might need for reporting purposes. For example, you might have asset management data that is not strongly tied to individual computers. This data is not appropriate for NOIDMIF files or MOF extensions, but you want to join it with SMS data for reporting purposes.
Removing IDMIF extensions from clients does not cause the associated data to be removed from the SMS site servers.
For More Information
Did you find this information useful? Please send your suggestions and comments about the documentation to firstname.lastname@example.org.