Skip to content

Conversation

@1000986-PHS
Copy link

@1000986-PHS 1000986-PHS commented Jun 18, 2025

…022+ compatibility

Description: The prior version used indexes when parsing netsh output and would fail with Windows Server 2022. The new version uses field-name-based parsing for netsh output in Add-SslCert to ensure compatibility with Windows Server 2022 and future versions.

The one thing I didn't see was if there was a version number somewhere that needed bumped.

Documentation changes required: (N)

Added unit tests: (N)

Attached related issue: (Y) #1039 #1008 #919 #1058 #862

Checklist:

  • Version was bumped - please check that version of the extension, task or library has been bumped.
  • Checked that applied changes work as expected.

…022+ compatibility

Use field-name-based parsing for netsh output in Add-SslCert, ensuring compatibility with Windows Server 2022 and future versions. The prior version used indexes and would fail with Windows Server 2022.
@1000986-PHS
Copy link
Author

@microsoft-github-policy-service agree company="ProMedica"

@1000986-PHS
Copy link
Author

@LeftTwixWand and @ivanduplenskikh You two seem to successfully complete PRs here. What do I need to do to move this along?

This bug has prevented my organization from being able to deploy to Windows Server 2022 for many years now. As a workaround I've had to manually fix the bug with every agent myself but that's tedious as every update to the agents could push the broken version again.

@ISAF87
Copy link

ISAF87 commented Jul 29, 2025

Any updates regarding this?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants