Config 101 even possible?

[BSmit21]

Trying to use Intel vPro as a replacement for IPMI or perhaps an Avocent remote KVM. We are looking for a simple, easily configured setup.

1) We don't want (or need) certificates.

2) We don't want (or need) a dedicated Management Presence Server.

3) Encryption is assumed via VPN to a trusted local network; we don't need it either.

All we're looking for is the ability to access the BIOS in the (rare) event of a small business server outage without having to dispatch somebody onsite. Servers all running RHEL/CentOS 6. Is this possible?

[Alan_A_Intel]

Hi BenjaminSmith,

If you're using server processors then the first thing you need to do is verify that your computers are actually vPro capable. Look up your CPU and motherboard at http://ark.intel.com/ http://ark.intel.com and check if they support vPro.

Once you've verified that they are vPro capable, then the easiest way to configure them is by logging into the Management Engine BIOS Extension (MEBx). The version will determine how you configure AMT in the MEBx, but if it's one of the last few generations then all you have to do is the following:

1. Login
2. Select Intel AMT Configuration
3. Activate Network Access
4. Exit and reboot

After the computer is configured you will use the MDTK (specifically the Manageability Commander Tool) to connect and manage your vPro computer.

http://opentools.homeip.net/open-manageability http://opentools.homeip.net/open-manageability

If you have any questions on how to configure your version of AMT in the MEBx, I will be more than happy to guide you through that.

-Alan