Skip to content

Intel AMT Endpoint Management ​

Intel AMT lets you inspect firmware, control power, open a remote console, and use boot media even when Windows or the Ordyn agent is offline. The device must have power and network connectivity, and its assigned AMT client must be connected.

Open Hardware > Intel AMT on an endpoint to review its configuration and management state. Provisioning and recovery also require its Windows agent to be online. See firmware compatibility for the AMT versions verified with Ordyn.

Device Requirements ​

Before provisioning, prepare:

  • a device with Intel AMT 11 or newer enabled in firmware
  • a supported 64-bit Windows installation with the Ordyn agent running
  • the manufacturer's Intel Management Engine Interface (MEI) driver and Local Manageability Service (LMS)
  • a wired IPv4 connection reachable by the assigned AMT client
  • the tenant's AMT infrastructure and an assigned Intel AMT configuration profile

See Windows MEI and LMS Prerequisites for driver installation and verification. Ordyn does not install BIOS, Intel firmware, or OEM driver updates.

A Wi-Fi adapter is unnecessary. Ordyn configures wired AMT networking; Wi-Fi, VLAN, 802.1X, and IPv6 configuration are unsupported. Linux endpoints can report basic AMT inventory, but provisioning requires Windows.

Understand the Device State ​

The overview separates firmware capability, provisioning, ownership, configuration compliance, and management connectivity. A provisioned device can still be unreachable, and a running Windows agent does not confirm that AMT is reachable.

Use ownership to choose the next step:

OwnershipWhat to do
UnmanagedSelect Provision to check readiness and provision the device.
ExternalAdopt the existing configuration using its current AMT administrator password.
ManagedUse AMT actions and the configuration profile to maintain the device.
Recovery requiredCheck recovery state before choosing how to continue or reset the configuration.

AMT Availability ​

The violet AMT indicator in the endpoint sidebar shows recently verified AMT connectivity. It is independent of the agent connection, so AMT can be available while Windows is offline.

If management connectivity is unavailable, check the AMT client's connection and the address on the endpoint's Intel AMT network interface. An unknown state can also mean that Ordyn could not verify the device's certificate or credentials. Review the endpoint guidance and operation history for the next step.

Configuration Profiles ​

Create an Intel AMT configuration profile with the required control mode, managed DNS suffix, wired IPv4 mode, firmware consent policy, and power package.

  • Client Control Mode (CCM) requires local user consent for protected operations and does not need an activation credential.
  • Admin Control Mode (ACM) supports the selected consent policy. Entering ACM requires an activation credential and matching trust installed in firmware.

Assign the profile to a tenant, folder, endpoint group, or endpoint. Audit only checks managed devices and reports differences. Remediate also provisions ready unmanaged devices and applies the profile to managed devices. Only one AMT profile applies; see configuration profile assignment for precedence.

Use Check now or Remediate now in the endpoint's configuration-profile actions for an immediate assessment or change. An authorized administrator can request one-time remediation for an audit-only assignment. External devices need adoption first, and interrupted configurations need recovery.

Disabling the profile stops AMT management and certificate maintenance while leaving firmware configured. Removing the assignment also leaves the firmware configuration in place. Use deprovisioning to remove it. The firmware WebUI remains available on managed devices.

Wired IPv4 Configuration ​

ModeUse it when
Shared DHCPAMT should receive an address through DHCP on the shared wired interface.
Shared static IPv4AMT should use the same static address as an active Windows interface.
Dedicated static IPv4AMT needs its own static address.

For either static mode, save a desired network plan in the endpoint's Intel AMT overview with the address, prefix length, gateway, and DNS servers. Provisioning or configuration remediation applies that plan. The current management address and desired address are shown separately until the change succeeds.

The endpoint's Network interfaces section contains its Intel AMT interface. Its current address is the one used for management and can differ from the Windows address. Administrators can correct it manually. To discover changed addresses automatically while Windows is offline, configure AMT address discovery through IPAM.

Preflight and Provisioning ​

  1. Assign the Intel AMT configuration profile and prepare the device requirements above.
  2. For ACM, apply the setup.bin for a matching activation credential if its trust is not installed in firmware.
  3. Select Intel AMT > Provision. This also enables the assigned AMT profile for this endpoint if disabled.
  4. Resolve any reported blockers and select Provision again.
  5. Wait for completion and confirm that ownership is managed and AMT connectivity is available.

Provisioning and adoption automatically check the firmware, network and activation prerequisites when needed. Run Preflight separately for a full diagnostic report, including optional firmware history and wireless information, without provisioning. With the profile enabled, Remediate now can start provisioning.

Provisioning can take several minutes. Keep the Windows agent, AMT client, and device network connected until it finishes. Use the endpoint's History to review the operation result. If it requires recovery, follow the recovery workflow before retrying.

AMT 11–13 Provisioning ​

For ACM on AMT 11–13, use an RSA-2048 / SHA-256 compatibility activation credential. Apply its setup file so the firmware trusts the root and uses the same DNS suffix as the credential and configuration profile.

