Clients don’t connect with WSUS 3.0 on non-standard port 8530

I’ve just installed WSUS 3.0 on a new server and decommissioned WSUS 2.0 on our old server. On our 2.0 server I had both WSUS and Sharepoint installed which presented me with a few issues when I tried to upgrade it to 3.0.

For this reason I chose to install WSUS 3.0 on the alternative port of 8530, leaving port 80 for other uses:
IIS Settings with WSUS 3.0

However having set the Group Policy to simply http://mercury for both settings and waiting a day, no clients were registered. I trawled through all of the documentation and there was no reference to doing anything different if WSUS was not on port 80. You’ll notice from the IIS setup that it did indeed create virtual directories on the port 80 web implying that this should work.

Well, here’s the answer, YOU HAVE TO SET THE PORT NUMBER on the URL, this would also apply if you were directly fiddling with the settings in the registry at:


Group Policy setting for WSUS 3.0

Happy WSUS’ing.


3 responses to “Clients don’t connect with WSUS 3.0 on non-standard port 8530

  1. Oh gosh! After troubleshooting a client connectivity issue to my WSUS server for the last 5 hours, it appears that your solution of adding the port number to the url has resolved my issue.

    Thank you, thank you, thank you!

  2. Nice… thank you for the post.

  3. Keep in mind that the port itself must already be opened in order for this all to work. Turns out that this was my issue with regards to WSUS ‘downstream’ servers not speaking to their ‘upstream’ counterpart.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s