Many engineers and end-users ask "Why do I need Intel AMT?" I can do X, or Y already...
If you're somewhat familiar with Intel AMT - you understand some of the complexities in setting up an enterprise environment to support the Intel AMT model. You also have a day-to-day support model where pre-AMT solutions are being utilized, and are familiar with how Intel AMT can simplify your IT life.
What roadblocks do you foresee in setting up an Intel AMT supported environment?
What legacy support models do you use for remote management?
What benefits do you hope to utilize (or are currently using) with your new Intel AMT infrastructure?
There is no 'one-way' to provide end-point support, and I hope to get some creative converstation on how your environment works and showcase the benefit of implementing Intel vPro Processor Technology into your current infrastructure vs. future support models and help clarify usage for Intel AMT.
Our biggest roadblock might be a non-issue: I can't find any documentation onf the vPro site for Linux. Does vPro support Linux? It seems like so much of vPro's selling point is its awareness of software and OS changes, but can that also be applied to Linux?
Hi Walter and welcome to the vPro experts center.
For most of the iAMT features of vPro you do not necessarily need OS support. Things like network filters, remote power on, serial-over-LAN terminal and IDE redirection work on a hardware level and do not require the OS to be iAMT aware.
There are also drivers for features that do require OS support, like agent-presence checking and the third party data store, on http://www.openamt.org .
If you want to use vPro (iAMT) features from a Linux server, I suggest you take a look at Syam. (http://syamsoftware.com/ Or you just Google for other Linux based management consoles)
Alex and Todd,
Thanks for the welcome and great links. I did know that there were many sub-OS features of vPro. This is similar to the (usually server-based) network management ports that have been around for a while now.
But some of hardware vendors have been marketing vPro, talking about software stuff, and my Linux inquiries have been drawing blank stares. I think on most of pre-packaged marketing stuff, Linux doesn't have a presence on the slides I've been seeing.
I will check out the resources you mention though, for sure.
Walter - great question! There has been some activity in the linux open source community, http://www.openamt.org/ has just released the official AMT tools and drivers for Intel vPro based systems last friday. http://communities.intel.com Yilan Saint-Hilaire (an active member of Open Port) has reported out that http://softwareblogs.intel.com/2007/08/20/intel-amt-dtk-v037-released-amp-audio-blog/ AMT Commander is starting to get some usage on Linux and MacOS.
First attempt at running Commander on Linux and MacOS. This new version for DTK includes a new folder called "MonoEdition" and source code includes a new "Debug-Mono" compiler target in an attempt to run Intel AMT Commander on the MONO framework. http://www.mono-project.com/ MONO is an open source project attempting to build a compatible Microsoft .NET framework on Linux. So far, only a very limited version of Commander can run on MONO 1.2.4 within Microsoft Windows, and no luck running on Linux yet. It's likely that with the release for MONO 2.0 later this year, Commander will run pretty well.
Today, Intel http://www.intel.com/pressroom/archive/releases/20070827comp.htm?iid=pr1_releasepri_20070827m released their latest version of Intel Active Management Technology (codename "Weybridge"), so keep your browser tuned to the Intel vPro Processor Technology drivers section for updates soon!