Release 6.1 adds several modifications to the Intel AMT architecture:
• All realms are now available from the local interface. See Functionality to Realm Mapping Local applications with sufficient privileges can configure Intel AMT parameters. This change applies to the WS-Management interface and to the deprecated SOAP interface. It is also possible to run the WebUI locally.
• A new predefined user, $$OsAdmin, allows a local application with OS Admin privileges on the Host platform to access many Intel AMT parameters with no additional Intel AMT credentials even before Intel AMT is setup and configured. This enables “out-of-the-box” operations. See Predefined Local System Users for a description of this feature.
• Intel AMT will respond to an RMCP ping before setup and configuration is performed. This provides a tool for detecting whether an unconfigured platform has Intel AMT capability and whether setup has completed. A remote application can do this without Intel AMT user credentials. See Use RMCP Ping to Determine the Platform State.
• The provisioning audit record is now a CIM object, with the instance indicating the type of setup performed.
• TLS-PSK and Remote Configuration are performed using mutual authentication TLS. Starting with Release 6.1, Intel AMT no longer validates the HTTP header for digest authentication during setup and configuration.
• The redirection library supports selecting link preference so that redirection sessions do not automatically eliminate host processor WLAN connectivity.
Copyright © 2006-2022, Intel Corporation. All rights reserved.