Hi, I'm planning to make a USB3.0 class driver(KMDF) with WDK8.1 for my PC that has an Intel chipset. 

Details of my PC:
  Model: DELL Optiplex 9020
  OS: Windows 7 Professional 32bit SP1
  Chipset: Intel Q87 Express
  CPU: Intel Corei7
 
Can I make a class driver for my PC ?
If not, how about another Windows 7 PC that has an another Intel Chipset ?
Thanks

If you’re not familiar with PSM I’d recommend having a look to the introduction presented by Gael in this post: http://intel.ly/MW65v6, there you’ll get a fairly good understanding on what the tool is and how to use it. By the time you finish reading the previous reference you’ll notice that the preconfigured plugins perform tasks such as Alarm Clock, Asset Inventory, Event Log, IDE-Redirection, KVM Remote Control, Power Management and Serial Over Lan, however other functionalities like Agent Monitoring aren’t present.

For those scenarios the plug-in development is the alternative to follow. In order to develop a plugin you should go through the following 5 steps:

1. Download and decompress the latest version of The PSM here: http://intel.ly/1fk6AFr (released on: 01/20/2014).
2. Create a WPF UserControl project in Visual Studio. PSM needs references to the following DLL’s:  System.Xaml, PresentationCore.dll, PresentationFramework.dll and WindowsBase.dll. Then add a reference to the object model defined by PSM in the library SolutionManagerAPI.dll and to the visual aspects included in SolutionManagerWPF.dll.
3. Add a class which derives the SolutionManagerPlugin and implement its abstract members. You’ll end up with something similar to the following class:

    public class AgentMonitor_Impl : SolutionManagerPlugin
    {
        ctrlAgentMonitor ctrl = null;

        public override void ExecuteNoUI() { }

        public AgentMonitor_Impl()
        {
            _properties.Icon = Plugin_AgentMonitor.Resource1.AgentIcon;
            _properties.Name = "Agent Monitor";
            _properties.Category = Categories.MISC | Categories.AMT;
        }

        public override bool RequiresAMT
        {
            get
            {
                return true;
            }
        }        

        public override System.Windows.Controls.UserControl PluginWPFControl
        {
            get
            {
                lock (this)
                {
                    if (ctrl == null)
                    {
                        ctrl = new ctrlAgentMonitor(this);
                    }
                }
                return ctrl;
            }
        }

        public override SolutionManagerPlugin CreateInstance()
        {
            return new AgentMonitor_Impl();
        }
    }

The previous code sets the plugin properties in the constructor (e.g.: icon, name and category) and exposes its visual elements in the PlugWPFControl property, which implements the singleton design pattern. This property should return your own UI control, so you can use anything inheriting from UserControl, however the PSM includes a ctrlWPFBase class which gives you a good starting point to define your own control.

1. Add a WPF user control to the project and change its base class from UserControl to ctrlWPFBase in the code behind and XAML files. This class is defined as follows:

    public partial class ctrlAgentMonitor : ctrlWPFBase
    {

        public ctrlAgentMonitor(SolutionManagerPlugin plugin)
            : base(plugin)
        {
            InitializeComponent();
            _plugin = plugin;
        }

        private bool _isLoaded = false;
        private void ctrlWPFBase_Loaded(object sender, RoutedEventArgs e)
        {
            if (!_isLoaded)
            {
                //One time stuff here
                ListWatchdogs();
            }
            _isLoaded = true;
        }

        private void btnRefresh_Click(object sender, RoutedEventArgs e)
        {
            ListWatchdogs();
        }

        /// <summary>
        /// Function to load a list of watch dogs
        /// </summary>
        private void ListWatchdogs()
        {
            IWSManClient wsmanClient = new DotNetWSManClient(_plugin.System.Fqdn, "admin", _plugin.System.Password,
                                                             _plugin.System.UseTls, false, null, null);
            WatchdogWrapper client = new WatchdogWrapper();
            var list = client.List(wsmanClient, null);            
            if (list != null)
            {
                lstAgents.DataContext = list;
            }

            
        }        
    }

For simplicity some functions were omitted. The most important functions are the injection of the plug in object via constructor arguments and the call to your custom code in the Loaded event. The plugin object is quite useful because gives you access to several properties/functions which abstract AMT functionalities/use cases. In this example the plugin object is used to get the machine’s FQDN, the password and other settings required to establish a second connection with the device to get the list of the watchdogs created in that machine.

By setting the DataContext object the data source object (a List<> in our case) is enumerated to match the property names of the objects contained in the collection with binding paths as described in the following XAML fragment:

<GridView >
                        <GridViewColumn x:Name="Id"   Header= " Id" DisplayMemberBinding="{Binding Path=Id}" />
                        <GridViewColumn x:Name="Name"  Header=" Name"  DisplayMemberBinding="{Binding Path=Name}" />
                        <GridViewColumn x:Name="State"  Header=" State"  DisplayMemberBinding="{Binding Path=State}" />
                    </GridView>

