Bobcares

How to Bind SSL certificate in IIS Powershell

by | Aug 24, 2023

Learn how to bind SSL certificate in IIS Powershell. Our IIS Support team is here to help you with your questions and concerns.

How to Bind SSL certificate in IIS Powershell

Did you know that binding an SSL certificate in IIS with PowerShell involves configuring our web server to use a specific SSL certificate for secure communications with clients?

How to Bind SSL certificate in IIS Powershell

PowerShell is a scripting language that lets us automate different tasks in Windows environments.

Our experts have put together this step-by-step guide on how to bind an SSL certificate in IIS using PowerShell:

  • First, we have to make sure we have an SSL certificate ready. This certificate has to be installed on our server and available in the Windows certificate store.
  • Then, we have to open a PowerShell window with administrative privileges.
  • Next, the WebAdministration module offers cmdlets for managing IIS configurations. We can import it by running this command:

    Import-Module WebAdministration

  • Now, we can opt to list the current bindings on our IIS sites to verify the existing configuration:

    Get-WebBinding

  • At this point, we have to use the New-WebBinding cmdlet to bind the SSL certificate to a certain site. Here is the syntax:

    New-WebBinding -Name "SiteName" -Protocol "https" -IPAddress "*" -Port 443 -SslFlags 1

    Here, we have to replace “SiteName” with our IIS site name. This command creates a new binding for HTTPS on all IP addresses, using port 443. Additionally, the -SslFlags 1 parameter indicates that the certificate should be used for SSL.

  • Next, we have to find the thumbprint of the SSL certificate we want to bind. We can access it with this command:

    $certThumbprint = (Get-ChildItem -Path Cert:\LocalMachine\My | Where-Object { $_.Subject -like "*ourCertificateCommonName*" }).Thumbprint

    Here, we have to replace “ourCertificateCommonName” with the common name (CN) of our SSL certificate.

  • Now, it is time to assign the SSL certificate to the binding we created:

    $binding = Get-WebBinding -Name "SiteName" -Protocol "https"
    $binding.AddSslCertificate($certThumbprint, "My")

  • Finally, we have to apply the changes by restarting the IIS site.

By this point, we have successfully bound an SSL certificate to an IIS site using PowerShell. This enables secure communication between clients and our web server over HTTPS.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

Today, our Support Techs demonstrated how to bind SSL certificate in IIS.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF