Setting up and configuring Intel
AMT in HP Business Notebooks,
Desktops, and Workstations
Detailed instructions for the IT professional
Table of contents
Executive summary 2
Setting up and configuring Intel AMT 4
Setup and configuration phases 4
Manual mode setup and configuration 4
Creating a password 5
BIOS prerequisites 5
Setup and configuration procedure 6
Using the WebUI 25
Enterprise mode setup and configuration 27
Using the TLS-PSK method 28
OEM TLS-PSK provisioning 29
Using a USB drive key for provisioning 29
Using the TLS-PKI method 30
Enabling TLS-PKI or TLS-PSK 32
Unprovisioning an Intel AMT system 36
Making a full return to factory default settings 37
Appendix A: Frequently asked questions 38
Appendix B: Overview of power, sleep, and global states 40
ME power states 40
Appendix C: Wake-On-ME overview 41
Appendix D: Supported certificates 42
Select HP models use Intel® vPro processor technology to simplify PC management and reduce IT-related expenditures. A key element of vPro is Intel Active Management Technology (Intel AMT), a platform-resident solution that includes both hardware and firmware, and relies on the Management Engine (ME) integrated into supported Intel chipsets.
Intel AMT provides out-of-band (OOB) remote access to individual systems regardless of power state or operating system condition – as long as the system is connected to a power source and a network. By default, Intel AMT is inactive; it must be setup and configured in order to enable its capabilities. There are two options for setup and configuration (also known as provisioning):
This white paper details the manual setup and configuration of a client PC (Intel AMT system), as well as discussing options and providing guidelines for enterprise-mode setup and configuration. Refer to the Intel website www.intel.com/technology/vpro/index.htm for other white papers and technical information on Intel vPro Technology.
Intended audience: This white paper is intended for IT administrators familiar with setting up and configuring manageability features. Basic knowledge of Intel AMT and networking are required.
Select HP Workstation, Desktop and Business Notebook PCs utilize Intel vPro Technology to simplify PC management, enhance security, and reduce IT-related expenditures. Intel vPro includes a range of technologies and components, including the following:
Resident on each client PC, Intel AMT enables out-of-band (OOB) remote access to the PC, regardless of the system power state or operating system condition – as long as the PC is connected to a power source and a network. By default, Intel AMT is shipped in an inactive state and must be setup and configured2 in the system before it can be used.
The following methods can be used for Intel AMT setup and configuration:
The SCS is a software application that is integrated into the remote console being used to manage client PCs. Consult the particular independent software vendor (ISV) for information on deploying an SCS.
Intel AMT technology is available on the following select HP models:
Remote access to a client PC can be wired or wireless, depending on the particular HP model.
– HP ZBook 17 Mobile Workstation
– HP ZBook 15 Mobile Workstation
– HP ZBook 14 Mobile Workstation
– HP EliteBook 850 G1 Notebook PC
– HP EliteBook 840 G1 Notebook PC
– HP EliteBook 820 G1 Notebook PC
– HP ProBook 650 G1 Notebook PC (select models)
– HP ProBook 640 G1 Notebook PC (select models)
Wired Intel AMT is supported with Integrated Intel 1217LM Gigabit Network Connection. Wireless Intel AMT is supported with Intel Centrino Advanced-N 6205, Advanced-N 6235 or Wireless-N 7260 802.11a/b/g/n or the Wireless-AC 7260 a/b/g/n/ac adapters.
– HP EliteDesk 800 G1 Ultra-Slim, Small Form Factor, and Microtower PCs
– HP EliteOne 800 G1 All-in-One PCs
– Z230 Tower and Small Form Factor
Setting up and configuring Intel AMT
Before it can be used, Intel AMT must be setup and configured, which involves the following activities:
Setup and configuration phases
The setup and configuration process involves the following phases:
In Factory phase, the system is initially as received from the factory; no Intel AMT setup and configuration has been performed. In this phase, you can only access Intel AMT locally, through the Intel Management Engine BIOS Extension (MEBx).3
Factory phase ends when the following occurs:
– Manual mode – You have changed the default password.
– Enterprise mode – You have changed the default password and set the Provisioning ID (PID) and Provisioning Passphrase (PPS).
The In-Setup phase is used to set most Intel AMT options,4 either manually or automatically, using an SCS.
The Operational phase is the final phase. Intel AMT has been fully setup and configured, making the system ready for normal use.
Manual mode setup and configuration
The Manual mode for Intel AMT setup and configuration is intended for customers that do not have an SCS or the necessary network and security infrastructures to use encrypted Transport Layer Security (TLS). Here, setup and configuration is performed manually through the MEBx.
Because less infrastructure is required, Manual mode is easier to implement than Enterprise mode; however, Manual mode is less secure because network traffic is unencrypted.
HP recommends performing a Manual mode setup and configuration in a closed network.
The remainder of this section provides prerequisites and guidelines for Manual mode setup and configuration.
The MEBx is not HP-specific and contains options that are not used by HP. Do not change unused options from their default state.
Creating a password
To reduce vulnerability to a dictionary attack, MEBx enforces the following minimum criteria for a password:
Note that the underscore character ( _ ) is considered alpha-numeric.
The following characters are not allowed:
– Quotation mark
– Less than
For best performance and to take advantage of AMT 9.x features, make sure the PC meets the following prerequisites:
The system BIOS and ME FW must be updated individually. For more information on flashing the system BIOS and ME FW, refer to the BIOS Flash white paper. Use the following steps to locate the document that applies to your particular system:
Intel AMT 9.x allows certain versions of ME FW to be downgraded to earlier versions, which may be useful for troubleshooting purposes.
Setup and configuration procedure
When you explore MEBx options for the first time (Factory phase), default settings are in place. This white paper details the settings recommended by HP, some of which may be the same as the default selections.
Even though the default setting is used for many options, it is good practice to double-check important options.
For setup and configuration, perform the following procedure:
For desktop PCs, by default, the Ctrl-P prompt is not displayed on the HP splash screen. This prompt can be displayed during POST if set in F10 Setup.
Workstation PCs do not provide a BIOS option to display the Ctrl-P prompt.
Figure 1. Selecting the MEBx password
Changing the password establishes Intel AMT ownership and moves the system from Factory to In-Setup phase. As a result, ME and Intel AMT options are now accessible within the MEBx; the system can be accessed via the Intel AMT WebUI (WebUI).
For information on using the WebUI, refer to Using the WebUI.
Figure 2. Selecting the Local FW Update option
Figure 3. Selecting the Local FW Update option
Unless otherwise specified, the system BIOS allows ME FW to be updated locally without password protection. If desired, you can modify the Local FW Update setting to enable password protection.
Figure 4. Local FW Update has been enabled
This option allows Intel AMT to be enabled (recommended) or disabled. By default, HP systems are set to enable Intel AMT.
Note that disabling Manageability Feature Selection also disables all remote management capabilities and unprovisions any Intel AMT settings.
Figure 5. Enabling Intel AMT via the Manageability Feature Selection setting
10. From the Intel AMT Configuration menu, select SOL/IDER/KVM.
The SOL/IDER/KVM screen appears, as shown in Figure 6. Review the following settings:
– Username and password: Enabled (Recommended setting; default)
When enabled, this setting allows users and passwords to be added via the WebUI; if it is disabled, only the
administrator has MEBx remote access.
– SOL: Enabled (Recommended setting; default)
This setting enables or disables Serial-over-LAN (SOL) functionality.
– IDER: Enabled (Recommended setting; default)
This setting enables or disables IDE Redirection (IDE-R) functionality.
– Legacy Redirection Mode: Disabled (Recommended setting; default)
This setting allows the redirection feature to work with a pre-Intel AMT 6.0 SCS.
– KVM Feature Selection: Enabled (Recommended setting; default)
This setting enables or disables the keyboard/video/mouse feature.
Figure 6. Configuring SOL/IDER/KVM settings
The User Consent screen appears, as shown in Figure 7. Review the following settings:
– User Opt-in: KVM (Setting is user-dependent; KVM by default)
– Opt-in Configurable from Remote IT: Enabled (Setting is user-dependent; Enabled by default)
This setting enables or disables a remote user’s ability to select user opt-in policy. If set to disabled, only the local user can control the opt-in policy.
Figure 7. Configuring user consent
This setting specifies when it is possible to change the MEBx password over the network.
The MEBx password can always be changed locally through the MEBx user interface.
As shown in Figure 8, options are:
– Default Password Only
You can change the MEBx password via the network interface if the default password has not yet been changed.
– During Setup and Configuration
You can change the MEBx password via the network interface during the setup and configuration process but at no other time. Once setup and configuration is complete, the password cannot be changed via the network interface.
– Anytime (recommended; default setting)
You can change the MEBx password via the network interface at any time.
Figure 8. Setting the password policy
The Intel ME Network Setup screen appears, as shown in Figure 9, allowing you to configure Intel AMT so that it can be accessed by a remote system.
Figure 9. Initiating the setup of the ME network
Figure 10. Setting up the ME network names
Review the following settings:
– Host Name: (Setting is user-dependent; there is no default)
Host names can be used in place of the system’s IP address for any application that requires this address.
Spaces are not acceptable in a host name.
Make sure there is not a duplicate host name on the network.
– Domain Name: (Setting is network-dependent; there is no default)
If a domain name is not specified, then the default domain name of Provisionserver will be used when connecting to the SCS.
If a domain name is not specified and the domain name for the SCS is not Provisionserver, you must set up an alias in the DHCP server to redirect the connection for Provisionserver to the appropriate domain.
If a domain name is specified, then that domain will be used. However, if there is no response after four DNS queries to the specified domain, Provisionserver will be used instead.
– Shared/Dedicated FDQN: Shared (Recommended setting; default)
This setting determines whether the Intel ME Fully Qualified Domain Name (FQDN) – that is, the HostName.
DomainName – is shared with the operating system or is in a separate domain.
– Dynamic DNS Update: Disabled (Recommended setting; default)
If Dynamic DNS (DDNS) update is enabled, the firmware will actively try to register its IP addresses and FQDN in DNS using DDNS update protocol. You must set the appropriate host and domain names; in addition, the MEBx menu displays the following options:
If DDNS update is disabled, the firmware will make no attempt to update DNS using DHCP option 81 or DDNS update protocol.
If DDNS update has not been set (that is, it is neither enabled nor disabled), the firmware will use DHCP option 81 for DNS registration; it will not directly update DNS using DDNS update protocol.
Intel AMT 9.x supports Internet Protocol version 4 (IPv4) and IPv6 interfaces, which are set up differently:
– IPv4: See Configuring IPv4.
– IPv6: The IPv6 option has been removed from the MEBx in Intel AMT 9.x. IPv6 (wired or wireless5) can be configured from an SCS or the WebUI. See Configuring IPv6.
Figure 11. Configuring TCP/IP settings
Select Wired LAN IPV4 Configuration and then configure the parameters shown in Figure 12.
Figure 12. Configuring the network for IPv4
– DHCP Mode: Enabled (Recommended setting; default)
If DHCP is enabled (recommended), skip to Step 16.
If DHCP is disabled, complete steps (i) – (v) of Implementing wireless connectivity for Intel AMT to configure an IPv4 static IP address for Intel AMT.
– IPV4 Address: (Network-dependent; default is 0.0.0.0 )
Specify the desired static IP address (such as 192.168.0.1). Ensure that each Intel AMT system has a unique IP address. Multiple systems sharing the same IP address may result in network collisions that would cause the systems to respond incorrectly.
Subnet Mask Address:
(Network-dependent; default is 255.255.255.0)
Default Gateway Address:
(Network-dependent; default is 0.0.0.0)
Preferred DNS Address:
(Network-dependent; default is 0.0.0.0)
Alternate DNS Address:
(Network-dependent; default is 0.0.0.0)
Both wired and wireless6 IPv6 can be enabled via an SCS or, as in this example, the WebUI.
Review the TCP/IPv6 settings for wired and wireless connections, as shown in Figure 13:
– Enable IPv6 (wired): Enabled (Recommended setting; default setting is Disabled)
– Enable IPv6 (wireless): (Implementation-dependent; default setting is Disabled)
Figure 13. Configuring wired and wireless networks for IPv6 via the WebUI
Implementing wireless connectivity for Intel AMT
Consider the following caveats:
– For desktop PCs, wireless Intel AMT is supported on EliteDesk 800 G1 Ultra Slim, Small Form Factor, and Microtower systems, and EliteOne 800 G1 All-in-One systems using the Intel Centrino Advanced-N 6205 mini PCI wireless LAN card or the add-on PCI Express x1 option card with Intel Centrino Advanced-N 6205.
– For business notebook PCs, wireless Intel AMT is supported on Intel Centrino Advanced-N 6205/6235 and Intel Dual Band Wireless-N 7260 802.11 adapters, and Intel Dual Band Wireless-AC 7260 802.11a/b/g/n/ac adapters; wired Intel AMT is supported on Integrated Intel 1217LM and 1218LM Gigabit Network Connection.
– Intel AMT only supports DHCP and does not support static IP addresses.
– Wired and wireless Intel AMT traffic cannot travel on the same subnet concurrently.
If you wish to use wireless Intel AMT connectivity, you must first connect to the Intel AMT system from a remote system using wired LAN in order to create a wireless profile. Carry out the following steps:
Figure 14. Specifying wireless power policy
iii. In the Profiles field box (Figure 15), click New to create a new wireless profile.
Figure 15. Selecting New to create a new wireless profile
iv. Enter the following data for the new wireless profile, as shown in Figure 16:
– Profile name:
Network name (SSID):
(the wireless network SSID name)
(implementation-dependent; default is WPA-PSK)
(recommended setting; default)
(wireless network pass phrase)
On completion, click Submit.
Figure 16. Configuring a new wireless profile
v. Select System Status to display the Wireless IP address, as shown in Figure 17.
Wireless Intel AMT only supports IPv6 addresses.
Figure 17. Verifying that you have configured a wireless IP address
A remote system should now be able to access the ME.
The Unconfigure Network Access option causes the ME to transition to the pre-provisioned state. For more information, refer to Unprovisioning an Intel AMT system or Making a full return to factory default settings.
Figure 18. Transitioning the ME to the newly-provisioned state
Figure 19. Selecting Power Control
Figure 20. Current Intel AMT ON in Host Sleep States setting
Figure 21. Options for Intel AMT ON in Host Sleep States setting
Recommended setting: Desktop: ON in S0, ME Wake in S3, S4-5
After you activate network access (Step 16), Intel AMT On in Host Sleep States is automatically set to Desktop: ON in S0, ME
Wake in S3, S4-5.
For more information on sleep states and Wake-On-ME, refer to Appendix B: Overview of power, sleep, and global states
and Appendix C: Wake-On-ME overview, respectively.
20. Select the appropriate Idle Timeout value for Wake-On-ME in minutes, as shown in Figure 22.
– Idle Timeout: 65535 (Recommended setting; default)
The timeout must be set to a non-zero value for the ME to take advantage of Wake-On-ME.
The timeout is not used when the system is in active state (S0); it is only used when the AMT ON in Host Sleep States setting is configured to allow Wake-On-ME.
Figure 22. Selecting the Idle Timeout value
Once the system reboots, it changes from Intel AMT In-Setup phase to Operational phase. Now, the system can be remotely managed through the WebUI or a remote console and can be provided to the end-user for regular use.
Using the WebUI
The WebUI is a browser-based interface that provides limited support for remote system management. It is often used to verify that Intel AMT setup and configuration has been performed properly on a system. Obtaining a successful connection between a remote system and the system running the WebUI indicates proper Intel AMT setup and configuration on the remote system.
The WebUI is accessible from the following web browsers:
Remote system management capabilities include:
WebUI support is enabled by default for Manual mode setup and configuration.
Connecting with the WebUI in Manual mode
– By default, the port is 16992
– If DHCP has been specified, then use the Fully Qualified Domain Name (FQDN) for the ME, which is a combination of the hostname and domain as in the following examples:
• Host names (see Host Name)
The remote system makes a TCP connection to the Intel AMT system and accesses the top-level web page embedded within the ME.
Figure 21. The WebUI System Status screen
You can use the WebUI to change the MEBx password (see Creating a password) for the remote system.
Changing a password in the WebUI or SCS results in the creation of two passwords for Intel AMT setup and configuration, with the new credential being known as the remote MEBx password.
The remote MEBx password only works remotely with the WebUI or SCS. The local MEBx password does not change.
If you create a remote MEBx password, you must now keep track of two passwords.
When the MEBx password is initially set in Intel AMT setup, it serves as both a local and remote password. In this scenario, passwords are synchronized; if you create a remote password, the passwords are now out of sync.
Enterprise mode setup and configuration
This section provides instructions and guidelines for Intel AMT setup and configuration (provisioning) in Enterprise mode.
Intel AMT is designed to support a range of SMB and enterprise provisioning scenarios that involve tradeoffs between security, cost, and convenience. At one end of the spectrum, it is possible to manually configure Intel AMT in a matter of minutes on a local machine. Alternatively, it is possible to configure a vast array of machines with Intel AMT in a large enterprise environment without physically touching these machines once; moreover, they can be configured in such a way that the process is trusted and secure, and not vulnerable to being attacked or snooped on by malware or prying eyes.
SMBs can perform all setup and configuration tasks manually, with no need for third-party software. However, enterprise IT departments typically automate the provisioning process by allowing Intel AMT systems to connect over the network to a setup and configuration server (SCS) application (such as Symantec Notification Server, LANDesk Management Suite, or Microsoft System Center Configuration Manager) that is integrated with the remote management console. Provisioning can then be achieved by establishing a secure Transport Layer Security (TLS) tunnel between the Intel AMT system and SCS, and then automatically downloading the necessary provisioning information to the Intel AMT system. Various levels of security are supported, including public-key infrastructure (PKI) and pre-shared key (PSK) implementations.
Intel AMT can support a range of provisioning scenarios:
Intel AMT offers a range of options for carrying out the actual provisioning:
Zero-touch provisioning uses the default MEBx setup.
Remote provisioning uses the TLS-PKI method and can be zero-touch at the client side. For more information, refer to Using the TLS-PKI method.
For more information, refer to Using the TLS-PKI method.
– OEM-TLS-PSK provisioning – HP supports zero-touch TLS-PSK provisioning by pre-configuring key Intel AMT settings at the factory. For more information, refer to OEM TLS-PSK provisioning.
Using the TLS-PSK method
TLS-PSK provisioning requires the Intel AMT system to possess a pre-shared key (PSK) in order to support authentication with the SCS. While the distribution of pre-shared keys adds complexity and cost, this method provides strong security.
To support PSK provisioning, Intel AMT and the SCS share a Provisioning ID (PID)/Provisioning Passphrase (PPS) set, which forms the PSK. Security can be further enhanced by allocating a unique PID/PPS set to each Intel AMT system.
Without dashes, PIDs have eight characters, while PPSs have 32 characters. Since there are dashes between every set of four characters, PIDs have a total of 9 characters, while PPSs have a total of 40 characters.
As soon as a PID/PPS set has been delivered to the ME – either manually via the MEBx or using a USB Key – the Intel AMT system starts looking for an SCS. The Intel AMT system continues to look for an SCS every time it is powered up until provisioning has occurred.
The provisioning process is as follows:
DHCP and DNS must be available for the SCS search to automatically succeed. If DHCP and DNS are not available, then you must manually enter the IP address of the SCS into the Intel AMT system’s MEBx.
The “hello” message contains the following information:
– UUID (Universally Unique Identifier)
– IP address
– ROM and FW version numbers
The “hello” message is transparent to the user; there is no feedback mechanism to tell you messages are being broadcast..
The initial “hello” message is unencrypted; however, all subsequent communications between Intel AMT system and SCS can be encrypted with TLS.
TLS is optional. However, if the infrastructure is available, you should use TLS for secure, encrypted transactions.
If TLS is not available, less secure HTTP Digest is used for mutual authentication.
The SCS looks up the appropriate PPS in its database7 and uses the PPS and PID to generate the premaster secret.
– New PPS and PID for future configuration
– TLS certificates
– Private keys
– Current date and time
– HTTP Digest credentials
– HTTP Negotiate credentials
Other options can be set depending on the particular SCS implementation.
The system goes from In-Setup to Operational phase; Intel AMT is fully operational. Once in Operational phase, the system can be remotely managed and is ready to be given to an end-user for regular use.
Enabling TLS-PSK provisioning
For information on enabling TLS-PSK provisioning on an Intel AMT system, refer to Enabling TLS-PKI or TLS-PSK.
OEM TLS-PSK provisioning
To reduce the burden on local IT staff, the information required to enable TLS-PSK provisioning can be pre-configured at the factory. OEM TLS-PSK provisioning is performed in the following stages:
During OEM manufacturing
During manufacturing, HP sets up Intel AMT8 and ships the customer a system that is already in In-Setup phase.
If desired, the admin password, PID, and PSS can be generated during manufacturing and transferred to the customer in a separate, secure fashion. Alternatively, customers can provide their own admin password, PID, and PPS to be used by HP for a particular order.
At the customer’s location
The customer receives In-Setup systems along with the PIDs, PPSs, and password information needed by the SCS. The systems are connected to the network and powered up, allowing remote provisioning to take place automatically.
Some SCSs may require additional settings, such as a port number and IP address. Contact the ISV for more information.
If desired, the SCS can generate a new PID/PPS combination to replace the combination configured by HP.
Using a USB drive key for provisioning
This is a zero-touch provisioning method that eliminates the errors that can occur when manually typing entries. Password, PID, and PPS information is loaded to the MEBx on system boot using a specially formatted setup.bin file. After this information has been loaded, the Intel AMT system starts requesting provisioning.
A USB drive key must meet the following requirements to support USB drive key setup and configuration:
Using the key
The following are typical stages in the use of a USB drive key:
– If a key is detected, the BIOS looks for a setup.bin file; if this file is found, the BIOS continues with Step 7.
– If a key is not detected – or if a key is detected but no setup.bin file is found – the system boots normally; no Intel AMT setup and configuration is performed.
Refer to the ISV for your SCS for more information on USB drive key setup and configuration.
Using the TLS-PKI method
Remote provisioning of Intel AMT systems is achieved using the TLS-PKI method.
By default, HP EliteDesk 800 G1 Business PCs are shipped ready for remote provisioning (that is, no changes to the MEBx are required). The MEBx is pre-configured to support PKI; thus, all that is required to initiate provisioning is an agent that can be pushed over the network to Intel AMT systems whenever convenient.
TLS-PKI provisioning uses Public Key Infrastructure with Certificate Hashes (PKI-CH) protocol to maintain security; a DHCP environment is required.
Thus, no pre-shared key is required with TLS-PKI provisioning; instead, authentication is mutual. The Intel AMT system maintains default hashes in firmware for a number of certificates; alternatively, you can add your own hashes (see Appendix
Creating a secure connection between the Intel AMT system and SCS requires a certificate, which is used for encryption rather than authentication. If you do not wish to use a third-party certificate, you can use the SCS to create a self-signed certificate. The SCS uses the public key from the certificate to encrypt the session key it generates and sends to the Intel AMT system, which can decrypt the session key using its private key.
Since the Intel AMT system is already running an OS, provisioning can take place at any time. The local agent contacts the SCS, which responds by telling the Intel AMT system to provide a one-time password (OTP).9 Once a TLS connection has been established, the SCS can begin provisioning the Intel AMT system.
The OTP is created and encrypted by the ME and is then sent to the SCS.
Delayed network access
TLS-PKI provisioning utilizes delayed network access; that is, provisioning does not commence as soon as the Intel AMT system is first powered up. In this implementation, provisioning can be initiated after an OS has been installed and a local agent has been pushed over the network to the Intel AMT system.
In this implementation, remote provisioning begins when the SCS is able to communicate with the ME through the Intel Host Embedded Controller Interface (HECI) driver, which requires a functional OS and agent to be installed on the Intel AMT system.
Consult the management console ISV for more information on OS agents that provide delayed remote provisioning support.
Enabling TLS-PKI provisioning
For information on enabling TLS-PKI provisioning on an Intel AMT system, refer to Enabling TLS-PKI or TLS-PSK.
Setting the remote configuration timeout
HP EliteDesk 800 G1 Business PCs are shipped with a Remote Configuration Timer that is set to 0, which effectively disables “hello” message broadcasting. Enabling the ME to broadcast “hello” messages requires the use of an Intel local agent.
The remote configuration timeout was omitted from subsequent HP Compaq Elite 8×00 and EliteDesk 800 Business PCs.
Consult the management console ISV for more information on delayed remote configuration timeouts.
The local agent typically configures ME to broadcast “hello” messages for six hours while the ME is active and the system is connected to a network. If there no response from an SCS within the timeout period, the network interface that is sending out “hello messages” is disabled. It can be re-enabled by one of the following methods:
Prerequisites and caveats for TLS-PKI
TLS-PKI provisioning requires the following prerequisites to be met:
– Unique Intel AMT OID value in the Extended Key Usage field is 2.16.840.1.1137184.108.40.206
– OU value in Subject field is Intel Client Setup Certificate
This OU value is case-sensitive and must be entered exactly as shown.
Enabling TLS-PKI or TLS-PSK
Remote provisioning via TLS-PKI or TLS-PSK may require you to manually specify certain network and security settings on the Intel AMT system unless you use a USB key to provide the appropriate information.
Carry out the following steps to manually configure an Intel AMT system that is already in In-Setup phase:
Skip the Activate Network Access and Unconfigure Network Access menu items.
Figure 22. Transitioning from Intel AMT setup to configuration
Figure 23. Menu used to enable remote provisioning
– Current Provisioning Mode
This menu item is used to display the provisioning mode currently selected. Options are:
No changes can be made at this menu.
– Provisioning Record
This menu item is used to display the data in the system’s provisioning record. The default setting is Not Present; no changes can be made at this menu.
The record for a system with PKI provisioning includes the following data:
The provisioning record for a system with PSK provisioning includes the following information:
Remote Configuration (RCFG) is an Intel AMT feature that allows a single OEM OS image to provision systems securely, without the need to manually modify Intel AMT options.
RCFG has the following requirements:
– Provisioning Server IPv4/IPv6
This menu item is used in Enterprise mode to point to the IP address of the SCS. The default is 0.0.0.0.
If the IP address is left at its default value, the ME will look for ProvisionServer on the DNS.
Some SCS products may require additional settings, such as the port number10 and IP address. Contact the particular ISV for more information.
– Provisioning Server FQDN
This menu item is used in Enterprise mode to specify the Fully Qualified Domain Name (FQDN) of the SCS, which is network-dependent. There is no default.
– TLS PSK
Select this menu item in order to configure TLS-PSK via the Intel TLS PSK Configuration screen, shown in Figure 24.
Figure 24. Configuring TLS–PSK provisioning
– Set PID and PPS
This option allows you to specify a provisioning ID (PID) and provisioning passphrase (PPS). Values are system-dependent; there is no default.
Without dashes, PIDs have eight characters, while PPSs have 32 characters. Since there are dashes between every set of four characters, PIDs have a total of 9 characters, while PPSs have a total of 40 characters. If you do not wish to enter the PID or PPS manually, you can use a USB key that contains the appropriate information (see Using a USB drive key for provisioning).
The admin password, PID, and PPS can be pre-populated by HP during manufacturing. Refer to the OEM TLS-PSK provisioning section for more information.
Legacy (zero-touch) provisioning uses a default certificate; no PID or PPS are needed. PKI is active in the base image, which contains 15 pre-installed certificates.
– Delete PID and PPS
This option is used to delete the current PID and PPS entries and should be skipped.
After configuring TLS-PSK, return to the previous menu.
– TLS PKI
Select this menu item in order to configure TLS-PKI via the Intel Remote Configuration screen,11 shown in Figure 25.
Figure 25. Configuring TLS-PKI provisioning
– Remote Configuration
This option enables (recommended; default) or disables TLS-PKI provisioning.
– PKI DNS Suffix
This option allows the PKI DNS suffix for the SCS to be specified.
– Manage Hashes
This option shows the hashes that are in the system, providing names and status (active/inactive). If there are no hashes in the system, you are given the option to add hashes; if hashes are available, you are given the option to delete one or more. For more information on supported certificates, refer to Appendix D: Supported certificates.
In Intel AMT 9.x, the MEBx allows you to manually activate a hash and use up to three additional certificate hashes. To add a hash:
The system displays a single Intel ME Configuration Complete message and reboots.
After you plug the system into a power source and make the network connection, the automated migration from In-Setup phase to Operational phase can commence.
Only use the integrated Intel NIC to make the network connection. Intel AMT does not work with other NIC solutions.
Unprovisioning an Intel AMT system
If desired, you can unprovision an Intel AMT system that has been setup and configured. Use the Unconfigure Network Access option on the Intel AMT Configuration menu, as shown in Figure 26.
Figure 26. Selecting the Unconfigure Network Access option
Having selected Unconfigure Network Access, you can select one or both of the following unprovisioning options depending on how the Intel AMT system has been provisioned:
Available for systems provisioned in Manual or Enterprise mode, full unprovisioning returns all Intel AMT configuration settings to their factory defaults. All certificate hashes are deleted; the default hash is made active.
This option does not reset all ME configuration settings (such as network settings) or the MEBx password.
Only available for systems provisioned in Enterprise mode, partial unprovisioning returns all Intel AMT configuration settings to their factory defaults with the exception PID, PPS, and PKI-CH settings.
This option does not reset ME configuration settings or the MEBx password.
Partial unprovisioning re-opens the network interface for six hours of “hello” message broadcasts.
Approximately a minute after you select the desired unprovisioning option, the caution shown in Figure 26 appears.
On completion, control is passed back to the Intel AMT Configuration screen. Notice that the Activate Network Access option (Figure 8) is again available.
After return to the previous menu and exiting, the system will reboot.
Making a full return to factory default settings
F10 setup provides an option that allows you to fully unprovision the ME to factory defaults. Use the Unconfigure AMT/ME option, which is located under the Advanced/AMT Configuration menu.
The unconfigure option clears CMOS, thus returning all MEBx settings to factory defaults; for example, the password is reset to admin.
Following the unconfigure, the system must be setup and configured again before remote management is possible. Any non-default certificate hashes will have to be re-applied.
Appendix A: Frequently asked questions
Q: How can I access the MEBx locally?
Q: Why isn’t the Ctrl-P prompt displayed during POST?
Workstation PCs do not provide a BIOS option to display the Ctrl-P prompt during POST.
A: Clearing CMOS resets all MEBx options including the password, which reverts to its default setting, admin.
Q: How can all MEBx options be restored to factory defaults?
Q: What happens if the wrong password is entered multiple times?
Q: Is TLS required?
A: No, TLS is optional.
Q: If TLS is not implemented, then what is used for authentication?
A: If TLS is not implemented, HTTP Digest is used for mutual authentication.
Q: Where can I get an SCS?
Q: Can Intel AMT be set for a static address while the OS is set for DHCP or vice versa?
A: The WebUI listens to port 16992.
Q: Does Intel AMT provide wireless LAN support?
Certain HP Business Notebook PCs and Mobile Workstations featuring the appropriate adapters can support wireless Intel AMT. See Support.
Wireless Intel AMT is not supported on HP Workstation PCs.
Appendix B: Overview of power, sleep, and global states
Under the Advanced Configuration and Power Interface (ACPI) specification, a PC may be in one of the following power states (also known as Sleep (Sx) or Global (Gx) states).
S0 (also known as G0) is the On state, during which the PC is fully functional. All system devices and the operating system, if available, are running.
S3 is the Standby (Microsoft® terminology) or Suspend-to-RAM state. The memory subsystem and Vaux power rail remain powered, while the remainder of the PC – including the processor – is not powered. After resuming from S3, the system context is still intact because system memory was powered at all times.
S4 is the Hibernate (Microsoft terminology) or Suspend-to-Disk state. The system context is saved to the hard drive as a hibernation file; when the PC resumes from S4, the system context is restored from this file.
During S4, Vaux remains powered; all other subsystems – including system memory and the processor – are not powered.
S5 (also known as G2) is the Soft Off state and is identical to S4, except that the system context is not saved. When the PC resumes from S5, it powers up and goes through POST.
G3 is the Mechanical Off state, during which all PC subsystems are powered off. The easiest way to achieve this state is by removing utility power from the PC by unplugging the power cord.
ME power states
The ME has its own power states (Mx), as follows:
M0 is the On state for the ME; the PC is in S0 state. The ME is fully powered and running.
M3 is the On state for the ME; the PC is in a non-S0 state. The ME is fully powered and running.
Moff is the Off state for the ME; the PC is in a non-S0 state.
The ME can be set to stay powered-on and active in all Sx states. In this scenario, if the PC is in S0, then the ME will be in the corresponding M0 state; however, if the system is in S3, S4, or S5, the ME remains active but migrates to M3 state.
Appendix C: Wake-On-ME overview
Wake-On-ME, also known as ME Wake-on-LAN (ME WoL), is a feature that allows the ME to go into a low power state when it is not being used but awaken if required. The ME counts down from the amount of time set in Idle Timeout before going to sleep.
The following condition must be met for Wake-On-ME to function:
Appendix D: Supported certificates
The following are supported certificate authorities and certificates (see also Figure D-1):
Not all certificates may be populated in certain configurations.
Figure D-1. Supported certificate authorities and certificates
Resources, contacts, or additional links
Intel vPro Technology
Sign up for updates hp.com/go/getupdated
Share with colleagues Rate this document
© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Microsoft is a registered trademark or trademark of Microsoft Corporation in the U.S. and/or other countries. Intel, Centrino, Core, Active Management Technology (Intel AMT), and vPro are registered trademarks or trademarks of Intel Corporation in the U.S. and/or other countries. All other product names mentioned herein may be trademarks of their respective companies.
742409-002, June 2013, Updated September 2013