Great questions. I would start by reading this quick start guide http://communities.intel.com/docs/DOC-1085 it does a great job of getting you going on the technology.

Now as for your current implementation, which OEM platform are you utilizing? have you updated the BIOS to the latest version, including the updated AMT Drivers? Have you enabled AMT in the BIOS? Have you gone into CTRL+P during the platform boot to validate AMT is working and in the correct mode?

On the vPro Expert Center we have a great deal of video's, tools & information from Pro's across the industry.. I look forward to hearing more about your setup.

Josh

I've done a little browsing through your doc that you sent me to.

We had never logged into the workstations and changed the AMT password. I'm not quite sure if this has anything to do with it not working properly or not. This just means that the BIOS and AMT settings are still the same as they were out of the box. It looks to me like everything is enabled that should be under the AMT settings, however I could be wrong.

I tried to browse to HP's website so that I could look for new drivers just in case, but that's going to have to wait for a little bit. The portion of the site to download drivers for our product appears to be having problems, but that's not an Intel issue

I'm going to try using the AMT commander management console again now that I've fooled around in the BIOS.

I've gotten it going! vPro rocks

Just as a quick demo for my supervisor and my fellow techies guys, I've set up roughly 30 or so machines for small business mode. I did remote SoL boot to BIOS setup from my office and reconfigured BIOS settings for my supervisor to see. "Very cool!" he said.

One thing I've noticed. Using the remote control features of AMT Commander, when the workstation has booted into Windows Vista, I do not get a display on the SoL session window. Is this normal behavior? I wouldn't really be surprised if it were isolated to Vista, being it's such a resource hog for pretty graphics. I do get a display on my SoL session when I reboot to bios setup. I haven't tried one of our XP workstations and have not yet tried booting off of a CD or floppy image

Regardless, this is really a great technology. I see lots of good things coming out of this and am quite happy to hear that my organization will be purchasing only vPro hardware in the future.

It's worth noting that SOL is exposed to Windows as a virtual COM port (usually COM3 from what I've seen). That means that applications could write to COM3 and the data will show up in the SOL display.

Dave

Well, we currently still aren't using this just yet too much. Once in a while I boot a computer off of a remote cd using AMT. AMT commander does work great, however everytime I try to use it, when I've boot off ot remote cd images, I can never seem to reboot the computer again using commander.

It's just not something we can widely adapt yet with our current infrastructure.

The boot CD that I am using is a DOS based cd that was created using Symantec GSS. This CD is one that we often use for reimaging workstations. Basically boots up, gets an ip from dhcp, loads up ghost, and connects to a server to deploy the OS.

We are actually moving away from the DOS based cd, however we need it sometimes. Only reason I tried using the DOS cd was because I was told graphical OS's wouldn't display on the AMT Commander terminal and that text based OS's would such as linux and dos. We're moving to a WinPE solution

Well like I said, it seems that when I boot up off of remote media I cannot do forced reboots using AMT commander.

Another thing I noticed, and I'm assuming it's related, when I boot up a computer to Windows, I can login to the AMT control panel webpage on the computer. When I'm booting off of external media, such as my DOS cd, I cannot login to the AMT webpage.