Skip navigation

Check out these two analysis papers, which show how two different companies deployed vPro and started seeing quick returns. These are two-pagers and they itemize the dollars saved.


ROI Analysis: Texas-Based Healthcare System Administers Patch Management and IT Support Efficiencies with Intel(R) vPro(TM) Technology


ROI Analysis: Utility District Achieves Positive ROI of 82%

Part III of my trip to Oregon. Jake shows off the server room for the automation environment the team has created for the testing of vPro systems.



Next Up:

I'll be closing out my trip to Oregon and finally show the automation interface they use to test.  I also am getting full access in my lab in folsom so i can leverage this awesome infrastructure, therefore save my local folks time and can test consoles on the fly.


Feet on the street Updates

*if there is a specific team you would like to know more about that works on vPro please leave a comment and let me know.  I'm planning on a few more groups before the end of the year as I finish my US Feet on the Street: vPro.


Past Feet on the Street Posts

Feet on the Street - vPro Series - Meet Jake G. - Part II

Feet on the Street - vPro Series - Meet Jake G. - Part I

Feet on the Street - vPro Series - Meet Wendy West

There have been some questions around how to setup the Intel® IT Director environment for SMBs.    Below is a diagram of how Intel IT Director can be setup and managed.


Important to point out the minimum system requirements for Intel IT Director:


System Requirements

Intel IT Director will ONLY install on the following hardware platform:

  • The Intel IT Director application, "itdirector.exe", requires an Intel® Core™2 Processor with vPro™ Technology, with the Intel® Q45 or Q35 Express Chipset
  • The Intel IT Director configuration tool, "itdirectorconfig.exe", requires no special hardware

Intel® IT Director dashboard PC and client PC’s should support one of the following Operating Systems:

  • Windows* XP Professional 32-bit with SP2 or SP3
  • Windows* XP Professional 64-bit with SP2
  • Windows Vista* Ultimate 32-bit or 64-bit, with no SP or with SP1
  • Windows Vista* Enterprise 32-bit or 64-bit, with no SP or with SP1
  • Windows Vista* Business 32-bit or 64-bit, with no SP or with SP1

Languages Supported
Intel® IT Director software application supports English, Russian, French International, Portuguese (Brazil) and German.


Where to download or learn more information about Intel IT Director:


If you have any questions about Intel IT Director, feel free to reply to this blog or start a discussion!  We are here to help answer questions!



Corey T. Morris

Do you need guidance for infrastructure preparation for Pro platforms?


The following checklist is for customer infrastructure preparation to ensure you can implement Pro platforms within the customer's corporate production environment.


Infrastructure Prep Checklist for Microsoft ConfigMgr

Jake walks me through the Ideation Lab, their infrastructure & their console testing automation setup.


NOTE: the lighting was not the best. 


Next Up, Jake shows me the data center that houses their infrastructure.


Prior Feet on the Street

Feet on the Street - vPro Series - Meet Jake G. - Part I

Feet on the Street - vPro Series - Meet Wendy West



This is my first contribution to the Intel vPro Expert center, and although I would not consider myself an expert on this product, I've still been graciously allowed to post here. Thanks Josh!   


I'd like to start out by introducing myself. My name is Trevor Sullivan, and I am a desktop systems engineer at a large retail corporation. Over the past 8 months or so, I've been working quite a bit with several people from Intel and Microsoft to better understand the Intel vPro technology, and how it can benefit my company. Overall, I'm really impressed with the technology, and I am fortunate enough to be working with an environment that has a pretty decent install base of Intel vPro-enabled systems.


I'd like to take a few minutes to explain a few issues that we recently experienced with our production vPro implementation.





Provisioning Certificate Chain Invalid


We're using Intel vPro with Microsoft Configuration Manager 2007 SP1, and for a while, we had been running into issues that prevented us from provisioning a vPro device. It turns out that the reasoning behind this was related to our provisioning certificate. We requested a certificate from Verisign, and imported it into our central SCCM site server. We have several child primaries to our central SCCM primary site server, however, and we were using the same provisioning certificate on those systems (Intel confirmed that this was possible).







