You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You may want to consider having AutoSPInstaller integrate with the new SSL certificate management functionality in SharePoint Server Subscription Edition. (The AssignCert function in AutoSPInstaller and related code.) There's a risk that SharePoint Server Subscription Edition might stomp on the SSL certificate binding configured by the existing AutoSPInstaller code now that SharePoint thinks it has control over the SSL certificate used by the SSL binding.
Take a look at the following new SharePoint PowerShell cmdlets to see what functionality is available:
Move-SPCertificate: Moves the specified certificate to a different certificate store.
New-SPCertificate: Creates a new certificate signing request. (Also creates a self-signed certificate that's placed in SharePoint's Pending certificate store.)
Add-SPCertificateNotificationContact: Adds an email address to the list of contacts to be notified when certificates are about to expire or have already expired.
Clear-SPCertificateNotificationContact: Deletes all email addresses from the list of contacts to be notified when certificates are about to expire or have already expired.
Remove-SPCertificateNotificationContact: Deletes an email address from the list of contacts to be notified when certificates are about to expire or have already expired.
... and the various PowerShell cmdlets that have been updated to add a -Certificate <SPServerCertificatePipeBind> parameter to specify which SSL certificate managed by the SharePoint SSL certificate management feature should be used. That includes New-SPCentralAdministration, Set-SPCentralAdministration, New-SPWebApplication, Set-SPWebApplication, and New-SPWebApplicationExtension.
The text was updated successfully, but these errors were encountered:
You may want to consider having AutoSPInstaller integrate with the new SSL certificate management functionality in SharePoint Server Subscription Edition. (The
AssignCert
function in AutoSPInstaller and related code.) There's a risk that SharePoint Server Subscription Edition might stomp on the SSL certificate binding configured by the existing AutoSPInstaller code now that SharePoint thinks it has control over the SSL certificate used by the SSL binding.Take a look at the following new SharePoint PowerShell cmdlets to see what functionality is available:
... and the various PowerShell cmdlets that have been updated to add a
-Certificate <SPServerCertificatePipeBind>
parameter to specify which SSL certificate managed by the SharePoint SSL certificate management feature should be used. That includes New-SPCentralAdministration, Set-SPCentralAdministration, New-SPWebApplication, Set-SPWebApplication, and New-SPWebApplicationExtension.The text was updated successfully, but these errors were encountered: