Revise driver and firmware installation instructions#4160
Revise driver and firmware installation instructions#4160Karl-WE wants to merge 12 commits intoMicrosoftDocs:mainfrom
Conversation
Updated guidance regarding driver and firmware installation for Azure Local 23H2 or later, specifying changes in the use of Windows Admin Center plugins and introducing OEM SBE packages for solutions.
|
@Karl-WE : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 9e4a368: ✅ Validation status: passed
For more details, please refer to the build report. |
Updated the document to reflect changes from version 23H2 to 24H2, including system requirements and additional notes on hardware and deployment. Major changes Headlines and structure replaced dotted information about drives into readable table thanks copilot placed OEM information at the bottom removed duplicate links for OEM. added clarity about drive configuration and external SAN support plus links. revised the information about Windows Admin Center extension for firmware (wrong) added information about driver and firmware management in common cases and the specialty of each solution category
|
Learn Build status updates of commit 232949d:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| azure-local/concepts/system-requirements-23h2.md | Details |
azure-local/concepts/system-requirements-23h2.md
- Line 114, Column 117: [Warning: file-not-found - See documentation]
Invalid file link: './windows-server/storage/storage-spaces/performance-history.md'. - Line 292, Column 1: [Warning: multiple-h1s - See documentation]
Multiple H1s(H1 'OEM information') are not allowed. You can only have one top-level heading.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
Updated drive requirements section and clarified OEM installation steps. Added note about Azure Local support for additional SAN via Fibre Channel. Sorry for the massive change. Reworked the document structure while reading it. OEM is now placed on the bottom as the former structure caused duplicate of backlinks added clarification on - SAN Support for Azure Local - converted bullet points on drive characteristics into a readable table - added notes and warnings where due - I mean it many still do not understand these critical things I've highlighted - added information about BIOS reset - reworked the former Driver and Firmware with WAC section as it it has dramatically changed. Included the most common scenarios since this concept page described it a bit but did not keep up with the changes and HW solution differences. Hope you appreciate this work. It took a whole while.
|
Learn Build status updates of commit 5c148d9:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| azure-local/concepts/system-requirements-23h2.md | Details |
azure-local/concepts/system-requirements-23h2.md
- Line 285, Column 1: [Warning: multiple-h1s - See documentation]
Multiple H1s(H1 'OEM information') are not allowed. You can only have one top-level heading.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
- fixed headers - reworked section about drivers and firmware, added common use cases and added solution specific guidance - resorted some sections, put OEM at the bottom and removed duplicate references - transferred bullet points for drive characteristics into a readable table (thanks Copilot) - added warnings and informational where due, because customers / deployments fail because of missing these crucial bits.
|
Learn Build status updates of commit 5da691c:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| azure-local/concepts/system-requirements-23h2.md | Details |
azure-local/concepts/system-requirements-23h2.md
- Line 285, Column 1: [Warning: multiple-h1s - See documentation]
Multiple H1s(H1 'OEM information') are not allowed. You can only have one top-level heading.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
fixed links
|
Learn Build status updates of commit 80ae085: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
Learn Build status updates of commit 41fca9d: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
There was a problem hiding this comment.
Pull request overview
This PR revises driver and firmware installation instructions for Azure Local, updating guidance for version 23H2 or later. The changes clarify that Windows Admin Center plugins should no longer be used for driver/firmware installation on Azure Local 23H2+, and introduce OEM Solution Builder Extension (SBE) packages as the recommended approach for different solution types.
Changes:
- Updated document title and description from version 23H2 to 24H2
- Restructured data drive requirements into a more organized table format
- Added new sections for BIOS settings, driver/firmware management guidance, and deployment workflows
- Clarified that Windows Admin Center extensions should not be used for Azure Local 23H2+ driver/firmware installation
- Added guidance for Premier Solutions, Integrated Systems, and Validated Nodes deployment and update processes
- Reorganized OEM information section and updated external SAN storage documentation
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ## Driver | ||
| ### Instance or node redeployment | ||
| Premier Solutions and Integrated Systems: Some OEM provide ready to use ISO Images that matches the preinstalled and preconfigured version. | ||
| Validated Nodes: These may come preinstalled. The forementioned check or further sideloading update packages is required as per OEM recommendation |
There was a problem hiding this comment.
Grammar issues: Same as line 170 - "The forementioned check or further sideloading update packages is required as per OEM recommendation" needs correction. "forementioned" should be "aforementioned" and subject-verb agreement should be fixed.
| title: System requirements for Azure Local, version 24H2 | ||
| description: How to choose machines, storage, and networking components for Azure Local, version 24H2. |
There was a problem hiding this comment.
The title and description reference version "24H2" but the filename remains "system-requirements-23h2.md". This creates a discrepancy between the file name and its content, which could confuse users and make the documentation harder to maintain. Consider either keeping the content aligned with 23H2 or renaming the file to match 24H2.
| ## Machine and storage requirements | ||
|
|
||
| Microsoft Support may only be provided for Azure Local running on hardware listed in the [Azure Local catalog, or successor](https://aka.ms/azurelocalcatalog). | ||
| Microsoft Support may only be provided for Azure Local running on hardware listed in the [Azure Local catalog](https://aka.ms/azurelocalcatalog). |
There was a problem hiding this comment.
The section heading structure is inconsistent. Line 60 removed ", or successor" from the text but left the heading level unchanged. However, the change from "# [Azure public]" to "### [Azure public]" (lines 34, 48) suggests this was intentional. Please verify that the removal of ", or successor" text doesn't break any important references or historical context that users might need.
|
|
||
| ### Initial Deployment | ||
| Premier Solutions and Integrated Systems: These are delivered preinstalled and preconfigured will update their firmware and driver automatically. | ||
| Validated Nodes: These may come preinstalled. The forementioned check or further sideloading update packages is required as per OEM recommendation |
There was a problem hiding this comment.
Grammar and clarity issues: The sentence "The forementioned check or further sideloading update packages is required as per OEM recommendation" has several problems:
- "forementioned" should be "aforementioned"
- The subject-verb agreement is incorrect ("check or...packages is" should be "check or...packages are")
- The sentence is unclear - consider rephrasing for better clarity
|
Can you review the proposed changes? This content requires automated and human checks available only in the private repository. Please close this PR ( #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
Learn Build status updates of commit 7d9f8c5: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
Learn Build status updates of commit 7c7becc: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
Updated guidance regarding driver and firmware installation for Azure Local 23H2 or later, specifying changes in the use of Windows Admin Center plugins and introducing OEM SBE packages for solutions.