SMS MOF file for Win32_PnPSignedDriver

Author
bhunter
Starting Member
  • Total Posts : 16
  • Scores: 0
  • Reward points: 27390
  • Joined: 2006/05/24 05:14:04
  • Status: offline
2008/05/14 12:11:36 (permalink)
0

SMS MOF file for Win32_PnPSignedDriver

Hello,
I have updated our MOF file to include the inventory of the Win32_PnPSignedDriver class.  Unfortunately, I'm getting the following error in the client's InventoryAgent.log file:
 

Failed to add an instance of class Win32_PnPSignedDriver to historical store: 80041002

 
 
I had started inventory every column, but knocked it down to only two and I still get the problem.
 
Here is the portion of code from the MOF file:

 [ SMS_Report     (TRUE),
  SMS_Group_Name ("PnP Signed Driver"),
  SMS_Class_ID   ("MICROSOFT|PNP_SIGNED_DRIVER|1.0") ]
class Win32_PnPSignedDriver : SMS_Class_Template
{
    [SMS_Report (TRUE), key ] 
        string     Description;
    [SMS_Report (TRUE)      ] 
        string     DriverVersion;
};
#1

9 Replies Related Threads

    phaustein
    Expert Member
    • Total Posts : 1061
    • Scores: 40
    • Reward points: 4660
    • Joined: 2005/03/21 17:42:28
    • Location: Washington, DC
    • Status: offline
    RE: SMS MOF file for Win32_PnPSignedDriver 2008/05/14 17:12:49 (permalink)
    0
    Is this occuring on all the clients or just one or a few?

    Hope this helps.
    Paul
    #2
    bhunter
    Starting Member
    • Total Posts : 16
    • Scores: 0
    • Reward points: 27390
    • Joined: 2006/05/24 05:14:04
    • Status: offline
    RE: SMS MOF file for Win32_PnPSignedDriver 2008/05/15 03:10:02 (permalink)
    0
    This is happening on all clients (Windows XP and Windows 2003)
    #3
    Guest
    Expert Member
    • Total Posts : 120
    • Scores: 0
    • Reward points: 0
    • Joined: 2002/06/01 05:49:42
    • Location: Orlando, FL
    • Status: online
    RE: SMS MOF file for Win32_PnPSignedDriver 2008/05/15 11:24:26 (permalink)
    0
    [SMS_Report (TRUE), key ] 
           string     Description;
     
    This is not a valid KEY, and if you don't use all the properties of the class you must use the MS_VIEW_INSTANCE_PROVIDER.
    And you must still include all the valid KEY's and they must be set to report TRUE.
     
     

    \ / /
    \\\' , / //
    \\\//, _/ //,
    \_-//' / //<,
    \ /// > \\\`__/_
    /,)-~>> _\` \\\
    (/ \\ //\\
    // // \\\
    (( ((
    #4
    bhunter
    Starting Member
    • Total Posts : 16
    • Scores: 0
    • Reward points: 27390
    • Joined: 2006/05/24 05:14:04
    • Status: offline
    RE: SMS MOF file for Win32_PnPSignedDriver 2008/05/15 11:44:30 (permalink)
    0
    According to MSDN documentation, that 'key' is the Name field.  I've changed it to this, but still have the same problem.
     
    Here is a copy of my MOF code now:

    #pragma namespace("\\\\.\\root\\cimv2\\sms")
    #pragma deleteclass("WIN32_PNPSIGNEDDRIVER",NOFAIL)
    [ SMS_Report     (TRUE),
      SMS_Group_Name ("WIN32_PNPSIGNEDDRIVER"),
      SMS_Class_ID   ("MICROSOFT|WIN32_PNPSIGNEDDRIVER|1.0") ]
    class Win32_PnPSignedDriver : SMS_Class_Template
    {
        [SMS_Report (TRUE), key ]
     string     Name;
        [SMS_Report (TRUE)      ]
     string     Description;
        [SMS_Report (TRUE)      ]
     string     DeviceID;
        [SMS_Report (TRUE)      ]
     string     ClassGuid;
        [SMS_Report (TRUE)      ]
     boolean    IsSigned;
        [SMS_Report (TRUE)      ]
     string     Signer;
        [SMS_Report (TRUE)      ]
     string     InfName;
        [SMS_Report (TRUE)      ]
     string     DriverVersion;
        [SMS_Report (TRUE)      ]
     datetime   DriverDate;
        [SMS_Report (TRUE)      ]
     string     DriverProviderName;
        [SMS_Report (TRUE)      ]
     string     HardWareID;
        [SMS_Report (TRUE)      ]
     string     DeviceName;
        [SMS_Report (TRUE)      ]
     string     DeviceClass;
        [SMS_Report (TRUE)      ]
     string     CompatID;
        [SMS_Report (TRUE)      ]
     string     Location;
        [SMS_Report (TRUE)      ]
     string     PDO;
        [SMS_Report (TRUE)      ]
     string     Manufacturer;
        [SMS_Report (TRUE)      ]
     string     FriendlyName;
        [SMS_Report (TRUE)      ]
     string     DevLoader;
        [SMS_Report (TRUE)      ]
     string     DriverName;
    };

     
     
     
    Still producing the exact same error messages...... 
     

    Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, Description, DeviceClass, DeviceID, DriverVersion, ClassGuid, CompatID, DeviceName, DevLoader, DriverDate, DriverName, DriverProviderName, FriendlyName, HardWareID, InfName, IsSigned, Location, Manufacturer, Name, PDO, Signer FROM Win32_PnPSignedDriver; Timeout = 600 secs.
    Failed to add an instance of class Win32_PnPSignedDriver to historical store: 80041002
    Failed to add an instance of class Win32_PnPSignedDriver to historical store: 80041002
    Failed to add an instance of class Win32_PnPSignedDriver to historical store: 80041002
    Failed to add an instance of class Win32_PnPSignedDriver to historical store: 80041002
    Failed to add an instance of class Win32_PnPSignedDriver to historical store: 80041002
    Failed to add an instance of class Win32_PnPSignedDriver to historical store: 80041002
    Failed to add an instance of class Win32_PnPSignedDriver to historical store: 80041002
    Failed to add an instance of class Win32_PnPSignedDriver to historical store: 80041002
    Failed to add an instance of class Win32_PnPSignedDriver to historical store: 80041002
    Failed to add an instance of class Win32_PnPSignedDriver to historical store: 80041002
    Unknown error encountered processing an instance of class Win32_PnPSignedDriver: 80041002
    #5
    Guest
    Expert Member
    • Total Posts : 120
    • Scores: 0
    • Reward points: 0
    • Joined: 2002/06/01 05:49:42
    • Location: Orlando, FL
    • Status: online
    RE: SMS MOF file for Win32_PnPSignedDriver 2008/05/15 12:06:20 (permalink)
    0
    http://msdn.microsoft.com/en-us/library/aa394354(VS.85).aspx
    read down a little further and you'll see that 
    SystemCreationClassName and
    SystemName have KEY qualifiers
     
    and to note: this MSDN article is missing the following properties
    CreationClassName
    DriverProviderName
     
    and ProviderName is NOT valid, it should be DriverProviderName

    \ / /
    \\\' , / //
    \\\//, _/ //,
    \_-//' / //<,
    \ /// > \\\`__/_
    /,)-~>> _\` \\\
    (/ \\ //\\
    // // \\\
    (( ((
    #6
    bhunter
    Starting Member
    • Total Posts : 16
    • Scores: 0
    • Reward points: 27390
    • Joined: 2006/05/24 05:14:04
    • Status: offline
    RE: SMS MOF file for Win32_PnPSignedDriver 2008/05/15 12:17:32 (permalink)
    0
    Oh gosh, this is getting confusion now.  I didn't use the MSDN article to get the names, I simply exported the Win32_PnPSignedDriver class using WMI CIM Studio.
     
    I'll make those changes and get back to you tomorrow.
     
    Thanks for your help so far...
    #7
    bhunter
    Starting Member
    • Total Posts : 16
    • Scores: 0
    • Reward points: 27390
    • Joined: 2006/05/24 05:14:04
    • Status: offline
    RE: SMS MOF file for Win32_PnPSignedDriver 2008/05/17 12:41:14 (permalink)
    0
    OK, so I figured this out eventually.
     
    SMS won't inventory the Win32_PnPSingedDriver class simply because it doesn't have ANY valid keys.  This is because the "name" field (which is the key) doesn't have any named values.
    So what I had to do was to create a new custom class (with a valid key) which is a replica of the Win32_PnPSignedClass, and then inventory this class.
    SMS is now able to inventory my custom replica class and the information is finally in SMS.  What a headache, but I'm glad I found a way to resolve this.
    #8
    brendan
    New Member
    • Total Posts : 1
    • Scores: 0
    • Reward points: 2830
    • Joined: 2017/05/25 23:17:08
    • Status: offline
    Re: RE: SMS MOF file for Win32_PnPSignedDriver 2017/05/25 23:21:05 (permalink)
    0
    Hi bhunter
     
    I know the last post on this page was over 9 years ago, but is there any chance you would have the code for the MOF for the custom class you created here? Or are you able to provide any further details on how you did this?
     
    Regards
    Brendan
    #9
    bhunter
    Starting Member
    • Total Posts : 16
    • Scores: 0
    • Reward points: 27390
    • Joined: 2006/05/24 05:14:04
    • Status: offline
    Re: RE: SMS MOF file for Win32_PnPSignedDriver 2017/05/30 04:02:36 (permalink)
    0
    Sorry, too long ago for my memory now.
     
    I think I wrote a script that would export each of the class's fields and wrote then back into a new class, with the key correctly assigned (when creating the new class).   Then a MOF would be able to correctly read this class and report it back into SCCM.
    #10
    Jump to:
    © 2018 APG vNext Trial Version 5.5