1. Once the code is done (and tested), copy the obtained DLL after compiling the WPF UserControl project onto The PSM’s plugin folder (usually: C:\Program Files\Intel Corporation\Intel(R) vPro(tm) Platform Solution Manager\Bin). Then run The PSM and test the new Agent Monitor plugin by selecting the “A” icon as described in the following image. Note that agent’s watchdogs are loaded in the collapsible sidebar.

General tips for building a custom Plugin:

• Use the .Net Framework version 3.5 because is the version used by The PSM.
• If planning to copy/paste a existing WPF user control to build yours make sure to change the XAML Build action to Page in the properties Windows to regenerate the InitializeComponent method (more information here: http://bit.ly/1cN7oWM).

Thinks I enjoyed/liked building a plugin for PSM:

• It’s simple. It’s not overcomplicated with plugin frameworks.
• The plugin object injected in the constructor provides access to virtually all AMT functionalities.
• The PSM’s UI. Also it feels fast and nicely asynchronous in ALL its operations.

Things I think can be that improved:

• The Real VNC plugin does not time out, it just keeps trying to connect “forever”.
• It’s not evident that the machine list is not saved automatically. It should be the default setting. Also the Settings > Options menu is not easy to reach.
• The PSM is highly modularized, and that’s a good thing. However the required DLLs can increase quickly.  For this simple plugin the following DLLs were required: DotNetWSManClient.dll, CIMFramework.dll, CIMFrameworkUntyped.dll, DotNetWSManClient.dll, IWSManClient.dll and HLAPI.dll. It would be great if all those DLLs would be provided as s single distributable DLL. This can be done using a tool like ilmerge (more information here: http://wp.me/p17pRQ-gm).
• The plugin object is quite handy, however for this plugin I actually could not find the object/function which provides that data, I thought was the following (but it wasn’t):

List<Agent> recordlist = _plugin.System.Password.AmtSystemInstance.AgentPresence.Remote.GetAllAgents();

The plugin object seems a bit like an ADO.Net DataSet object because is massive, it includes several properties which in turns include several properties and so on, like a Russian doll.

The code used for creating the plugin and to access the watchdog list via WS-Man are attached.

Javier Andrés Cáceres Alvis

Intel Black Belt Software Developer

Microsoft Most Valuable Professional – MVP

I have been experiencing persistent problems with my system (DVD drives not working, excessively long boot sequences etc) for some time now. A recent fresh install of Windows 7 seemed to do the trick but now the problem is back.

I have just noticed that the Intel Management Engine Interface is showing a yellow error

This device cannot start. (Code 10)

Any ideas as to the cause

Hi all,

I have Troubles to Log in into AMT Web UI, I can access to the login web page, but I can't login with the default user "admin" and my MBEx password.

All the info is in the last post of this tread: http://software.intel.com/en-us/forums/topic/292757 

Please Help, 

Brand new install of Intel SCS v9.0.23.10 in non-database mode. Need to do zero touch to a lot of far away AMT v9.0 clients.

After launching the Intel SCS console and stepping through the configuration profile wizard to "Transport Layer Security", a little blue "i" says:

"The CA plugin option is not available because a CA plugin was not loaded"

Where is this CA plugin option so a certificate can be purchased and used?

Good morning, 

I have a test environment where i am trying to configure SCCM 2012 and OOB. 

I have configured the OOB service and logged into the IME and configured it with the correct HASHS and enabled the network.

When trying to provision the AMT sccm logs: DoConnectToAMTDevice: Failed to establish tcp session to 192.168.0.13:16993

I can connect via the web browser on 16992 but not 16993 - I have attached my amtopmgr.log file, as you can see at the top it connects once and detects the AMT but it then reverts back to undiscovered. 

Any help would be appreciated. 

Thanks, Lee

Having trouble logging into the Intel AMT WebUI after you are certain everything has been configured correctly?  Did you recently start using a different keyboard or perhaps you are using a VM that was created with US-based language settings?  There are many different QWERTY (and QWERTZ) keyboards in use world-wide.  Below is just an example of 3 (US QWERTY, UK QWERTY, and German QWERTZ.) 

The issues when accessing the Intel AMT Web UI or the MEBx on an Intel AMT system starts with the BIOS/MEBX screens in that they expect key sequences that are based on the US QWERTY-based keyboard. This can be a big problem if the "@" symbol is one of your favorite special characters to use in your MEBx password.  For example, let's take a look a where the @ symbol is on 3 different keyboards:

• US-QWERTY:  @ is Shift-2
• German-QWERTY:  @ is AltGR-Q
• UK-QWERTY: @ is Shift-'

This is just one issue. Many keyboards have special characters as well, such as German umlauts (Ä, Ö, Ü, ä, ö, ü.)  If you suspect that you may be having a keyboard issue, you will need to enter your password in terms of the layout the US QWERTY keyboard.

In summary, if you are having issues accessing Intel AMT and you are certain you are typing in your password correctly, check the following items:

• Your keyboard - are you using a different keyboard (that has international differences?)
• How about your Host OS or VM?  Make sure your OS/VMWare environment is set with the correct Regional and Language settings.

Hi everyone,

I have been research about small project.

Following

- Power On a computer using Intel vPro chip through LAN. My program at Linux platform remote to computer using vPro chip through LAN. I'm using      'AMT_Implementation_and_Reference_Guide'. https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm

 and I implemented 'Change Power State' computer using vPro chip.It's ok.

So, I just power On button on computer using vPro but I try set a [PowerOn password] of vPro comuputer at BIOS configuration. The dialog box will appear at vPro computer's BIOS Screen When vPro computer powerOn and require input a [PowerOn password] which i have been set before.

- I can't pass my [PowerOn password] from Linux platform to vPro computer's BIOS Screen. i have been test and debug with API, class, method,... which Intel SDK provided. For Example: 

 + CIM_BootSettingData

 + CIM_PowerManagementService

 + Get Password Model

 + CIM_BootConfigSetting

 + ...

Anyone can help me,  

thanks you and best Regards

>Hi all.

I want to describe information about my application on Linux management:

Purpose: I want to bypass the BIOS password from Linux system to Window system. Following functional:

 1. Check power State of vPro system:

     + Reference url (https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm?turl=WordDocuments%2Fgetsystempowerstate.htm)

     + I have implemented' CIM_AssociatedPowerManagementService.PowerState' object to get powerState of vPro system. 

2. Change powerState (PowerOn) vPro system:

     + Reference url       (https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/WordDocuments/changesystempowerstate.htm)

     + Retrieve the instance of Cim_PowerManagementService and call this method Cim_PowerManagementService.RequestPowerStateChange with  following parameters:

• powerState: One of the defined power states
• Managed Element: A reference to the "managed system" object
• Time: NULL
• TimeoutPeriod: NULL

3. Problem:

   + Currently, the state of the option [PowerOn password] in vPro BIOS configuration must be "ON" (required).

   + When vPro is turned on, it requires user to input [PowerOn password] and i have to input the password manually. So my question here is:

   - Can I set the [PowerOn password] in the PowerManagementService object so when i use my application to turn on vPro, it will bypass the input [PowerOn password] screen and instantly move to the log in screen of the OS ? Is there any other way to bypass this input [PowerOn password] screen ?

Thank you for your help.

Thank you for your interest in the Intel® Active Management Technology (Intel® AMT) High-level API Technology.

Introduction

Introduction to the High-level API Intel Management Library Technology

Intel® Active Management Technology (Intel® AMT) is a capability embedded in Intel-based platforms (in an Intel AMT device). Intel AMT enables remote access to platforms even when the operating system is not available or the platform is turned off. The only requirement is that the platform must be connected to a power supply and a network.

Software developers can include support for Intel AMT features in their applications to enhance the ability of organizations to manage their computing facilities.

The Intel AMT High Level Application Programming Interface (HLAPI) provides software developers with a simple interface to the Intel AMT features.

Supported Features:

This version of the Intel AMT High Level API is also included in the latest Intel AMT SDK and supports the following Intel AMT features:

1.  ACL (Access Control List) Management
2. PET -event subscription
3. PET-event/ WS-event listener
4. Simplify events subscription API
5. Agent Presence remote and local
6. Power & Boot Operations
7. Get Intel AMT/Host FQDN
8. Redirection (SOL & IDER)
9. KVM Administration
10. Alarm Clock
11. Hardware Asset
12. System Defense
13. Time synchronization
14. WS-Event subscription
15. Network Administration
16. Agent Presence
17. Certificate Management
18. Wireless
19. Remote Access (also known as CIRA)

The API download includes C# samples for all features. There are also JavaScript samples that demonstrate the COM interfaces. Compatible with Intel AMT versions 2.2 and above.

Documentation

• Intel® AMT High Level API Unzip the documentation and open default.htm in the root directory.
• For more information please see the Release Notes.
• HLAPI Demo Learn how to include support for Intel AMT features in you application

* Please note that the terms of the software license agreement included with any software you download will control your use of the software.

Download

Thank you for your interest in the Intel® Active Management Technology (Intel® AMT) Software Development Kit. The Intel® AMT SDK (Software Development Kit) contains the building blocks and documentation material needed to develop software that interacts with Intel® AMT systems.

Overview

Intel® Active Management Technology (Intel® AMT) is a capability embedded in Intel-based platforms that enhances the ability of IT organizations to manage enterprise computing facilities. Intel AMT operates independently of the platform processor and operating system. Remote platform management applications can access Intel AMT securely, even when the platform is turned off, as long as the platform is connected to line power and to a network. Independent software vendors (ISVs) can build applications that take advantage of the features of Intel AMT using the application programming interface (API).

The Intel AMT SDK includes the Intel® AMT High Level API (Intel AMT HLAPI) as well as the Intel vPro Platform Solution Manager. The Intel AMT HLAPI provides a very simple and consistent API across all Intel AMT versions/SKUs enabling software developers to easily build support for Intel AMT features into their applications. For more information, see the HLAPI documentation.  The Intel vPro Platform Solution Manager is a Management console that was built from the Intel AMT High Level APIs. The source code is included in this package.

Download the most recent update to the Intel® AMT SDK and get everything you need to develop manageability applications.

New Features included with Intel AMT/SDK Release 10:

MOFs and XSL Files

The MOFs and XSL files in the \DOCS\WS-Management directory and the class reference in the documentation are updated to version 10.0.25.1048.

OOB Screen Blanking

The ability to remotely blank out the client remote console screen during updates and administrative activities was added in the HLAPI and the KVM application tool.

New WS Eventing and Pet Table Argument Fields

Addition arguments were added to the CILA alerts to provide the reason for the UI connection and the hostname which generated the alert.

Updated Real VNC

The Real VNC version has been updated to v1.2.5 in Linux and KVM.

Updated Root Certificate Length

The supported root certificate length has been extended to 2500 bytes.

Windows Connected Standby / Instant Go Support

Windows connected standby, also known as Instant Go, operations are supported on Windows 7 and above.  Intel AMT support uses the term power saving state and generates UNS events. This capability was also added in the HLAPI.

Graceful Power Operation Support

Graceful power operations are supported on Windows Vista, 7, and 8 32 and 64-bit platforms, including from Windows 8 connected standby / Instant Go, and generate UNS events. This capability was also added in the HLAPI.

Secured FQDN Provisioning Support

Provisioning in both Admin and Client Control Modes with secured FQDN is now supported.

Notes:

• WLAN provisioning with USB Key will not allow TLS enablement on LAN-less platforms in Intel AMT Release 9.5.
• The C++ samples fail to compile on Windows* 7 and Windows Server 2008 R2 due to a bug in the Windows SDK function mt.exe. For further information and workaround see the Windows 7 SDK: Beta Release Notes. Note that a file compiled on other Windows operating systems, such as XP or Vista, will also execute on Windows 7 and Windows Server 2008 R2.
• The "Configure Default KVM Port" script sets the RFB password. This script contains WinRM commands and may change the user's WinRM configuration.
• Microsoft WinRM - Intel AMT interrupt on associations: The WinRM client fails to perform a retrieval or delete of an instance of an association class using an EPR when its selectors are also EPRs. An example where this capability is needed in Intel AMT is the System Defense association AMT_ActiveFilterStatistics.
• Redirection library provides AES 256 cipher suites as an option although only AES 128 ciphers are supported by Intel AMT.
• UCT Tool: Cannot delete or update the application settings file while the application is running.
• Because of limitations within the Tight VNC application (a third-party application for KVM), asterisks will not appear when entering the opt-in code. In addition, while Intel AMT will respond to keyboard and mouse actions, these will not show in the client until the user refreshes the display.
• Samples and other applications which use signed dll are loaded very slowly. This can occur because .NET Framework repeatedly attempts to verify the signed DLL files, even when there is no internet connection.

Known Issues:

• 1. Redirection library: The Linux version of the redirection library does not support IDER over DVD.
  2. Redirection library: Cannot write a to floppy diskette.
  3. Redirection library: Trying to connect without first configuring the CIRA settings may result in a Timeout error after the CIRA settings are configured.
  4. Redirection library: The IDER session may close unexpectedly in the following scenario:  IDER and SOL sessions are open and sending data from the console to the Intel AMT in S3.  The user then wakes up the Intel AMT to S0 and during the wake up, the user enables the IDER registers.
  5. KVM: The KVM Control application uses the firmware version to determine how many display pipes are supported, rather than how many are actually available.
  6. KVM:  When working with Linux library and using the scancode extension, the caps lock; number lock and Alt+ key events on the console side are not forwarded to the server.
  7. KVM:  When opening the Windows Start menu on a remote console, the menu opens on both the management and remote consoles when KVMControlApplication is implemented over default or redirection ports.
  8. KVM:  Rapid changes in display color levels while a KVM session is running could result in a session disconnection.  Restart the KVM session to reconnect.
  9. KVM:  A KVM session may return a 404 error resulting in a session disconnect .  This can occur after sending HTTP traffic over CIRA and wireless connection or if the KVM session is left open but inactive.  Restart the KVM session to reconnect.
  10. WS-EVENTING:  In AMT 5.2 the HLAPI does not parse the header to 63 characters.  As a result,  when a long string is entered, the HLAPI will fail to create a subscription.

Copyright and Trademarks (C) Intel Corporation, 2004 - 2014
Other names and brands may be claimed as the property of others.
 

Getting Help

• Need more help? Refer to the FAQs or get expert advice from the Developer Discussion Forum
• For more information, see the release notes.

Additional Information

• Intel® AMT SDK Documentation
• Download Microsoft Windows* Platform SDK

Resources

• The Intel Business Client Developer's Community
• The Intel Business Client Community Forum
• Intel® Active Management Technology Use Cases
• Intel® Active Management Technology (Intel AMT) Software Development Kit (SDK) Start Here Guide
• Intel® Active Management Technology Brief

Hi

We're replacing our laptop clients with a new model from HP (EliteBook 1040-G1). In total we're going to deploy more than 2500 new clients. The clients provides AMT functionalities, however, we don't want to use it and also the user should not be able to activate it. Therefore, we would like to set a strong password instead of using the default password. Is there a way to change the default password automatically during the staging/provisioning process without manual interaction?

Kind regards,

Daniel

Contents

Introduction 
What is new with the Intel® AMT Release 10.0
Preparing your Intel® AMT Client for use
Manual Configuration Tips
Client Control Mode and Admin Control Mode
Accessing Intel® AMT via the WebUI Interface
Intel® AMT LMS, UNS, and IMSS
Intel® AMT Software Development Kit (SDK)
Other Resources

Introduction

Intel® Active Management Technology¹ (Intel® AMT) is part of the Intel® vPro™ technology² offering. Platforms equipped with Intel AMT can be managed remotely, even if the operating system is unavailable or the system is turned off. Intel® AMT-enabled systems have special out of band network access through the Intel® Wireless(or wired) network connection allowing remote platform management applications secure access as long as the platform is connected to line power and to a network. Independent software vendors (ISVs) can build applications that take advantage of Intel AMT features using the Intel AMT SDK which includes the Intel AMT High Level API (Intel AMT HLAPI) which provides a very simple and consistent API across all AMT versions and Intel SKUs. For more information, see the HLAPI documentation in the SDK.  The SDK also contains the Intel vPro Platform Solution Manager, which is a management console that was built from the Intel AMT HLAPIs.
Intel AMT uses a number of elements in the Intel vPro platform architecture, most notably the Intel® Management Engine (Intel® ME), part of the firmware (supplied by the system manufacturer with the BIOS). The firmware uses a small portion of system RAM, which is why slot 0 must be populated and powered on for the firmware to run. It also has its own Flash storage that holds the configuration settings among other information.

Note: To use Intel AMT out of band management, the system must have an Intel® Ethernet or Intel Wireless Network Connection that supports connections to the Intel ME firmware. 
Note that for Intel AMT 10.0, the platform will require a 10.x version of the Intel ME Firmware and driver. The 10.0 driver set can be loaded on systems that shipped with 8.x. 9.x or 10.0 firmware.  You should always use the firmware provided by your system manufacturer.

Intel AMT supports remote applications running on Microsoft Windows* or Linux* but supports only Windows-based local applications. For a complete list of system requirements, please refer to the documentation in the latest Intel® AMT Software Development Kit (SDK) and the Intel® AMT Implementation and Reference Guide located in the Docs folder.

What is new in the Intel AMT Release 10.0:

 Note: Intel AMT 10 is backward compatible to systems using the Intel® 7, 8, and 9 series chipsets.

• The most important change:   OpenSSL* is now implemented with no heartbeat flag. So on systems being upgraded to AMT10, please revoke and reissue the certificates and change passwords. 
• Blanking the Screen of the Intel AMT client (during remote access) was added in the HLAPI and KVM application tool.
• Updated MOFs and XSL files as well as the class reference are now version 10.0.25.1048.
• The Real VNC* version has been updated to v1.2.5 in Linux and KVM.
• Windows Connected Standby*/Instant Go are supported in Windows 7 and above (also available in the HLAPI)
• Graceful power operations are supported on Windows Vista, 7, and 8 32 and 64-bit platforms, including from Windows 8 connected standby / Instant Go, and generate UNS events. This capability was also added in the HLAPI
• Provisioning in both Admin and Client Control Modes with secured FQDN is now supported
  For more information, see the release notes.

Preparing your Intel AMT Client for use  

Configuration (provisioning) of an AMT client involves moving the client through setup and configuration mode into operational  mode. To get into SetupMode requires initial information (which varies by AMT versions) set by the system manufacturer.  The Intel AMT capability is enabled using the Intel® Manageability Engine BIOS extension (Intel® MEBx) as implemented by the system provider. A remote application can be used to perform enterprise setup and configuration. Various setup methods exist based on the AMT version. For more information see the Setup and Configuration documentation.

AMT Releases                                       Setup Method  
1.x; plus 2.x, 3.x in legacy mode            Legacy
2.x, 3.x, 4.x, 5.x                                      SMB
2.0 and later                                           PSK
2.2, 2.6, 3.0 and later                             PKI  (remote)      
6.0 and later                                          Manual      
7.0 and later                                          Client Control Mode and Admin Control Mode
10.0                                                       Secured FQDN is now supported

 Intel® Setup and Configuration Software (Intel® SCS) is capable of provisioning systems back to Intel AMT 2.X. For more information about the Intel SCS and provisioning methods as they pertain to the various Intel AMT Releases, visit: Download the latest version of Intel® Setup and Configuration Service (Intel® SCS)

Manual Configuration Tips

Manual configuration can be accomplished though the Intel MEBx menu which should be available right after the BIOS startup screen - usually by pressing <Ctrl+P>. Some BIOS provide the option to hide the <Ctrl+P> prompt. 

To manually set up an Intel AMT client, perform these steps:

1. Enter the Intel MEBx default password (“admin”).
2. Change the default Intel MEBx password to a new strong password (required).  It must be at least eight characters and contain at least one upper case letter, one lower case letter, one digit and one special character. Note: A management console application can change the Intel AMT password without modifying the Intel MEBx password.
3. Select Intel® AMT Configuration.
4. Select Manageability Feature Selection.
   1. Select ENABLED to enable Intel® AMT.
5. Select SOL/IDE-R/KVM and enable all of these features. Enabling Legacy Redirection Mode ensures compatibility with management consoles created to work with the legacy SMB mode that did not have a mechanism implemented to enable the listener. Note that if SOL/IDER/KVM features are not enabled in the Intel MEBx, they will not be available to management consoles.
6. Select User Consent
   1. Select desired options for KVM and Remote IT operations. Enabling User consent means that anytime the Intel AMT Client is to be accessed remotely the user will need to agree.
7. Enter Network Setup to enter network preferences for the Intel ME.
8. Enter Activate Network Access to enable Intel AMT.
9. Exit to the Main Menu.
10. Select MEBx Exit to continue booting your system.

The platform is now configured. You can set some additional parameters using the Web User Interface (Web UI) or a remote console application.

Admin Control Mode(ACM) and Client Control Mode (CCM)

When any method of setup completes, Intel AMT 7.0 and later versions are placed into one of two control modes:

Admin Control Mode – After performing setup using the Intel MEBx menu or remote configuration, Intel AMT enters Admin Control Mode. In this mode, there are no limitations to Intel AMT functionality since there was a high level of trust associated with these setup methods.

Client Control Mode – Intel AMT enters this mode after performing a basic host-based (local) setup . This mode limits some of Intel AMT functionality, reflecting the lower level of trust required to complete a host-based setup. The following limitations apply:

1. The System Defense feature is not available.
2. Redirection actions (IDE-R and KVM but not the initiation of an SOL session) and changes in boot options (including boot to SOL) require user consent in advance. This still enables IT support personnel to remotely resolve end-user problems using Intel AMT.
3. If an Auditor is defined, the Auditor’s permission is not required to perform unprovisioning.
4. A number of functions are blocked from execution to prevent an untrusted user from taking over control of the platform.
   
   Note: The ability to configure a headless platform remotely without the need for local user-consent was added as of AMT 9.0.

Accessing Intel® AMT Clients

An administrator with user rights can remotely connect to an Intel AMT client via the Web UI by entering the IP address or FQDN of the client followed by the port number into the browser URL:  Use http and port 16992 when TLS is NOT configured and https and port 16993 with TLS. :      

           For example: http://134.134.176.1:16992     or     https://amtsystem.domain.com:16993

To access the Intel AMT client using Serial Over LAN (SOL), you must ensure the SOL driver is installed. 

Intel AMT Local Manageability Service (LMS) & User Notification Service (UNS)

The Local Manageability Service (LMS) runs locally in an Intel AMT device and enables local management applications to send requests and receive responses to and from the device. The LMS listens for and intercepts requests directed to the Intel AMT local host and routes them to the Intel ME via the Intel ME Interface driver.

Note that as of Intel AMT 9.0, the User Notification Service is combined with the Local Management Service. The UNS registers with the Intel AMT device to receive a set of alerts. When UNS receives an alert, it logs it in the Windows “Application” event log. The Event Source will be Intel® AMT.

The Intel Management and Security Status (IMSS) tool

The IMSS tool can be accessed by the “blue key” icon in the Windows tray.

The General tab of the IMSS tool shows the status of Intel vPro services available on the platform and an event history. Other tabs provide additional details.

The Advanced tab of the IMSS tool shows more detailed information on the configuration of Intel AMT and its features. The following screen shot verifies that Intel AMT has been configured on this system.

Intel AMT Software Development Kit (SDK)

The Intel® AMT Software Development Kit (SDK) provides the low-level programming capabilities to enable developers to build manageability applications that take full advantage of Intel AMT.

The Intel AMT SDK provides sample code and a set of APIs that let developers easily and quickly incorporate Intel AMT support into their applications. The SDK also has a full set of documentation. The SDK supports C++ and C# on Microsoft Windows and Linux operating systems. Refer to the User Guide and the Readme files in each directory for important information on building the samples. 

The SDK is delivered as a set of directories that can be copied to a location of the developer's choice on the development system. Because of interdependencies between components, the directory structure should be copied in its entirety. There are three folders at the top level: one called DOCS (documentation), and one each for Linux and Windows (sample code.) For more information regarding how to get started and how to use the SDK, see the "Intel® AMT Implementation and Reference Guide.”

Below is a screen shot of the Intel AMT Implementation and Reference Guide. For more information on system requirements and how to build the sample code, read through the “Using the Intel® AMT SDK” section. The documentation is available on the Intel® Software Network here: Intel® AMT SDK (Latest Release)

Other Intel AMT SDK Resources

The Intel AMT SDK provides frameworks and samples that simplify WS-Management development and demonstrates how to take advantage of the advanced product features. For more information, see the following:

• High Level API
• Intel vPro Platform Solution Manager

There are a variety of development environments for which to write software that supports Intel AMT. The Intel vPro Enablement Tools are available only in C++ (C# wrapper in SDK) and require COM object by Microsoft. (not just .NET). Also note: SOAP support has been completely removed from the SDK as of AMT 9.0. 

About the Author

Colleen Culbertson is an Application Engineer in Intel’s Developer Relation Division Scale Enabling in Oregon. She has worked for Intel for more than 15 years. She works with various teams and customers helping developers optimize their code.

Intel, the Intel logo, and vPro are trademarks of Intel Corporation in the U.S. and/or other countries.

Copyright © 2014 Intel Corporation. All rights reserved.
*Other names and brands may be claimed as the property of others.

¹ Intel AMT requires activation and a system with an Intel network connection, an Intel® AMT-enabled chipset,  and software. For notebooks, Intel AMT may be unavailable or limited over a host OS-based VPN, when connecting wirelessly, on battery power, sleeping, hibernating or powered off. Results dependent upon hardware, setup and configuration. For more information, visit Intel® Active Management Technology.

²Intel® vPro™ Technology is sophisticated and requires setup and activation. Availability of features and results will depend upon the setup and configuration of your hardware, software and IT environment. To learn more visit: http://www.intel.com/technology/vpro.

Hi all,

We're sorry to have inconvenienced you. We posted some thread. We don't spam. We want clarify information about my application again. 

---

We have run into a problem while trying to create an application that can turn on the Intel vPro PC (Windows OS) from another PC (Linux). In detail:

1. Requirement

We were creating an application on Linux that can turn on another Intel vPro PC (Windows OS) (like Wake-On-Lan) with the following conditions:

    - The Intel vPro PC should enable the [PowerOn Password] option in its BIOS (so when the PC is turned on, it requires user to input a password in order to access the computer).

    - Directly remote to Intel vPro PC is unpermitted (ex: using VNC to remote to vPro PC) because of services order.

2. Progress

    - We are using the Intel AMT SDK library.

        i. We call the method "RequestPowerStateChange" from class "CIM_PowerManagementService" to turn on the power of Intel vPro PC.

        ii. When the PC is turned on, we have to input the PowerOn password on the console screen in order to proceed to Windows (because the       [PowerOn Password] option is enabled).

3. Target

    - The PowerOn password of vPro Pc is provided and set in the Linux Pc application.

    - We are willing to automatically input this password from Linux PC to vPro PC when we run our application. 

    Our target is:   If the set password is correct, the below process will be done automatically.

        1. We turn on the vPro PC.

        2. The PowerOn password will be automatically input.

        3.  The process will go to the Windows Logon.

        (which mean there will be no console screen to input PowerOn password)

4. Question

-> Therefore, we want to ask if the current Intel AMT SDK has any class or method that can handle this process ? 

We have been searching from the SDK Home Page but still have not found anything that can help us solve this problem.

We really appreciate any help you can provide.

Thank you.

This blog has a video tutorial associated with it as well click HERE to watch.

Intel® Active Management Technology (Intel® AMT) is part of the Intel® vPro™ technology offering. Platforms equipped with Intel AMT can be managed remotely, even if the operating system is unavailable or the system is turned off. Intel® AMT-enabled systems have special out of band network access through the Intel® Wireless(or wired) network connection allowing remote platform management applications secure access as long as the platform is connected to line power and to a network. Independent software vendors (ISVs) can build applications (Management Consoles) that take advantage of the Intel AMT features using APIs provided in the Intel AMT SDK

The Intel AMT SDK also includes code snippets that can be run with Microsoft PowerShell. Intel AMT features can be accessed by copying and pasting the code snippets provided in the Intel AMT SDK into a PowerShell template. The template requires connection information for a previously configured Intel AMT platform in order to run. The snippets require that the Intel vPro Scripting Library is installed on the platform where the snippets are executed.

To install the Snippet Library:

• Navigate to the following folder:  <SDKRoot>\Windows\Common\WS-Management\ IntelvProModule\x86 or x64 for the  install files.
• Execute the appropriate msi version for your environment.
• The installation does not require any special responses.
• The DLL and associated Snippet files are installed in the following directory: C:\Program Files\Intel Corporation\PowerShell\Modules\  
• A silent installation of Intel vPro Module msi is possible by using the /quiet switch and running it with admin privileges.  
• In an admin rights cmd window enter the following for a silent installation:  c:\IntelvProModule-x64.msi/quiet.

PowerShell Template

See Intel AMT SDK Implementation and Reference Guide for Installation Instructions

It is very simple to use the snippets provided by the Powershell installation - you simply insert them in the template where it says:

And then run it. You may need to check your system configuration if it doesn't work: Configure your system to run the Intel vPro Powershell Module

Some snippets use Snippet Functions to perform repetitive steps.  The Intel AMT SDK provides two snippet functions - ConvertToBase64 and ComputeMD5.

Here are some more resources on using Powershell:

• Configure your system to run the Intel vPro Powershell Module
• For more information on the Intel(r) vPro Module for Powershell: http://www.intel.com/go/powershell
• Customize the AMT GUI in the Intel® vPro™ PowerShell* Module: PowerShell GUI Overview Video

If you don't have much time, check out our 6 second vine:

Be sure to follow us on Twitter:

• @IntelTim
• @GaelHof

Hi,

I am using 'Win32_PNPSignedDriver' WMI class (Windows Management Instrumentation) for retrieving information from Device manager.

In that list "Intel(R) Management Engine Interface"driver information like (DeviceName, DriverVersion, Signer, Issigned) looks empty. But I can able to see the same information in device manager through manual.

This issue happening in version 7.1.70.1198 and until 9.*.*.*, but this issue was fixed in the latest version 10.0.30.1054

Kindly let me know, Why is this happened? and How is this fixed?

Thanks,

Rajadurai

Hi All, i'm not yet developing into AMT, but just playing around AMT configuration of my simple system.i have these working properly now:

home PC --> router --> ADSL modem --> physical phone line --> internet <--office network <-- office PC

i don't have TLS so in RealVNC+ i'm just using no encryption. port 9 is open for Wake-On-LAN via internet, ports 16992-16995 is open too. all those ports are open in win7 firewall as well. the router is configured as an AccessPoint so I port forward those ports to the PC with AMT (let's say it is 192.168.1.100). I have also made the .100 PC DMZ'ed. The ADSL also port forwards all those ports to the .100 PC. the ADSL is configured to give static DHCP .100 to a specified MAC address (which is the same .100 PC). my AMT config is shared with host, wait 3mins before power down, set for On in S0, ME Wake in S3, S4-5.

so, everything is working with RealVNC+ in the office. I can power up remotely using WOL via internet magic packets sent to MAC address in my FQDN. i know it is on, because i can see the MEBx webUI of my FQDN:16992. I can connect to my Home PC with KVM, power it down, power it on again without problems. I know the home PC is powering down/up because I can see my personal website (I had IIS configured to display simple html) or not see the webpage (as the case maybe when i turn it off via KVM)

the problem begins when during KVM i decide to make the home PC sleep (S3/S4/S5). I check my website and indeed it is down. so i send WOL magic packet and in a few minutes, I can see my website back up again. however, MEBx port is closed. I can tell because FQDN:16992 is unreachable. How can this be? my PC is on but MEBx is off? how come shutdown/power up is ok? Is there anyone who knows about a solution for this? anyone who has the same set up as mine can try and confirm SLEEP to WAKE is problematic?

i'm using IMB-850-L motherboard by Asrock (it is Q87), running latest drivers, AMT 9.0. I have a FSP power supply (Raider 550W 80+ bronze) that supports i7 socket 1150 S6/S7 sleep state if that could be a problem?

right now i can live with not using sleep (costs money anyway, however small) :D   but it just bugs me that I could hit that sleep in different places in win7 that I could not recover from :( remotely speaking, that is.

thanks  for any information

I'm searching for a comprehensive list of, or links related to, ME features are available for Intel systems that don't have vPro. Specifically I have a set of HP Elitebook 720s, 740s, 820s, and 840s. I saw the post by Colleen Culbertson,  Intel AMT, ME, MEI, and Windows Instant On/Connected Standby/ where she said “Back in the old days, one only needed to think about ME (Intel^® Manageability Engine) Firmware if one was using Intel^® Active Management Technology (AMT) on Intel^® vPro^TM Technology systems.  But some form of ME is now found on most Intel client architecture based systems including the need for an interface driver between the OS and the hardware (previously called HECI, now called the MEI (Manageability Engine Interface) driver.) " This got me very curious about what I could do on my Intel laptops that aren't vPro. Can anyone point me to any resources related to this?

I'm searching for a comprehensive list of, or links related to, ME features are available for Intel systems that don't have vPro. Specifically I have a set of HP Elitebook 720s, 740s, 820s, and 840s. I saw the post by Colleen Culbertson,  Intel AMT, ME, MEI, and Windows Instant On/Connected Standby/ where she said “Back in the old days, one only needed to think about ME (Intel^® Manageability Engine) Firmware if one was using Intel^® Active Management Technology (AMT) on Intel^® vPro^TM Technology systems.  But some form of ME is now found on most Intel client architecture based systems including the need for an interface driver between the OS and the hardware (previously called HECI, now called the MEI (Manageability Engine Interface) driver.) " This got me very curious about what I could do on my Intel laptops that aren't vPro. Can anyone point me to any resources related to this?

Hi All,

Have come across a very frustrating problem with out AMT 8.x systems where the install fails due to the installed version of C++  2010 Redistributable either being a later or equal version to the one that the AMT install package is trying to install. It appears that the installer does not check that C++ is installed or even the version and just dumbly starts the install every time resulting in the error (0x13EC) as the logs show below. The only workaround I have found is to uninstall the current version using a batch file then let the AMT package install it again however that has it own set of issues due to SCCM having a dependence on the same version of C++.

This issue is holding up the entire roll-out and I am struggling to believe others have not experienced similar issues however aside from a few minor mentions there is nothing out there.

Thanks.

IntelAMT.log

------

Executing 'C:\WINDOWS\ccmcache\s\DAL\vcredist_x86.exe /q'

Flags: Wait=yes Hidden=no

!   Process returned 0x13EC

IIF will NOT initiate reboot

Exit code = 0x13EC

ResultCode = 5100

Version:

MEI:8.0.0.1262

SOL:8.0.0.1262