Closed ChristophHannappel closed 2 years ago
I know the SecureSocketsLayer parameter also existed pre-Subscription Edition, but then didn't configure IIS like Subscription Edition is now able to. But it did configure the HTTPS host header names, etc.
Just checked the v4.x code and saw that there the update part didn't exist yet. That was added with the update for SPSE. So I think you are 100% right and this was a copy/paste issue. The New-SPWebApplication did have a SecureSocketLayer parameter, but the Set-SPWebApplication cmdlet didn't 😄. Will review the PR!
Problem description
The Set Function for SPWebApplication adds the
SecureSocketsLayer
Parameter to theSet-SPWebApplication
function, if the WebApplication URL has an https scheme.In SharePoint Server 2019 the Set-SPWebApplication Function does not have a parameter SecureSocketsLayer
Verbose logs
DSC configuration
Suggested solution
Put the Code Block into the SharePoint Server Subscription Edition IF block https://github.com/dsccommunity/SharePointDsc/blob/fe2111d3c911e2b5ddd7f14855f1a17c32ff0047/SharePointDsc/DSCResources/MSFT_SPWebApplication/MSFT_SPWebApplication.psm1#L627
SharePoint version and build
Operating system the target node is running
PowerShell version and build the target node is running
SharePointDsc version