Skip to content

Intel AMT Infrastructure ​

Intel Active Management Technology (AMT) lets you manage supported Intel business devices even when their operating system is offline. Ordyn uses an AMT service client with network access to the devices. Browser KVM and SOL consoles also require a Relay service.

AMT management is available for devices already enrolled as Ordyn endpoints. For endpoint setup and daily use, see Intel AMT Endpoint Management.

Firmware Compatibility ​

Intel AMT 11.x, 12.x, 14.x, 16.x, and 19.x have been verified for use with Ordyn.

Support is best effort. Available features depend on the device and its firmware. Other firmware versions have not been verified with Ordyn; check the workflows you need on representative devices before deployment.

Components ​

Prepare the following before provisioning endpoints:

A tenant can have several AMT clients, for example one per site. Choose which client each endpoint uses through Service routing.

Network Requirements ​

The AMT client connects to the IPv4 address on the endpoint's Intel AMT network interface. The configured AMT name identifies its TLS certificate. Use an address reachable from the AMT client, including when Windows is offline.

SourceDestinationPort and protocolPurpose
Windows agentAssigned EdgeWSS TCP 443Provisioning and recovery
Windows agentLocal Intel LMSTCP 16992 or 16993Local firmware setup, depending on AMT version
AMT clientAssigned EdgeWSS TCP 443Service connection
AMT clientAMT deviceTLS TCP 16993Firmware management
AMT clientAMT deviceTLS TCP 16995KVM, SOL, and redirected media
AMT clientCache nodeHTTPS TCP 443Media download
AMT client and browserRelay serviceWSS TCP 443KVM and SOL
Relay serviceAssigned EdgeWSS TCP 443Service connection
Runner, for optional Intel trust refreshtsci.intel.comHTTPS TCP 443Intel ODCA bundle download
Net node, for enabled IPAM scansDevice networkTCP 16992 and 16993AMT address discovery

The AMT client and endpoints need no public inbound access. Provisioning does not require a direct connection between the Windows agent and AMT client. Make the Relay service reachable by both the browser and AMT client.

Managed firmware connections use TLS. AMT 11–13 setup can use local HTTP through LMS on the Windows endpoint; remote plaintext management is unsupported.

To discover changed AMT addresses while Windows is offline, configure automatic IPAM scans with common protocol probes and a Net node on the device's local network. Ordyn verifies the device before updating its management address.

Installation ​

Prerequisites:

Open Services > Intel AMT, select Add AMT client, and choose its name, tenant, and assigned Edge service. Copy the created service client ID.

Check out the AMT deployment folder:

bash
if [ ! -d /opt/ordyn-compose/.git ]; then
  git clone --filter=blob:none --sparse https://github.com/ordyn-project/compose.git /opt/ordyn-compose
fi
cd /opt/ordyn-compose
git sparse-checkout add amt

Create the environment file:

bash
cd /opt/ordyn-compose/amt
cp .env.example .env

Set these values in .env:

dotenv
ORDYN_AMT_EDGE_HOST=ordyn-edge.example.com
ORDYN_AMT_SERVICE_CLIENT_ID=<service-client-id>

Pull and verify the service image:

bash
docker compose pull
python3 /opt/cosign-docker-verify/verify.py

Continue after image verification succeeds. Under Administration > Enrollment Tokens, create a Service client token for Intel AMT using the same tenant, Edge service, and AMT client. Enroll with the container stopped:

bash
docker compose stop amt
printf '%s' '<enrollment-token>' | docker compose run --rm -T --no-deps amt npm run enroll -- --token-stdin

After enrollment succeeds, start the service and confirm that the AMT client is connected in Ordyn:

bash
docker compose up -d amt

To renew or replace its service enrollment certificate, issue a fresh enrollment token and run:

bash
docker compose stop amt
printf '%s' '<enrollment-token>' | docker compose run --rm -T --no-deps amt npm run enroll -- --token-stdin --force

After forced enrollment succeeds, start it with docker compose up -d amt.

AMT Service Clients ​

