MSU Listserv


MSUNAG Archives

MSUNAG Archives


MSUNAG@LIST.MSU.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV at MSU

LISTSERV at MSU

MSUNAG Home

MSUNAG Home

MSUNAG  July 2016

MSUNAG July 2016

Subject:

Re: WSUS, Win2012 R2, SSL configuration

From:

Stefan Ozminski <[log in to unmask]>

Reply-To:

Stefan Ozminski <[log in to unmask]>

Date:

Tue, 26 Jul 2016 15:49:14 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (158 lines)

After multiple tries with multiple variations, including an OS reinstall
and an image restore from a known good point, I got WSUS with SSL to
work on Server 2012, but only on port 443. I was never able to get
clients to communicate properly on port 8531.

The default configuration of WSUS on Server 2012 is with http port 8530,
which I was able to get to work as well as port 80. After a server
rebuild (OS re-install), I downloaded all updates, configured WSUS, and
then changed to port 80 mode with the following command:

"c:\Program Files\Update Services\Tools\WsusUtil.exe" usecustomwebsite false

I saved an image of the server at that point because WSUS configuration
seems to be rather fragile. Then I created a binding in IIS for port
443 on the website with a certificate (from InCommon) selected in the
dropdown list of installed certificates and made the other SSL settings
necessary as documented on the web. Then I configured SSL for WSUS with
the following command:

"c:\Program Files\Update Services\Tools\WsusUtil.exe" configuressl
server.level3.msu.edu

where server.level3.msu.edu was a subject name from the installed
certificate.

The netsh commands I used to configure the firewall for WSUS were the
following:

advfirewall firewall
delete rule name="HTTP"
add rule name="HTTP" action=allow protocol=TCP dir=in localport=80
remoteip=LocalSubnet,192.168.113.0/24,35.8.0.0/13,35.20.0.0/17,35.22.0.0/17
advfirewall firewall
delete rule name="SSL"
add rule name="SSL" action=allow protocol=TCP dir=in localport=443
remoteip=LocalSubnet,192.168.113.0/24,35.8.0.0/13,35.20.0.0/17,35.22.0.0/17

Then, in Group Policy, I updated a policy object with the item "Specify
intranet Microsoft update service location" to specify the new server
address https://server.level3.msu.edu:443 (under Computer
Configuration/Administrative Templates/Windows Components/Windows Update)

-Stefan