When I exported the certificate (using the Certificates MMC snap-in), with its private key, from my central SCCM site server, I did not choose the option to export the certificate chain with it. Importing the certificate, with its private key, went just fine on the other SCCM primaries, but provisioning just didn't work. After working with Bill York from Intel for several hours, it was finally determined that the Verisign Class 3 Intermediate Certificate Authority's public key certificate was expired in the Intermediate certificate store on the SCCM site server running the out-of-band (OOB) service point. I imported the updated Verisign Intermediate certificate into the server's Intermediate CA certificate store, which resolved the issue I was having.







If you are experiencing this specific problem, you should see something like the following in your amtopmgr.log on the SCCM site server running the OOB service point:







Try to use provisioning account to connect target machine

Server unexpectedly disconnected when TLS handshaking.

**** Error 0x382b948 returned by ApplyControlToken





Although this probably should have been obvious to me, I did not actually open the provisioning certificate on the server I had imported the certificate on, to verify that the certificate was valid. If I had done so, I would have seen a message stating that the certificate was invalid, and then I could have looked at the certificate chain tab to see that the Verisign Intermediate CA's certificate was not valid. After examining the certificate for the Intermediate CA, it was determined that it had expired, causing my provisoning certificate to become invalid.





Microsoft PKI -Auto-Approval of Pending Certificate Requests



