fix: update 202 and 203 to supported power states

[shaoboon]

PR Checklist

• Leverages formatting as provided by https://squidfunk.github.io/mkdocs-material/reference/abbreviations/
• Have viewed and verified edits in rendered form ensuring proper formatting

What are you changing?

• Created supported and unsupported sections for Alternative Boot Options section
• Added 202 and 203 boot options into supported alternative boot options
• Added 104, 200 and 201 boot options into unsupported alternative boot options

Anything the reviewer should know when reviewing this PR?

For issue #626

Preview:

[Copilot]

Pull request overview

Updates the power state reference to clarify which alternative boot options are supported by the Toolkit, specifically moving 202/203 into a supported section and explicitly listing unsupported options.

Changes:

• Replaces the prior “not natively support…” note with a supported alternative boot options section focused on IDE-R CD-ROM (202/203).
• Adds an “Unsupported Alternative Boot Options” subsection containing 104, 200, and 201.
• Reorganizes the table content to separate supported vs. unsupported boot options.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[graikhel-intel]

Thanks for doing this @shaoboon! A few suggestions to improve clarity and accuracy in the docs:

1. Avoid calling this “In-band”

This section could be clearer if we avoid the term in-band altogether and directly state that Intel LMS is required.

Current text:

In-band Required
The power actions below require an in-band agent, Local Management Service (LMS), or Intel® Integrated Management and Security Status (Intel® IMSS).

Suggested improvement (of course this could further be improved):

Intel LMS Required
The power actions below require the Intel Local Manageability Service (LMS) to be installed and running on the system.

This keeps things simple and avoids introducing terminology that may confuse users.

2. Clarify LMS installation guidance (especially for non-Windows)

The following section is accurate for Windows systems, but it may help to add guidance for other platforms and point users to the official Intel LMS repository.

Current text:

The service installer is packaged with the Intel MEI drivers on the OEM websites. If Windows OS is reimaged or reinstalled, only the Intel MEI Driver is reinstalled, not LMS or IMSS.

If the LMS is not installed, visit the OEM website and look for download packages for Intel® IMSS or the Intel CSME driver.

Suggested improvement (of course this could further be improved):

On Windows systems, LMS is typically installed as part of the OEM Intel CSME driver package. If the OS is reimaged or reinstalled, LMS may not be reinstalled automatically. Make sure to install the latest Intel CSME driver package, which should include LMS.

For Linux platforms (or if LMS is missing), users can build LMS from source using the official Intel LMS GitHub repository https://github.com/intel/lms. Prebuilt packages (such as snap) are not actively maintained, so building from source may be required.

3. It may be worth double-checking whether Power actions 400 (Reset to PXE) and 401 (Power on to PXE) are still working. I don’t think we’ve tested these in quite a while. Can you confirm whether these actions are still supported and functional? If this needs more investigation, we can create a follow-up backlog item to track it.

4. These links don't seem to work for me, can you check if there's something I'm missing or the links need to be updated?

[shaoboon]

4. These links don't seem to work for me, can you check if there's something I'm missing or the links need to be updated?

These links are pointing to MPS API v2.22.5, but it is not available, I was only able to find v2.22.3 that is available to the public, I am not sure if the link should be pointing to v2.22.3 or we should update the MPS API in the swagger hub, please advise.

[shaoboon]

3. It may be worth double-checking whether Power actions 400 (Reset to PXE) and 401 (Power on to PXE) are still working. I don’t think we’ve tested these in quite a while. Can you confirm whether these actions are still supported and functional? If this needs more investigation, we can create a follow-up backlog item to track it.

I tried testing it on an AMT device, but unfortunately the device doesn't support PXE boot, so when the power command is sent, the device simply reboot back to OS, may need a follow-up backlog to test it.

[shaoboon]

1. Avoid calling this “In-band”

This section could be clearer if we avoid the term in-band altogether and directly state that Intel LMS is required.

Current text:

In-band Required
The power actions below require an in-band agent, Local Management Service (LMS), or Intel® Integrated Management and Security Status (Intel® IMSS).

Suggested improvement (of course this could further be improved):

Intel LMS Required
The power actions below require the Intel Local Manageability Service (LMS) to be installed and running on the system.

This keeps things simple and avoids introducing terminology that may confuse users.

Resolved by using Remote Power Actions and Local Power Actions to replace out-of-band and in-band

2. Clarify LMS installation guidance (especially for non-Windows)

The following section is accurate for Windows systems, but it may help to add guidance for other platforms and point users to the official Intel LMS repository.

Current text:

The service installer is packaged with the Intel MEI drivers on the OEM websites. If Windows OS is reimaged or reinstalled, only the Intel MEI Driver is reinstalled, not LMS or IMSS.
If the LMS is not installed, visit the OEM website and look for download packages for Intel® IMSS or the Intel CSME driver.

Suggested improvement (of course this could further be improved):

On Windows systems, LMS is typically installed as part of the OEM Intel CSME driver package. If the OS is reimaged or reinstalled, LMS may not be reinstalled automatically. Make sure to install the latest Intel CSME driver package, which should include LMS.
For Linux platforms (or if LMS is missing), users can build LMS from source using the official Intel LMS GitHub repository https://github.com/intel/lms. Prebuilt packages (such as snap) are not actively maintained, so building from source may be required.

Mentioned Windows and Linux LMS installation instruction separately