On 5/2/2016 10:39 AM, David Graff wrote:
> Stefan,
>
> IPF runs their WSUS servers over SSL with InCommon certs, it does work and
> is worth doing. I believe the step that is missing from Microsoft's
> documentation is that you need to right click on the WSUS Administration
> site object in IIS manager, go to bindings, and then add your FQDN binding
> to https 8531 and/or 443 and assign your cert to the binding.
>
> Feel free to contact me if you would like assistance getting it set up.
>
> Dave Graff
>
> On Wed, 27 Apr 2016 14:20:49 -0400, Stefan Ozminski <[log in to unmask]> wrote:
>
>> <html>
>> <head>
>> <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
>> </head>
>> <body bgcolor="#FFFFFF" text="#000000">
>> I have had no response on this questing regarding WSUS with SSL.<br>
>> <br>
>> My guess is that everyone resorted to WSUS without SSL.<br>
>> <br>
>> I will share the script I use to configure the firewall on my WSUS
>> server. The rule for port 8530 is separate from 8531 in case I want
>> to expand the remoteip list for the SSL port 8531 at some future
>> time. I run this script after WSUS is installed so the wide open
>> WSUS rule is deleted.<br>
>> <br>
>> WSUSFirewall.cmd<br>
>> ----------------<br>
>> @echo off<br>
>> setlocal<br>
>> set scriptdir=%~dp0<br>
>> rem use %scriptdir% to reference folder from which this script is
>> run<br>
>> @whoami /groups | find "S-1-16-12288" &gt;nul<br>
>> @if errorlevel 1 (cscript /nologo
>> %scriptdir%..\kbsutils\RunCmdElevated.vbs %0 %*) &amp; exit /b<br>
>> netsh %1 %2 %3 %4 -f "%~dpn0.txt"<br>
>> endlocal<br>
>> <br>
>> WSUSFirewall.txt<br>
>> ------------------<br>
>> advfirewall firewall<br>
>> delete rule name="WSUS"<br>
>> delete rule name="WSUS8530"<br>
>> delete rule name="WSUS8531"<br>
>> add rule name="WSUS8530" dir=in action=allow protocol=tcp
>> localport=8530
>> remoteip=LocalSubnet,35.8.0.0/13,35.20.0.0/17,35.22.0.0/17
>> profile=domain<br>
>> add rule name="WSUS8531" dir=in action=allow protocol=tcp
>> localport=8531
>> remoteip=LocalSubnet,35.8.0.0/13,35.20.0.0/17,35.22.0.0/17
>> profile=domain<br>
>> <br>
>> -Stefan<br>
>> <br>
>> <div class="moz-cite-prefix">On 4/26/2016 2:26 PM, Stefan Ozminski
>> wrote:<br>
>> </div>
>> <blockquote cite="mid:[log in to unmask]" type="cite">
>> <meta http-equiv="content-type" content="text/html; charset=utf-8">
>> WSUS administrators,<br>
>> <br>
>> Has anyone had success setting up WSUS on Windows Server 2012 R2
>> with an SSL configuration?<br>
>> <br>
>> I've tried it twice now, and although the https connection works,
>> the clients don't communicate with the server properly. To make
>> it worse, when I follow the instructions <a
>> moz-do-not-send="true"
>> href="https://technet.microsoft.com/en-us/library/bb633246.aspx">How
>>
>> to Configure the WSUS Web Site to Use SSL</a>, I lose the
>> ability to open the administration console on the WSUS host, and
>> when you test client access with the url <a
>> moz-do-not-send="true" class="moz-txt-link-freetext"
>> href="https://"><a class="moz-txt-link-freetext"
> href="https://">https://</a></a>&lt;wsushost&gt;.kbs.msu.edu:8531/ClientWebService/Client.asmx?singleWsdl,
>> the xml returned contains references to <a moz-do-not-send="true"
>> class="moz-txt-link-freetext" href="http:8530">http:8530</a>
>> instead of <a moz-do-not-send="true"
>> class="moz-txt-link-freetext" href="https:8531">https:8531</a>.Â
>> Since the instructions say to lock the virtual directory
>> ClientWebService to SSL, it isn't going to work. Before you ask,
>> the answer is yes, I remembered to use wsusutil.exe configuressl
>> hostfqdn, and I configured the clients with the <a
>> moz-do-not-send="true" class="moz-txt-link-freetext"
>> href="https://hostfqdn:8531"><a class="moz-txt-link-freetext"
> href="https://hostfqdn:8531">https://hostfqdn:8531</a></a> that was
>> output to the Command Prompt window by wsusutil.exe.<br>
>> <br>
>> The initial HTTPS connection works. I can open the administrator
>> console on a server that is not the WSUS host and connect remotely
>> to the console interface of the WSUS host.<br>
>> <br>
>> The WSUS version that loads on my server when the role is enabled
>> is WSUS 6.3.9600.<br>
>> <br>
>> I have seen instructions that say the SSL certificate should
>> contain a Subject Alternative Name (SAN) that matches the friendly
>> name of the host (i.e. not FQDN), but that isn't possible
>> now-a-days with InCommon certificates.<br>
>> <br>
>> -Stefan<br>
>> <br>
>> </blockquote>
>> <br>
>> </body>
>> </html>
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2023
June 2023
May 2022
April 2022
March 2022
February 2022
December 2021
January 2019
August 2018
June 2018
May 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001

ATOM RSS1 RSS2



LIST.MSU.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager