Loading...
You are not logged-in Login/Register





  • Posts   Search Threads
  • Stephen Hibbert (Intel)June 18, 2009 12:32 PM PDT   
    Retrieving Disk Information

    I use CIM_Processor to get information about the processor, I use CIM_PhysicalMemory to get information about physical memory, etc.

    Which CIM class do I use to retrieve disk information (model, serial number, size)? This information is shown in the WebUI, so I know it's possible to retrieve it.

    Thanks,
    Stephen

    Andrew Schiestl (Intel)June 18, 2009 1:18 PM PDT
    Rate
     
    Re: Retrieving Disk Information

    I use CIM_Processor to get information about the processor, I use CIM_PhysicalMemory to get information about physical memory, etc.

    Which CIM class do I use to retrieve disk information (model, serial number, size)? This information is shown in the WebUI, so I know it's possible to retrieve it.

    Thanks,
    Stephen

    That should be the CIM_MediaAccessDevice class, but the CIM_PhysicalPackage class could also be involved (there's an association between the two in the Hardware Asset instance diagram).

    Stephen Hibbert (Intel)June 18, 2009 3:53 PM PDT
    Rate
     
    Re: Retrieving Disk Information


    That should be the CIM_MediaAccessDevice class, but the CIM_PhysicalPackage class could also be involved (there's an association between the two in the Hardware Asset instance diagram).

    Thanks! I had tried everything but CIM_PhysicalPackage, which gives you the model and the serial number. CIM_MediaAccessDevice gives you the size.

    Were you referring to the diagram in "Intel AMT WS-Management Flows.pdf"?

    Andrew Schiestl (Intel)June 18, 2009 5:14 PM PDT
    Rate
     
    Re: Retrieving Disk Information


    Thanks! I had tried everything but CIM_PhysicalPackage, which gives you the model and the serial number. CIM_MediaAccessDevice gives you the size.

    Were you referring to the diagram in "Intel AMT WS-Management Flows.pdf"?

    That's also a valid place for the diagram I used, but I actually got to it in a different manner.

    I actually looked at the WS-Managment Class Reference.  Probably the quickest way to get there is if you open the index.html in the DOCS folder of the SDK, then select the WS Management Class Reference hyperlink (the top level of the reference is actually the index.html file in the DOCS/WS-Management_Class_Reference folder, but that's kind of buried and easy to miss).

    Anyway, the class reference has an expandable menu of CIM classes by interface (like Hardware Asset), I find it a little easier to use that then the Flows.pdf when I'm searching for information. 

    Andy

    Stephen Hibbert (Intel)June 19, 2009 9:50 AM PDT
    Rate
     
    Re: Retrieving Disk Information


    That's also a valid place for the diagram I used, but I actually got to it in a different manner.

    I actually looked at the WS-Managment Class Reference.  Probably the quickest way to get there is if you open the index.html in the DOCS folder of the SDK, then select the WS Management Class Reference hyperlink (the top level of the reference is actually the index.html file in the DOCS/WS-Management_Class_Reference folder, but that's kind of buried and easy to miss).

    Anyway, the class reference has an expandable menu of CIM classes by interface (like Hardware Asset), I find it a little easier to use that then the Flows.pdf when I'm searching for information. 

    Andy

    Wow, this is extremely useful. Thanks.

Forum jump:  

Intel Software Network Forums Statistics

16,377 users have contributed to 46,364 threads and 164,041 posts to date.

In the past 24 hours, we have 9 new thread(s) 31 new posts(s), and 20 new user(s).

In the past 3 days, the most popular thread for everyone has been Program compiles in release but not debug The most posts were made to You need to show us the whole The post with the most views is vectorization of sin/cos results in wrong values

Please welcome our newest member fruitbrown


For more complete information about compiler optimizations, see our Optimization Notice.