These devices require a working local LMS service and an enabled wired connection with DHCP for activation. Firmware can report 0.0.0.0 before activation; the endpoint still needs a valid address on its shared wired Windows interface. A static AMT network plan can be applied during provisioning after activation.

These activation requirements also apply when moving from CCM to ACM. Adopting a device already in the selected control mode does not require another activation setup.

Firmware Certificates ​

Use Hardware → Intel AMT → Certificates to check activation trust and management certificate validity. Collect fresh observations through preflight or Inspect when troubleshooting; a failed collection can leave older results visible.

See Intel AMT Certificates and Renewal for renewal and expiry recovery.

Firmware Events ​

Select Collect firmware events in the endpoint's Intel AMT menu, then open Hardware > Intel AMT > Firmware events to review firmware message and audit records. Available logs depend on the device. Stored history remains available if a later collection fails.

Adoption, Recovery, and Deprovisioning ​

Detect an External Management Identity ​

If a provisioned device's management identity has changed, set its current AMT administrator password in the endpoint secret variable hardware.intel_amt.admin_password, then run Inspect. Ordyn can recognize a configuration owned by another management environment after verifying access to the expected device.

Inspection does not take ownership or change firmware. Use Adopt to bring an externally managed device under Ordyn management.

Adopt an Existing Configuration ​

Use adoption for a device already provisioned in CCM or ACM. You need its current AMT administrator password, which can differ from its MEBx password.

  1. Assign an Intel AMT profile in Remediate mode with the device's existing control mode.
  2. Set the endpoint secret variable hardware.intel_amt.admin_password to its current administrator password.
  3. Bring the Windows agent and assigned AMT client online.
  4. Select Intel AMT > Adopt. Ordyn checks readiness and discovers the AMT address when needed, then continues adoption automatically.

Adoption applies the profile, installs an Ordyn device certificate, and rotates the administrator password to a unique managed value. It preserves the control mode, activation trust, AMT users, and access-control entries. An Ordyn setup file is unnecessary for adoption in the same control mode.

Existing firmware certificates are removed

Adoption replaces the firmware certificate store, including certificates and keys installed by other management systems. Features that depend on those certificates, such as certificate-based 802.1X or CIRA, require separate reconfiguration.

Use full deprovisioning if existing users, access rules, and custom activation trust must also be removed. If you do not know the current administrator password, use the manufacturer's local MEBx or firmware recovery procedure before provisioning with Ordyn.

Forget a Registration in This Environment ​

Use Intel AMT > Forget when a device is managed elsewhere and you want to remove its AMT registration from this Ordyn environment. Use the AMT Administrator role. The device can be offline; finish active AMT operations and close console sessions first.

Forgetting disables the endpoint's AMT profile and clears its current stored administrator credential. Device configuration, installed certificates, and management by other environments stay unchanged. Operation history and variable value history are retained.

A device that remains provisioned is shown as External. To adopt it again, enable its AMT profile and supply its current AMT administrator password. Use deprovisioning when you want to remove the firmware configuration.

Recover an Interrupted Operation ​

When an operation is interrupted, Ordyn may be unable to confirm how much of the configuration firmware accepted. Keep the Windows agent online and select Check recovery state in the Intel AMT overview. This obtains a fresh firmware observation so Ordyn can offer the available recovery actions.

Follow the resulting guidance:

  • Use Resume to continue an incomplete configuration when recovery is possible.
  • Use Roll back to abandon an incomplete setup. If the check reports Setup Mode, follow its rollback guidance before provisioning again.
  • If the check confirms that the device is unprovisioned, address any remaining preflight requirements and provision again.

A recovery check does not guarantee that provisioning can restart. A configured device still needs authenticated recovery. If Ordyn cannot verify its credentials or identity, use local MEBx or the manufacturer's recovery procedure, then check recovery state again.

After rollback or deprovisioning, allow firmware to finish resetting and follow any remaining recovery guidance before provisioning again.

Deprovision and Reprovision ​

Choose the reset that matches your goal:

ActionUse it toWhat remains
Partial deprovisionRemove the active configuration and operational certificates before provisioning again.The AMT administrator password and activation trust.
Full deprovisionRemove the configuration, AMT users, installed certificates, and custom activation trust.AMT stays enabled; Ordyn removes the stored managed administrator credential.

Neither action changes the MEBx password or deletes reusable activation credentials and tenant certificate authorities from Ordyn. A device in Setup Mode needs rollback first.

To reprovision:

  1. Select Partial deprovision or Full deprovision from the endpoint's Intel AMT menu.
  2. Wait for confirmed completion. If completion is uncertain, check recovery state first.
  3. For ACM, apply a setup file if the required activation trust was removed. Partial deprovisioning normally preserves that trust.
  4. Select Provision. It enables the assigned Intel AMT profile for this endpoint when disabled and checks readiness when needed. The profile must use Remediate mode.
  5. Resolve any reported blockers and retry provisioning.

Deprovisioning disables the profile to prevent automatic reprovisioning. It stays disabled until you provision explicitly or enable it in Configuration Profiles.

Reset and Reprovision an Adopted Device ​