Open a tenant, endpoint folder, or agent endpoint and select Service routing > Intel AMT. Select a client from that tenant and save. Set a tenant route as the default, then override it for folders or individual endpoints where needed. Leave a folder or endpoint selection empty to inherit its route.

An endpoint uses its own route first, then the nearest folder route, then the tenant route. The panel shows the effective selection. An unavailable client does not cause automatic fallback to another client.

Finish active operations, close console and media sessions, and complete recovery before changing the client used by a device. Changing routing does not deprovision the device. Disabling an AMT profile keeps its routing selection, ready for management to resume.

Connected clients check managed device availability about every five minutes, including while Windows is offline.

Keep the AMT client's persistent data when updating or restarting it. Restarting the client ends its active KVM, SOL, and redirected-media sessions.

Activation Credentials ​

An activation credential authorizes a device to enter ACM. Create one under Services > Intel AMT > Activation Credentials, choosing the tenant, DNS suffix, and certificate profile:

  • ECC P-384 / SHA-384 for compatible firmware
  • RSA-2048 / SHA-256 compatibility for firmware requiring RSA, including Ordyn's AMT 11–13 provisioning workflow

Activation credentials belong to a tenant and can be used through any of its routed AMT clients. Changing the service route does not require a new setup file when the existing activation trust is still valid. The DNS suffix must match the planned AMT configuration; create another credential for a different suffix.

Generate and apply a per-device setup.bin to install the credential's activation trust in firmware. Creating a credential in Ordyn alone does not prepare the device. Select Provision after applying the file. Ordyn checks readiness automatically when needed; resolve any reported trust or DNS-suffix requirements before retrying.

CCM provisioning does not need an activation credential. Adopting a device already in the selected control mode uses its current AMT administrator password and does not require another setup file.

Ordyn generates activation credentials. Importing externally issued provisioning certificates or activating through an existing Trusted Endpoint Provisioning (TEP) owner identity is unsupported. See Intel AMT Certificates and Renewal for renewal and activation-root rotation.

Intel ODCA Trust ​

Keep endpoint agents and firmware trusted and up to date before provisioning Intel AMT. Ordyn does not check Intel ODCA certificate revocation during provisioning; importing an ODCA bundle does not enable that check.

Administrators can review optional Intel trust and revocation bundles under Services > Intel AMT > Intel ODCA. Imported bundles are not required for provisioning.

To refresh a bundle, run an infrastructure job with a Refresh Intel ODCA trust step on a Windows or Linux Runner that can reach tsci.intel.com over HTTPS. Schedule the job if regular updates are needed. Without a Runner, obtain a bundle through your organization's approved process and import it on the Intel ODCA page.

Intel AMT Operational Certificate Authority ​

Create an authority under Administration > Certificate Authorities, selecting the Intel AMT operational purpose and the tenant. Ordyn uses it to issue the device certificates needed for managed TLS connections.

Ordyn selects a compatible device certificate profile and maintains certificates automatically while management is enabled. View installed device certificates under Hardware > Intel AMT > Certificates on the endpoint. For renewal, rotation, and expiry recovery, see Intel AMT Certificates and Renewal.

Logging, Diagnostics, and Alerts ​

For a failed operation, review the endpoint's History and Intel AMT guidance first. Confirm that the assigned AMT client is connected and, for provisioning or recovery, that the Windows agent is online.

Export an endpoint support bundle when more detail is needed. It collects related AMT-client and agent diagnostics. AMT clients retain local logs for 14 days within their disk allowance.

Administrators can enable temporary WS-Man debugging on the AMT client for up to 15 minutes when investigating a communication problem. Diagnostic logs exclude passwords, private keys, and console content.

Review alerts for provisioning failures, authentication problems, device or client outages, and certificate maintenance. Follow the recovery workflow if the endpoint requires recovery.

Service Retirement ​

Remove or replace service routes and resolve dependent device assignments before deleting an AMT client. Resolve dependent devices and setup files before deleting an activation credential. Ordyn blocks deletion while it is still in use. Deprovision devices first if their firmware configuration must also be removed.