Re: Extending hardware information using MIF files

I suggest that you loop in your micrsoft pss engineer on this, in case they
have a quick solution to the problem.
Meantime, here are a few links:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/smssdk03/hh/sms/usingsms_FormatChanges.asp

http://support.microsoft.com/default.aspx?scid=kb;en-us;202078

http://support.microsoft.com/default.aspx?scid=kb;en-us;199229



--
Thanks,
Joseph Calabig

This posting is provided "AS IS" with no warranties, and confers no rights.

"Dorel Sturm" <dodo@xxxxxxxxxxxxxxxxxxx> wrote in message
news:djngip$icj$1@xxxxxxxxxxxxxxxxxxx
> Hi,
>
> I'm using IDMIFs because I use a computer which is non-client and I add
> new information into SMS. The MIF file I create is copied directly to the
> CAP directory (usually ...CAP_<site_name>\inventry.box). Before I copy the
> MIF file there I create a "new computer" in SMS using DDRNew,
> DDRAddString, etc. functions (and the DDR file created with DDRWrite is
> copied into ...CAP_<site_name?\ddr.box directory).
>
> I tried different ways for MIF header and none worked as I expected. E.g.
> this one will be rejected by SMS as bad MIF file:
>
> //AgentID<MyMagicAgent1>
> //Architecture<System>
> //UniqueID<123456>
> //KeyAttribute<NetBIOS Name><MyComputerName>
> //ClientType<1>
>
> What I really need is the //ResyncAgent<1>. Until now the only stuff that
> seems to work is //FullResync<1>.
> Without a header, the MIF file is almost always rejected by SMS as either
> bad MIF file or orphaned MIF file.
>
> Any ideas?
>
> Be
>
> "Jeff Gilbert" <jeff.gilbert@xxxxxxxxxxx> wrote in message
> news:%23ml0SqZ2FHA.620@xxxxxxxxxxxxxxxxxxxxxxx
>> If you're using a NOIDMIF then you don't have to put in the header
>> information--sms will do it for you since it appears you're wanting to
>> run this on a computer system that is an SMS client you can just use a
>> NOIDMIF--IDMIFs for non-client systems are a different story. If the
>> NOIDMIF will work for you, then my first advice would be to try it
>> without the header information and see how that goes.
>>
>> Jeff Gilbert, MOF Master
>> SMS Expert
>>
>> "Dorel Sturm" <dodo@xxxxxxxxxxxxxxxxxxx> wrote in message
>> news:djlghn$o45$1@xxxxxxxxxxxxxxxxxxx
>>> Hi There,
>>>
>>> I'm using here MIF files to extend the hardware information for clients.
>>> I'm able to add new "computers" and new groups. A typical MIF file that
>>> I use has this format:
>>>
>>> //AgentID<MyMagicAgent1>
>>> //Architecture<System>
>>> //UniqueID<123456>
>>> //ResyncAgent<1>
>>>
>>> Start Component
>>> Name = "Workstation"
>>> Start Group
>>> Name = "System"
>>> ID = 1
>>> Class = "System"
>>> Pragma = "SMS:ADD"
>>> Key = 1,2
>>> Start Attribute Name = "SMSID" ID = 1 Type = String Value = "123456"
>>> End Attribute
>>> Start Attribute Name = "Name" ID = 2 Type = String Value =
>>> "MyComputer" End Attribute
>>> Start Attribute Name = "SystemType" ID = 3 Type = String Value =
>>> "SpecialComputer" End Attribute
>>> End Group
>>> Start Group
>>> Name = "Computer System"
>>> ID = 3
>>> Class = "Computer System"
>>> Pragma = "SMS:UPDATE"
>>> Key = 3
>>> Start Attribute Name = "Number Of Processors" ID = 1 Type = Integer
>>> Value = 5 End Attribute
>>> Start Attribute Name = "Description" ID = 2 Type = String Value =
>>> "Super Computer" End Attribute
>>> Start Attribute Name = "Name" ID = 3 Type = String Value =
>>> "MyComputer" End Attribute
>>> Start Attribute Name = "Status" ID = 4 Type = String Value = "OK" End
>>> Attribute
>>> End Group
>>> End Component
>>>
>>>
>>> First time I use the MIF file the information is added correctly in the
>>> SMS database.
>>> Now I create again the MIF file and I want to "update" the information
>>> and create a Hardware History.
>>> Everything works OK for the groups that are in all MIF files and have
>>> "Pragma = "SMS:UPDATE"". However in the new MIF file some groups are
>>> missing and they should be removed from the SMS database. I have
>>> something like this:
>>>
>>> - first MIF file
>>> Group Name A
>>> Class AA
>>> Group Name B
>>> Class AA
>>>
>>> (both groups are added into the SMS database)
>>>
>>> - next MIF file
>>> Group Name B
>>> Class AA
>>>
>>> (Group Name A should be deleted from the SMS database)
>>>
>>> To do this I tried these:
>>>
>>> 1) Added Pragma = "SMS:DELETE" for "Group Name A" in the second MIF
>>> file. However Group Name A is not deleted from the SMS database. Seems
>>> that "Pragma = "SMS:DELETE"" is ignored......
>>>
>>> 2) The documentation says that "//ResyncAgent<1>" in the header of the
>>> MIF file will force SMS to replace the data generated for this
>>> architecture (with ID "123456") for this agent ("MyMagicAgent1") with
>>> the information from this MIF file. However this is not working, the
>>> "Group Name A" is missing from the second MIF file and is not deleted
>>> from the SMS database.
>>>
>>> Any ideas how to delete the group from the SMS database using MIF files?
>>>
>>> What is really working as expected is "//FullResync<1>" but this will
>>> replace all the data for this architecture (with ID "123456") with the
>>> one from this MIF file. I cannot use this because I have multiple agents
>>> (MyMagicAgent1, MyMagicAgent2,....) that generate MIF files for the same
>>> "computer" with the ID "123456".
>>>
>>> Thanks for your support.
>>>
>>> --------------------------------------------------------------------------
>>> Dorel Sturm
>>> Germany
>>>
>>>
>>
>>
>
>


.

Relevant Pages

  • Extending hardware information using MIF files
    ... I'm using here MIF files to extend the hardware information for clients. ... Class = "Computer System" ... First time I use the MIF file the information is added correctly in the SMS ... and they should be removed from the SMS database. ...
    (microsoft.public.sms.inventory)
  • Re: Extending hardware information using MIF files
    ... The MIF file I create is copied directly to the CAP ... file there I create a "new computer" in SMS using DDRNew, DDRAddString, etc. ... I tried different ways for MIF header and none worked as I expected. ... >> missing and they should be removed from the SMS database. ...
    (microsoft.public.sms.inventory)
Loading