Skip to content

Release Notes

Release Highlights


Note From the Team

After dusting off some old shelves and checking every nook and cranny for Spring, we found a bunch of new features for RPC-Go for the April 2024 Release. The team is getting closer and closer now to being able to offer full activation and configuration entirely locally with RPC-Go. As of this release, we can now offer activation, wired/wireless configuration, TLS, configuration of redirection features, and a number of maintenance-type commands available now 100% locally utilizing only RPC-Go.

Next stop, RPC-Go wired and wireless 802.1x configuration using Enterprise Assistant! We aren't far away now!

Best Wishes,

The Open AMT Cloud Toolkit Team

What's New?

Feature: RPC-Go Local Wired Configuration

Wired settings can now be configured locally using just RPC-Go. For wired connections, AMT supports both DHCP and Static IP environments. Configuration info can be passed two different ways, either directly via the command line or read from a config file.

rpc configure wired -dhcp -ipsync
rpc configure wired -config config.yaml

See the RPC documentation for flag details and config file examples.


Feature: RPC-Go Change AMT Password

The AMT password can now be reconfigured by RPC-Go using the following new configure amtpassword subcommand. This will give a quick and easy way to update AMT passwords across a large number of devices.

However, because this is a local command, there is no centralized database storing the new AMT passwords so make sure to take note of any changes made! For deployments utilizing RPS and MPS, see the rpc maintenance changepassword command.

rpc configure amtpassword -newamtpassword newAMTPassword -password oldAMTPassword

See the documentation for additional details.


Feature: RPC-Go Configure AMT Features

AMT Features can be configured locally now too. For those familiar with the AMT Features MPS API call, the functionality is the same. With this command, redirection features like KVM, SOL, and IDER, can be enabled or disabled.

For Admin Control Mode devices, the user consent settings can also be configured. User consent cannot be modified for CCM devices.

rpc configure amtfeatures -kvm -sol -ider -userConsent none

See the documentation for additional details.

Get the Details

Additions, Modifications, and Removals

RPC-Go

v2.32.1

  • fix: changed optin all type (47ba85f)

v2.31.2

  • feat: adds configure amtpassword local command (#442)
  • feat: adds amt features configuration (#407)
  • fix: removes duplicate printing for -h and -help flags on maintenance commands
  • fix: use tm2 for SetHighAccuracyTimeSynch (#460)
  • fix: configure error code
  • fix: variable names for configJson input (#441)
  • refactor: adds wireless and wired subcommands deprecating addwifisettings and wiredsettings (#461)
  • ci: address permissions for trivy-scan to upload (#447)
  • docs: update badge links
  • docs: update badge styles

v2.29.1

  • fix: local acm activate does not prompt for password when it is in the config (#436) (9a6e048)

v2.29.0

  • feat: adds addwiredsettings local configure command (#422) (ba58bb5)

v2.28.3

  • fix: XML messages are no longer escaped when using -json flag (#429) (01c646c)

v2.28.2

  • fix: changes amtinfo output to use stdout instead of stderr (7caa756)

v2.28.1

  • fix: generated binaries should not use CGO (#426) (2138cfe)

Enterprise Assistant (EA)

  • fix: logs are made generic and profile request updated #18
  • fix: security key and port #16

go-wsman-messages

v2.2.2

v2.2.1

  • fix: changes SetAdminACLEntryEx_INPUT to SetAdminAclEntryEx_INPUT for AMT_AuthorizationService (#269) (35139e2)

v2.2.0

v2.1.11

  • fix: wsman calls to set amt features (#262) (de460c5)

v2.1.10

  • fix: removes typo in GeneralSettingsRequest struct (#260) (c33b573)

v2.1.9

  • fix: updates pull call to take instanceid as a string (#256) (0f2430b)

  • fix: set OptInRequired to uint32 (#221) (865e6d8)

Project Boards

Check out our new Sprint Planning project board to see what stories the dev team is actively working on, what is in our backlog, and what is planned for the next sprint.