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

Update supported client OS's - Windows Server IoT 2019 for Storage and Windows Server IoT 2022 for Storage are not supported client OSs #4657

Merged
merged 1 commit into from
Nov 12, 2024

Conversation

lamosley
Copy link
Contributor

Windows Server IoT 2019 for Storage and Windows Server IoT 2022 for Storage are vendor-specific versions of Windows IoT, and can't be tested.

I'm adding explicit entries that they are not supported, but if there is a better way to call this out in the documentation, please suggest.

Windows Server IoT 2019 for Storage and Windows Server IoT 2022 for Storage are vendor-specific versions of Windows IoT, and can't be tested. 

I'm adding explicit entries that they are not supported, but if there is a better way to call this out in the documentation, please suggest.
Copy link
Contributor

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

Copy link
Contributor

Learn Build status updates of commit fd9d079:

✅ Validation status: passed

File Status Preview URL Details
memdocs/configmgr/core/plan-design/configs/supported-operating-systems-for-clients-and-devices.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@dougeby
Copy link
Contributor

dougeby commented Nov 12, 2024

Looks ok. Approving. #sign-off

Copy link
Contributor

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @BalaDelli

@dougeby dougeby merged commit c5ccb66 into MicrosoftDocs:main Nov 12, 2024
11 checks passed
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.

3 participants