Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security, Veeam & DevOps

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form

Configure SSL connection for WSUS Upstream and Downstream Servers

Posted on 10/03/201817/08/2026 Christian By Christian No Comments on Configure SSL connection for WSUS Upstream and Downstream Servers
  1. Home
  2. Windows Server
  3. Configure SSL connection for WSUS Upstream and Downstream Servers
Secure communication

In this article, we will learn how to Configure SSL connection for WSUS Upstream and Downstream Servers. SSL stands for Secure Sockets Layer, a vital security technology. See the following guides for some related articles I have written. Configuring WSUS Email Notification to Work With Office365, How to setup and configure Windows server update services (WSUS), important Areas to Master on WSUS (Installed and not applicable, Install 1/4, and Installed / Not applicable 100).

SSL and its successor, Transport Layer Security (TLS) are protocols that establish authenticated and encrypted links between networked computers.

Before we proceed with these steps, please take a look at the articles below. – Targeting WSUS Client with the Registry keys: How to configure WSUS Clients to get Updates from the WSUS server using Registry settings and how to apply Windows Updates from WSUS to the server using AWS RunCommand and some very handy WSUS Commands “Windows Server Update Services Commands, WAUACLT, PowerShell and USOClient “.

Configure Server Certificate

From the Server Manager, click Tools and open IIS. Click on the IIS Server Node, and double click on the Server Certificate

SSL setup

Click on Import (and import the SSL certificate in .pfx format and enter the password)

WSUS servers

Note: Nonetheless, to ensure secure communication, it’s crucial to learn how to configure SSL. Import the CA certificate into the Trusted Root CA store on downstream WSUS servers or the local computer.

If the certificate is only imported to the Local User Trusted Root CA store, the downstream WSUS server will not be authenticated on the upstream server.

Note: Moreover, You must import the certificate to all computers that will communicate with the WSUS server. Therefore, this includes all client computers, downstream servers, and computers that run the WSUS Administration Console.

The certificate should be imported into the local computer Trusted Root CA store or into the Windows Server Update Service Trusted Root CA store. See how to configure WSUS.

Bind the SSL certificate

We have to bind the SSL certificate. Expand your server, expand Sites, and select WSUS Administration

Under Actions, click on Bindings

The binding windows opens, click on Edit and enter the host names (Select the cert for HTTPS)

SSL configuration

Enforce SSL Encryption

Now enforce the SSL encryption on the following virtual roots listed below. Ensure to repeat all steps for each directory listed below

  • ApiRemoting30
  • ClientWebService
  • DSSAuthWebService
  • ServerSyncWebService
  • SimpleAuthWebService
Secure communication

Select the directory (virtual root) e.g  ClientWebService and double click on SSL Settings

Screenshot of the IIS (Internet Information Services) Manager home interface, showing various management features including authentication options, output caching, and settings options.

Check the require SSL  and under Actions click on Apply

Screenshot of Internet Information Services (IIS) Manager displaying SSL settings, including an option to request status for other virtual trunks or directories.

Let’s instruct WSUS to make use of SSL, and this can be done via the command line.

Navigate to the WSUS installation path C:Program FilesUpdate ServicesTools as shown below on your Server

Run the WsusUtil.exe as shown above followed by configuressl and the FQDN as shown below

Command Prompt window displaying a command related to Microsoft Update services.

The result would be this

Command Prompt window displaying configuration commands related to Windows Update services.

Finally, restart the WSUS server to make sure all changes take effect.  This should enable access to the  WSUS management console if everything is okay.

See the following guide for some related WSUS contents “how to Start, Stop and Restart Windows Server Update Services (WSUS) via PowerShell and CMD, Windows Server Update Services: Windows 2016 Servers does not show up on the WSUS console, and WSUS clients appear and disappear from the WSUS Update Services console“.

Note: However, You can witness some weird issues after configuring SSL, simply use these link

  • wsusutil usecustomwebsite false
  • wsusutil usecustomwebsite true
C:Program FilesUpdate ServicesToolsWSUSutil usecustomwebsite false

And rerun

C:Program FilesUpdate ServicesToolsWSUSutil usecustomwebsite True

To establish secure communication for downstream servers connecting to the upstream server via port 8531. Ensure proper rules are in place for this setup. And you can additionally reconfigure using the configure SSL from this path.

C:Program FilesUpdate ServicesToolsWSUSutil

Note: However, You can set up your own CA: (Enterprise root CA). I hope you found this article useful on how to Configure SSL connection for WSUS Upstream and Downstream Servers. Please feel free to leave a comment below.

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
Windows Server Tags:Certificates, HTTPS, SSL

Post navigation

Previous Post: How to target WSUS clients with the registry keys
Next Post: Configure WSUS Email Notification for Office365

Related Posts

  • WinRM set up for specific IP
    Configure WinRM to accept connection from a specific IP Address Windows
  • Task Scheduler Error 0x2 1
    How to fix Windows Task Scheduler 0x2 Error Windows
  • ycx
    How to use SysInternals Live Tools Windows Server
  • wds and dns l
    What happens when WDS and DNS are installed on the same Windows Server? DNS issues with WDS Windows Server
  • ycx
    Detect registry keys using Process Monitor using Sysinternals Tools Windows Server
  • Perform Site Maintenance or reset this site greyed out
    Fix “Perform Site Maintenance or reset this site” greyed out Windows Server

More Related Articles

Lockout7 Change Account Lockout Threshold for Local Accounts in Windows: The reference account is locked Windows
Missing Windows defender Missing Windows Defender? Install and manage Microsoft Defender via Windows Security on Windows Server Windows Server
erroradkupdate An error has occurred in the script on this page: HTA applications report a Script error after upgrading to ADK for Windows 11, version 22H2 Windows Server
yxxycx yx How to change the Default First-Site-Name in Active Directory Windows Server
upgrade 2 How to upgrade Windows Server Evaluation to Full Version Windows Server
Permit a Blocked File or App in Windows Security How to Permit a Blocked File or App in Windows Security Manually Windows

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

vexpert-badge-stars-5

Virtual Background

VEEAMLEGEND

Categories

Top 30 Sysadmin blog

veeaam100

Veeam Vanguard

  • nonRDP admin
    Allow RDP access for non administrators: Add User to Remote Desktop Users Group in Active Directory Windows Server
  • Fix invalid backup repostory and delete not needed repo via Veeam Backup Repository
    Fix missing path and delete a Veeam Backup Repository Backup
  • encryption 04.05.32
    How to Enable BitLocker without Compatible TPM Security | Vulnerability Scans and Assessment
  • Norton RDP
    Can’t connect via RDP upon installing Norton 360 Anti-Virus Solution
  • FailedRegistration
    DNS Bad key 9017: The Cluster Name registration failed of one or more associated DNS names Virtualization
  • proxmox
    Clone a Proxmox Container: CT Restoration Guide Virtualization
  • images 2
    AnyConnect SSL VPN Client Configuration Guide Network | Monitoring
  • windows 10 creators update wallpaper
    Run or Edit and Delete Tasks via Windows Task Scheduler Windows

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,747 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Contact
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon
  • Bsky

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2026 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.