Activation Blog

Previous Next
Click to view josh.hilliker's profile
4

I witnessed our Internal IT guys defining a BKM that I thougth was very relevant to share out to the community, therefore let me explain.

Challenge: How can you use a mgmt console to read the AMT version so you can write a report in your mgmt console?

Output: You need to have a value placed into the registry that has data whether it's all of the BIOS, MEBx, SOL, HECI, etc.. driver versions, then you can read this data into a mgmt report.

Solution: run MEInfowin.exe and redirect the output to a text file using the “>” operator
Example --

MEinfowin.bmp

Then you need the write a program in your favorite language such as VB script or C# to read through that text file and write the desired into to the registry.

Then use your mgmt console to read these values & report out. The internal IT guys are doing this to check versions.

Thanks Intel IT folks for the BKM.

Tags: vpro_expert_center, troubleshoot, vpro, intel_it
Average User Rating
(0 ratings)


Add a comment Leave a comment on this blog post.
May 30, 2008 1:04 AM Reply Click to view Terry Cutler's profile Terry Cutler

Handy if you're trying to do a "Delayed Provision" - and need to know what systems are Remote Configuration capable and have not been provisioned\configured.

Some environments - like Altiris - use a client based agent and "discovery" to determine some of the core AMT components and states.

Curious though - why place the information in the registry?

May 30, 2008 1:12 AM Reply Click to view josh.hilliker's profile josh.hilliker in response to: Terry Cutler

why registry? I think the reason is that reading the registry is a known easy thing to program in & most consoles have default script that you can just plug in key to read & report back.

Oct 2, 2008 11:26 AM Reply Click to view wditto's profile wditto

Here is an approach that might come in handy. Small, silent utility that is software deployment friendly.

http://communities.intel.com/openport/docs/DOC-2062

Oct 6, 2008 2:51 PM Reply Click to view mgdyck's profile mgdyck in response to: Terry Cutler

The reason we write to the registry is that we already are capturing registry data using another package. We just added these new values to the data being collected so that we can then do reporting based on the resultant values.