Adopt an externally managed device before using Ordyn's partial or full deprovisioning actions. Once adoption succeeds, follow Deprovision and Reprovision. Without valid administrator credentials, use the device's local firmware recovery procedure.

Credentials and Recovery Bundle ​

Ordyn retains two distinct endpoint secrets:

  • hardware.intel_amt.admin_password: the AMT administrator credential used for management. Use the credential-rotation action to change the device password. Editing the variable alone changes only the value stored in Ordyn.
  • hardware.intel_amt.mebx_password: the intended MEBx password supplied when generating a setup file. Its presence does not prove that the file was applied successfully.

An AMT Administrator can download a recovery bundle from the endpoint's Intel AMT menu. It includes device identity, retained administrator credentials, the MEBx value, and public certificates for recovery outside Ordyn. Keep it in a protected password vault or encrypted offline location and download a fresh copy after credential or certificate rotation.

Deleting an endpoint or tenant leaves its AMT firmware configured while removing its Ordyn records. Deprovision first if the firmware configuration should be cleared, or retain a recovery bundle if it must remain manageable outside Ordyn.

Immediate Actions and Jobs ​

Use the endpoint's Intel AMT menu for management actions and History for their results. Actions that communicate with firmware require a connected AMT client. AMT job tasks support inspection, power, one-time boot, and media workflows; a job can wait for the client within its deadline.

Combine Job Operator with AMT Operator or AMT Administrator for the target scope. Select media available to your role. KVM and SOL are interactive consoles and cannot run as job tasks.

Remote Power ​

Use the endpoint's Power menu for supported AMT power actions. Prefer graceful shutdown when the operating system should close cleanly. An unconfirmed graceful shutdown does not force the power off; investigate before retrying.

Power-off and power-cycle operations can interrupt console and media sessions. See Powering on endpoints for method selection.

One-Time Boot ​

Select a next-boot target supported by firmware, such as local disk, PXE, redirected media, or BIOS setup. The setting applies to one boot; it does not change persistent boot order or restart the device.

Read-Only Redirected Media ​

Select Mount image in the KVM console to attach an Ordyn ISO or raw IMG file that has passed malware scanning. The image must be available through the site's Cache node. Preparation can take time for large images; the default maximum size is 20 GiB.

Mounted media is read-only and can be used by the running operating system. To boot from it, keep it mounted, select redirected media as the one-time boot target, then reset or power on the endpoint.

Set an automatic unmount time and unmount when finished. Media can remain attached after the KVM window closes; the default duration is four hours and the maximum is twelve hours. Restarting the AMT client ends the mount. Some firmware can delay a power transition while media is attached, so unmount it unless it is needed for the next boot.

If an attached image is reported as Not detected, the device has not started reading it. Check the boot target if booting from the image, or unmount and retry. Export a support bundle if the problem persists.

For automated workflows, use separate mount, wait, and unmount job tasks. A wait can use agent reconnect, power state, a duration, or manual completion. Firmware consent can still require a person at the device.

KVM and SOL ​

Open KVM or SOL from the endpoint toolbar's Intel AMT menu using desktop Chrome, Edge, or Firefox, and allow console popups. The endpoint needs a connected Relay service assignment, configured through its folder or tenant's Service routing.

KVM ​

KVM provides the firmware display, keyboard, mouse, fullscreen, and special keys. Select the keyboard layout used by the remote system; German and US layouts are supported. If the pointer cannot reach part of the remote display, try relative pointer mode. Press Escape to release a captured pointer.

Display resolution and color options depend on firmware. Clipboard transfer and console recording are unsupported.

SOL ​

Serial over LAN (SOL) provides a text console on firmware that supports it. Ordyn does not retain a terminal transcript.

When firmware requires consent, enter the code displayed on the physical endpoint. CCM requires consent for protected operations; ACM follows the configured consent policy. The Windows agent cannot retrieve the displayed code for you.

One KVM or SOL session can run on an endpoint at a time, alongside one media mount. Consoles have a four-hour maximum lifetime and end after 15 minutes without operator input. A countdown warns you five minutes before the idle timeout. Select Keep open to continue monitoring without keyboard or mouse activity. Keeping a session open does not extend its four-hour maximum lifetime.

Closing the console or losing the AMT-client connection ends the session. Start a fresh session to reconnect and obtain local consent again when required.

Roles, Audit, and Security ​

AMT Viewer provides read access. AMT Operator adds power, consoles, inspection, and media operations. AMT Administrator adds configuration, provisioning, recovery, credential rotation, and deprovisioning. Service Operator manages infrastructure separately from endpoint control. See Access Control for role assignments.

Operations are recorded in endpoint history and audit records. Normal diagnostic logs and support bundles exclude credentials and console content; the recovery bundle intentionally contains secrets.

Unsupported Capabilities ​

Ordyn does not provide AMT-client automatic failover, CIRA/MPS remote access, Kerberos or Active Directory AMT authentication, or external operational certificate authorities. It also does not configure firmware Wi-Fi, VLANs, 802.1X, or IPv6.

Use Windows Remote Access or Remote Desktop for operating-system desktop support. For service setup and troubleshooting, see Intel AMT Infrastructure.