After resolving the certificate issue, we started seeing another issue. This issue was related to our internal Microsoft PKI. The next symptom we saw was again in the amtopmgr.log file (+in case you haven't figured it out, this is probably the most useful AMT log in SCCM). Here are the messages we saw:


Send request to AMT proxy component to generate client certificate. (MachineId = 60752)

Successfully created instruction file for AMT proxy task: D:\SMS\inboxes\

RETRY(1) - Validate client certificate for AMT device being generated.

Wait 20 seconds to find client certificate for AMT device being generated again...

AMT Provision Worker: Wakes up to process instruction files

AMT Provision Worker: Wait 20 seconds...

RETRY(2) - Validate client certificate for AMT device being generated.

Wait 20 seconds to find client certificate for AMT device being generated again...

AMT Provision Worker: Wakes up to process instruction files

AMT Provision Worker: Wait 20 seconds...

RETRY(3) - Validate client certificate for AMT device being generated.

Wait 20 seconds to find client certificate for AMT device being generated again...

AMT Provision Worker: Wakes up to process instruction files

AMT Provision Worker: Wait 20 seconds...

RETRY(4) - Validate client certificate for AMT device being generated.

Wait 20 seconds to find client certificate for AMT device being generated again...

AMT Provision Worker: Wakes up to process instruction files

AMT Provision Worker: Wait 20 seconds...

RETRY(5) - Validate client certificate for AMT device being generated.

Error: Missed device certificate. To provision device with TLS server or Mutual authentication mode, device certficate is required. (MachineId = 60752)

Error: Can't finish provision on AMT device with configuration code (0)!

>>>>>>>>>>>>>>>Provision task end<<<<<<<<<<<<<<<





What this is telling you, is that the OOB service point was unsuccessful with its attempt to generate and retrieve a web server certificate, for the vPro client, from your internal Microsoft CA (either root or subordinate, but in our case, a subordinate). Although we had duplicated and configured the web server certificate template on our CA, the certificate was not getting created as we expected. The issue, in this case, was that our CA was not configured to automatically approve pending certificate requests.





In order to resolve this issue, follow these steps:





1. Open the Certification Authority MMC snap-in and connect to your CA

2. Right-click the CA node, and select Properties

3. Select the "Policy Module" tab

4.  Click the Properties button

5. Choose the lower radio button (It reads: "Follow the settings in the certificate template, if applicable. Otherwise, automatically issue the certificate.")

6. Click OK on all dialog boxes

7. Restart the CA service, to allow the setting to take effect








I have a  few more issues I'd like to talk about, mostly related to DNS. I will post again with details.





Thanks for reading,





Trevor Sullivan

Systems Engineer



Some customers might have an environment where there is a network domain that is different to their Active Directory domain. This typically arises when there is a Microsoft Active Directory structure, yet there is a legacy non Microsoft DHCP and DNS infrastructure that uses a different (network) domain. This can cause a bit of an issue for vPro management if you are integrating with Active Directory (and also if you are using certificates for encrypting communication.) The reason for this is that typically a machine will be provisioned with the AD FQDN as all provisioning methods which rely on the Activator Utility or a management console's client agent will query locally using WMI and will pick up the FQDN that resides at the OS level. This will be OK for provisioning and will not be flagged as an issue. However, when the machine will be accessed for OOB management , the Kerberos protocol that dictates how the AD Objects for your provisioned vPro machines is accessed, will prevent access. This is because when the AD Object is interogated it will get a request from the management console that relies on a DNS resolution. That resolution will provide a different FQDN than the AD OS FQDN.


In the past, the paradigm has been to circumvent this situation for the purposes of vPro provisioning and management by using hostname only provisioning, assuming that the hostname was unique. This was possible as long as you were using SCS 3.x. If you are using SCS 5.0 and above this approach will no longer work. Even though my direct personal experience on this matter has been directly with SCS and SMS I see no reason why this won't also apply to Microsoft SCCM or Altiris with its underlying SCS (when is supports SCS 5.x).



The Solution: you will need to provision your vPro machines with the network resolvable FQDN. The manner that we have implemented it is by having a server script that performs an nslookup dynamically and plugs that into the SCS DB instead of the AD FQDN as part of the provisioning flow. The other thing that caught us out for a while, is that we had to add the network domain into the Server TCP/IP advanced network settings as a secondary domain suffix. As you will most probably have a new Server setup for hosting SCS then this configuration step most probably hasn't been performed for you and therefore you will need to remember to do it!



Hopefully this helps prevent some headaches for some of you...






A representative of Microsoft holds a discussion with an Intel manager from Digital Office Platform Division, Mike Ferron-Jones. Find more about what Intel is doing for security, manageability, and energy efficiency with vPro and how Microsoft is helping to deploy some of the vPro solutions with its software. Listen to this clip for an insight on Wake-on-LAN, Microsoft Application Virtualization, and Virtual Desktop Infrastructures. Click the link below to listen.

Listen Here: [Microsoft/Intel Podcast|]

While in Oregon this week I was able to talk with Jake G, He's in the Brand Promise Validation team (which I thought he was part of Interop team), however you'll see what he tells me when you watch the video.   This is the first part of the day & throughout the afternoon he showed me a couple of innovative ways Intel is testing vPro to ensure it is ready for IT shops & End Users.   



Also to note, if you have seen my prior posts on CIRA (FAst Call for Help), Jake is the one helped me get the pitures, demo's & startup data for those posts a few month's back.


Next Up, Jake walks me through the Ideation Lab, their infrastructure & their console testing automation setup.


Prior Feet on the Street

Feet on the Street - vPro Series - Meet Wendy West

I had the pleasure this week of having lunch with Wendy West, She is in Digital Office Platform Marketing, which is responsible for vPro Marketing, specifically she is the Communications Program Manager in that team.   Here's a quick intro I was able to snap while we were driving.  Also to note, I have worked with Wendy about a year now and she is a super star on the vPro virtual team. 



Next up, I had the pleasure of meeting with Jake Gauthier & he showed me how we do testing on the platforms and the infrastructure that supports it.  stay tuned.


I've posted an update to the iAMT Scan Process Results Troubleshooting Guide to incorporate the changes to the iAMT Scan Tool. 



The new document is at



The new iAMT scan tool is at


Case Studies

Posted by gnszolnx Nov 11, 2008

Learn how Intel has helped top companies, universities, and hospitals  shorten the time it takes to do IT, including the following:


  • Complete an Asset Inventory

  • Solve Hardware Problems

  • Solve Software Problems

  • Protect all PC's by detecting antivirus agents


In many cases Intel has shortened the time it takes to complete these tasks by 25 to 50 percent, saving money, while also developing a more efficient workflow.


Business Success Stories


Whether you are planning to implement a Vendor TLS Certificate in the future, or you are having trouble applying a certificate you've already obtained, this article walks through the best practices. The details include all the steps to properly install the right items and resolve issues we've encountered up until this point. This article applies to Out of Band Management Solution 6.2. Since certificates introduce tight encryption security, if the right items and steps are not in place or followed, it can break the ability of AMT systems to provision with Remote Configuration.






Using Remote Configuration to Provision your Intel AMT vPro capable computers takes the work out of the progress. All 2.6, 3.0+ AMT systems come preconfigured to automatically use Remote Configuration to provision with a valid Provisioning Server. The hashes from vendors (AMT 3.0 includes Verisign, GoDaddy, Comodo) are already configured in the firmware, and upon connection to power and the network, will begin to send out requests for provisioning. Thus in this way the managed vPro systems are already prepared to be provisioned without any needed intervention by the IT staff.






The issues we see then arise from the server-side application of a certificate that matches the hashes already loaded. Obtaining and installing a vendor TLS Remote Configuration certificate needs to be done the right way so that authentication can succeed. Once in place, provisioning will roll forward without any further intervention. This article focuses on applying the server-side certificate so that provisioning can move forward automatically.





Obtaining a Remote Configuration Certificate

This subject has been covered previously. I wanted to lightly touch upon this as there is a vital step that should be taken so that if anything goes wrong we can correct it. First, the following article covers how to properly obtain a certificate:






Note that part of obtaining a Remote Configuration is submitting the request from the Server you plan to install the certificate onto. This process creates the private key for the server-side certificate, and this piece will not be available until partway through the application of the crt (or cer) file obtained from the vendor. The specific step that provides the full key, both private and public, is when the certificate is exported after the initial import into a PFX format, checking the option to export the private key will give you a complete backup of the full certificate. If something happens, or if the application didn't go right, we'll need both, so it's essential to export this as soon as possible.







During the steps to install the certificate emphasis will be given on the step where the export should take place.





Installing the Certificate

I've condensed the steps required into the following list. This process works for all vendors once you've obtained a certificate. Note that these steps are provided to consolidate both recommended steps and documentation into one whole.


  1. Go to Start > Run > type mmc > and click OK.

  2. In the resulting console click under File and choose Add/Remove Snap-in...

  3. Near the bottom of the resulting window click the Add button.

  4. From the list that appears select Certificates and then click the Add button.

  5. Leave the radial button selected on ‘My user account' and click Finish.

  6. From the same list select Certificates again and click the Add button.

  7. From the resulting window change the radial select to ‘Computer account' and click Next.

  8. Leave the selection at ‘Local computer: (the computer this console is running on) and click Finish.

  9. Click the Close button in the window offering you the list of available snap-ins.

  10. At the original add/remove snap-in screen verify that you have two entries:

    1. Certificates - Current User

    2. Certificates (Local Computer)

  11. Click OK.

  12. Expand both trees in the left-hand pane within the console. You should see the full certificate stores.

  13. Right-click on the Personal folder under the Current User certificate store and highlight ‘All Tasks' and click on ‘Import' in the pop-out menu.

  14. Click Next on the Welcome page of the Certificate Import Wizard and click the Browse button.

  15. Browse to the cer or crt file provided by the vendor, highlight it, and click Open.

  16. Click Next, and leave the radial option on ‘Place all certificates in the following store', which should be set to ‘Personal'. Click Next.

  17. Under the Completing section of the wizard, Click Finish. You should receive a pop-up .

  18. NOTE! This is the vital step mentioned previously in the article. We will now export the certificate with both public and private keys, which will give us the full set and allow us to remove and reapply if necessary. In the MMC select the newly imported certificate > right-click > and choose All Tasks > Export...

  19. Click Next on the Welcome screen. In the resulting list you should have an active option for ‘Personal Information Exchange - PKCS #12 (.PFX)'. If this option is not available there is a problem with the certificate and the private key is not accessible.

  20. Follow the wizard, and ensure you select the option ‘Yes, export the private key'. When saving the file, it will prompt you to set a password to protect the private key (this is recommended for security reasons). The export should leave you a PFX file. Keep this in a safe place, and back it up just in case.

  21. Next we need to import the full key into the Computer store. Start back in the MMC, under the Local Computer certificate store, right-click on the Personal folder, select All Tasks > Import...

  22. Click Next on the Welcome screen and click the Browse button on the subsequent screen.

  23. Browse to the newly exported PFX file. Note that you will need to change the ‘Files of type' to include the PFX format. Click Next.

  24. The Password screen prompts for the password you set when you exported the key in step #20. Enter the password and click Next.

  25. Choose or leave the select to ‘Place all certificates in the following store'. The value should be Personal. Click Next.

  26. Click Finish on the end details page to complete the import.

  27. Next, we need to load the certificate into Intel SCS so it can properly authenticate with the AMT systems requesting Remote Configuration. Browse to the following location: \Program Files\Intel\AMTConfServer\Tools.

  28. Execute the file loadcert.exe.

  29. Press Y and Enter.

  30. A ‘Select Certificate' popup will appear. Select the name of the cer or crt file you received from the vendor and click OK. The window will disappear.

  31. Now both Personal certificate stores and Intel SCS should have all the needed certificates to successfully work with Remote Configuration. However, we are not done as other steps may be needed.


Reinstalling the Certificate

If you need to reinstall the certificate and have a PFX file, you can do so by opening both certificate stores (User and Local Computer) as outlined in the previous steps. Browse through the certificate stores and delete any instance of the vendor certificate. This will remove any associations and allow a clean application of the certificate to occur. Look for the following:


  • The name matching the name of the cer or crt file obtained from the vendor

  • The vendor's certificate (the entry will contain the vendor name).


NOTE: Be careful when removing vendor certificates as they may not be part of the Remote Configuration. The best example is Verisign, which may have many entries. If unsure, leave the certificate in place, or export it before deleting it so you can restore it if necessary.




Other Setup Requirements

The following items may be required, depending on the environment.





Each zone within DNS should have a ProvisionServer entry to ensure that Remote Configuration requests are properly routed. This will also help properly resolve names during the authentication process. To test, log onto a system on the subnet you're trying to conduct Remote Configuration from. Run a command prompt and use the following command:


  • ping ProvisionServer





We should see the responding IP Address by the IP Address of the Notification Server, or, if you've set it up this way, the Intel SCS Server conducting provisioning. Another test you can try is to run the following command:



  • nslookup ProvisionServer





We should get the data on the Notification Server's name.





DNS Zones

In a multiple domain structure this is especially important, but all environments need to have the right data in DNS to properly pass and authenticate in a TLS environment. The DNS Primary Zone should be set to the Domain path contained within the certificate. For example, if the certificate name is MyNSServer_My1Domain_local, the DNS Primary Zone should be My1Domain.local. Without this, authentication can fail as the FQDN is used during authentication, and if the name being transmitted across the wire doesn't match what's in the certificate, authentication will fail. Here is another example:


  • Certificate: MyNSServer_My1Domain_local.crt

  • DNS Primary lookup Zone: My1Domain.local


DHCP Option

Another Network related requirement may be DHCP Option 15. While I'm not sure why this has proven to be required in some environments and not others, creating this option has resolved failed authentication issues within Remote Configuration.






In DNS, create an entry for Option 15, with the value of the domain path. This will often be the same as what is located in the DNS Primary Zone. The following details are an example:



  • Certificate: MyNSServer_My1Domain_local.crt

  • DNS Primary lookup Zone: My1Domain.local

  • DHCP Option 15: My1Domain.local



Following the above procedure should allow remote configuration to occur without problems. Once in place, the configuration will move forward with automatically provisioning systems that support Remote Configuration.

There have been many questions around which Intel® boxed products such as Intel® Desktop boards and processors.     See below which desktop boards and processors are supported for Intel® vProTM Technology:



Desktop boards supported:

DQ45EK -


DQ45CB -



Processors supported:

Intel® CoreTM2 Quad Processor -


        Q9650, Q9550, Q9450, Q9400, Q9300


Intel® CoreTM2 Duo Processor -


     E8600, E8500, E8400, E8300, E8200


For complete list of part numbers – See the following links:

Intel Core2 Quad Processor -

Intel Core2 Duo Processor -


Microsoft has just released a hotfix to address AMT 4 / AMT 5 power control within System Center Configuration Manager 2007 Service Pack 1.






System Center Configuration Manager 2007 (KB957469):


  • Description: The Out of Band Power control function does not work for clients that have the Intel AMT 4 or Intel AMT 5 chipset in System Center Configuration Manager 2007 Service Pack 1






Please reference the following WIKI for a comprehensive list of required software bundles and hotfixes for SCCM SP1 and vPro/AMT Out of Band Management:









--Matt Royer

In continuation of my quest to learn more about power and identify who's making the IT shop transition to power management a possibility, I have news to report out on. 


Today while talking with a Frank (Intel IT) he mentioned that the very company I used to work for is now giving out rebates to customers that are utilizing power management software to control their PC's.  Specifically if you are in the Northern California area, the power company is called PG&E (Pacific Gas & Electric)   


Here are the conditions: (Please note the NO laptop portion).



Must be a PG&E electric customer. The installation of qualifying

software must allow centralized control at the server level of the

power management settings (sleep mode and shutdown) of PCs

on a distributed network. In addition, the software must have a

reporting feature that allows monitoring and validation of energy

savings. Qualifying software must be purchased and installed on

or after March 1, 2007. When contacted, customers must allow

PG&E access to customer property site to verify the software

license installation at the server level and the number of PCs

being controlled by the system. When submitting a rebate

worksheet, customers must ensure the following documentation

is attached:

1. copy of Software License Agreement,

2. a report directly from the Network Energy Management

Software that verifies the number of PCs that are being

controlled by the system, and

3. the number of computers authorized per License.

New Requirements

• Effective August 8, 2008, the rebate for the qualifying

software is for control of desktop PCs only.

• Effective August 8, 2008, a rebate will not be available for

control of laptop and laptop stations.

• Customers who purchase qualifying software by August 8,

2008 for laptop and laptop stations will receive a rebate if

applications are postmarked or received by PG&E’s Integrated

Processing Center (IPC) by October 8, 2008.

• Applications postmarked or received by PG&E’s IPC on or

after October 8, 2008 are not eligible for a rebate for laptop

and laptop stations.


Product Code Rebate/Unit Measure

M03 Network PC Power

Management Software $15.00/perPC



How wide spread is this across the globe?  i know in New York this is happening, where else?

Awhile back Nick the Intern & I decided to build a rock star vPro PC on our own. We scoped out the best hardware we could at the time and we built the following:


Intel BOXDQ35JOE Core 2 Quad/ Intel Q35/ FSB 1333/ vPro/ A&V&GbE/ MATX Motherboard

2.83GHz Core 2 Quad


Apevia X-Qpack2 Case

500W PSU

ASUS HD4870 Video Card


32GB SSD (for OS)

2x500GB RAID (storage)

Blu-ray/HDdvd Drive


After building it we started to test out the vPro functionality and that is when we realized that certain Intel MOBO (motherboard) the AMT settings are not seen through a CTRL+P prompt.  So tonight after a bit of VGA2USB conversion I created the following video to show where they are at.   Key message is if your building a vPro machine on your own & are planning on managing then be aware of where the location of the AMT settings.


Here's the video.




Have you created your own?  Let me know. .  post a pix and share.  I guess I should also post out a few pixs .. (will do shortly.).


Josh H

I just updated the vPRO ready systems page with the latest models from HP. This list covers all the current systems in the Notebook, Mobile Workstation, and Business PC lines that are vPRO ready. You can view the list here:

The Duchess of Windsor once famously quipped, “You can never be too rich or too thin.”  If she was a modern day IT director, however, she might be lamenting that neither is satisfactory.  End-users want their PCs rich, powerful and mobile, and most IT managers would like to give them what they want.  However, given budget constraints, nightmares of lost laptops brimming with customer records and the job of keeping applications uniform across an entire fleet of PCs, many IT managers might, albeit with regret, conclude, “Make mine thin, manageable and secure.”  To many IT professionals, this may seem the best answer:  equip as many end-users as possible with thin clients, and store the images and data on a central server where they can be maintained and guarded.  As we know, that works fine in some instances, but today’s end-users are too mobile, too performance oriented and too stubborn to part with their high-powered, go-anywhere-anytime PCs.  My Aunt Ruth, a duchess to me, used to tell me, “There’s more than one way to skin a cat.”  As Intel’s PR guy for business PCs, that’s what I’ve also been learning from Mike Ferron-Jones about client computing.  Mike heads up Intel’s research into a number of different models for client computing or what he calls “dynamic virtual clients.”  The idea is to give IT managers what they want – the efficiency and security of managing client applications, data and even OSs on a server, but without a large datacenter buildout – while at the same time offering in-kind benefits to end-users – the performance and mobility they’re accustomed to.  Simply put, the best of rich and thin.  Mike accomplishes this with various combinations of virtualization, streaming and storage, all with a financial objective commensurate with IT’s dwindling budgets.  If you’re interested in learning more, Mike has been asked to talk about “Dynamic Virtual Clients – How To Be Rich and Thin” at BrightTALK’s Virtualization Webcast, which airs here at 3:45 p.m. PST, Tue. Nov. 4.



If you can’t make that, there’s plenty to be learned on the Intel Emerging Compute Model Forum.  Check them both out.  As Mike likes to say (yeah, there’s one more) about dynamic virtual clients, “You can have your cake and eat it too.”

Here's a followon post for the new ICON in the system tray. I just received my new Dell e6400 machine and thought showing the real icon vs. the screen shots from the past would be helpful.  They definitely show more information as I discussed prior.


Centrino2 with vPro  - Finally more Screens to share out



Quick Tip for the Dell e6400

  • During bootup you will NOT be presented with a CTRL+P screen, however if you hit right after the machine starts it will take you into the MEBx.   I looked throughout the BIOS and there are no places to change this. if you find a route, let me know..


Josh H

Here's a TIP from our Interop team around how to verify whether a ping response is through OS or ME.  To do so you look to the TTL field in teh ping response. 


value in the range of 127/128 = OS NIC responding

Value in the range greater > 128 = ME is responding


Here's a quick video.



if your reading this blog you may have heard these words "Fast call for help" in relation to vPro, however without seeing it in action on a live platform it may not make a lot of sense.   Therefore this last week I had an opportunity to see my first platform live in action making a call back to the enterprise and then to be managed through a Serial over LAN to go into the BIOS.   The Platform was the new Panasonic CF-F8.  Nicole already posted out the console view. 


What questions do you have about this feature?  Also to note is that I started blogging about this capability called CIRA (see blogs below).


Client Initaitied Remote Access - vPro in 2008 - IDF


Centrino 2 - Digging in deeper into CIRA


My plan is to do a few more platforms over the next week with help from my IT expert (Frank).

Filter Blog

By date: By tag: