Audit Monitor details

All Replies

• Friday, November 06, 2009 3:31 PMKent Agerlund

   
  

  0

  Sign In to Vote
  Hi,
  
  You have an example here - http://www.myitforum.com/articles/8/view.asp?id=8489 It's for SMS 2003 which means that you don't have to run mofcomp on each client but instead add the information to configureation.mof.

  ---

  Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
  • Reply
  • Quote

   
• Friday, November 06, 2009 3:42 PMBagowarrior

   
  

  0

  Sign In to Vote
  Excellent. I'll implement that. Will I be able run a report against this information?
  • Reply
  • Quote

   
• Friday, November 06, 2009 3:56 PMKent Agerlund

   
  

  0

  Sign In to Vote
  sure, once you have the information in the database you can run reports and queries against the info.

  ---

  Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
  • Reply
  • Quote

   
• Friday, November 06, 2009 4:29 PMBagowarrior

   
  

  0

  Sign In to Vote
  Would I be able to query by creating a report and then doing a SQL query? If so what fields names would I query against? Will then be available to select in the Views field?  Any help appreciated this is all pretty new stuff to me.  Thanks
  • Reply
  • Quote

   
• Friday, November 06, 2009 8:20 PMGarth JonesMVP

   
  

  0

  Sign In to Vote
  There are a few tools out that that you might want to look at Sherry did a blog post a while back. http://myitforum.com/cs2/blogs/skissinger/archive/2008/08/14/how-to-gather-monitor-information-like-serial-number.aspx
  
  

  ---

  http://www.enhansoft.com/

  • Marked As Answer byBagowarrior Wednesday, November 11, 2009 10:59 AM
  •  
  • Reply
  • Quote

   
• Tuesday, November 10, 2009 1:42 PMBagowarrior

   
  

  0

  Sign In to Vote
  Hmm. I'm not sure I have followed this correctly in SCCM, or I don't know where to look to find the data. 

  
  

  Is any one able to break this down step by step for a noob?

  
  

  Thanks
  • Reply
  • Quote

   
• Thursday, November 12, 2009 1:34 PMSherry KissingerMVP

   
  

  0

  Sign In to Vote
  That blog entry mentioned several different methods: some of which are free and require quite a bit of legwork by the individual to get them to work (free is never easy).  Which one did you pick? If you picked one of the free ones, did you confirm the data got into WMI?  did you update the mof files? did you monitor inventory.log?
  
  I won't be able to give you tips of where to start, until we know which method you are trying.  (personally, I'd skip the free ones, and evaluate one of the for-pay solutions.  The free ones are dicey at best if you are looking for accurate information.  If you've told the bosses' that it'll be a best guess, and 70% accuracy is better than 0% data, go for a free answer.)

  ---

  Standardize. Simplify. Automate.
  • Reply
  • Quote

   
• Tuesday, November 17, 2009 11:57 AMBagowarrior

   
  

  0

  Sign In to Vote
  i used the following link http://www.myitforum.com/forums/m.asp?m=183273

  
  Once I worked out how to put the information in the mof files correctly it worked a treat.

  
  

  The way I did it was put the following in configuration.mof

  
  

  #pragma namespace("\\\\.\\root\\CIMV2")

  #pragma deleteclass("MonitorInfo", NOFAIL)

  [ dynamic, provider("RegProv"),ClassContext("local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Tools\\MonitorInfo")]

  
  

  class MonitorInfo

  {

    [Key] string EDID_SerialNumber;

    [PropertyContext("EDID_DeviceID")] string EDID_DeviceID;

    [PropertyContext("EDID_ManufactureDate")] string EDID_ManufactureDate;

    [PropertyContext("EDID_ModelName")] string EDID_ModelName;

    [PropertyContext("EDID_Version")] string EDID_Version;

    [PropertyContext("EDID_VESAManufacturerID")] string EDID_VESAManufacturerID;

    [PropertyContext("Windows_PNPID")] string Windows_PNPID;

    [PropertyContext("Windows_VESAID")] string Windows_VESAID;

  };

  
  

  The add the following to sms_def.mof

  
  

  #pragma namespace("\\\\.\\root\\CIMV2\\SMS")

  
  

  [SMS_Report(TRUE), SMS_Group_Name("MonitorInfo"),SMS_Class_ID("MicroSoft|MonitorInfo|1.0")]

  class MonitorInfo : SMS_Class_Template

  {

    [SMS_Report(TRUE),Key] string EDID_SerialNumber;

    [SMS_Report(TRUE)] string EDID_DeviceID;

    [SMS_Report(TRUE)] string EDID_ManufactureDate;

    [SMS_Report(TRUE)] string EDID_ModelName;

    [SMS_Report(TRUE)] string EDID_VESAManufacturerID;

    [SMS_Report(TRUE)] string Windows_PNPID;

    [SMS_Report(TRUE)] string Windows_VESAID;

  };

  
  

  
  

  Then run the vbs on each workstation so that the relevant regkey entry is created.

  
  

  I've since amended my report files to bring back the serial numbers of the monitors. Great stuff so far. 

  
  

  To keep the data fresh I'll be deleting the reg key and recreating on login.

  
  Thanks for all your help.
  • Reply
  • Quote