Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Stack HCI Upgrade - OEM support warning #3372

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

YannickDeKoeijer
Copy link

@YannickDeKoeijer YannickDeKoeijer commented Oct 22, 2024

Before you upgrade from 22h2 to 23H2 you should always consult your OEM first.

I am a Microsoft employee working on HCI with customers and Hardware OEMS.

Customers have done this upgrade as described, an now have an unsupported environment because the OEM doesn't support the upgrade, or the new OS version (In combination with their own tools, or simply not validated the HCI version yet for that specific hardware)

please refer to Dell documentation as an example.
https://dell.github.io/azurestack-docs/docs/hci/supportmatrix/2406/14g-15g_hci/

I also see we put a notice for EOL on 22h2 on may 2025. how can we stop support on an OS there is no upgrade path for that's supported by the OEMS? Especially for customers with strech that CANT even upgrade.

Before you upgrade from 22h2 to 23H2 you should always consult your OEM first.

I am a Microsoft eomployee working on HCI with customers and OEMS, where customers have done this upgrade as described an now have an unsupported environment because the OEM didn't suport it
Copy link
Contributor

@YannickDeKoeijer : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 3465f7a:

✅ Validation status: passed

File Status Preview URL Details
azure-stack/hci/upgrade/about-upgrades-23h2.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@ShannonLeavitt
Copy link
Contributor

@alkohli

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged Tracking label for the PR review team label Oct 22, 2024
@YannickDeKoeijer
Copy link
Author

YannickDeKoeijer commented Oct 22, 2024

I'd love to give more feedback if needed. You can reach out through internal teams on the name you see here as my user name.

I've added some more comments to the main message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants