How to set WSUS Administration MMC Console to SSL Port 8531?

We have SSL set up on the WSUS server so that the clients connect and get
updates over port 8531.
This part works fine. Clients get updates and windsowsupdate.log shows they
are using the secure 8531 port.

I don't understand what else needs to be done so that when we open the
administrative console, that opens with an SSL connection.

I have already tried running the command:
wsusutil configuressl wsusservname.domain.local

The response in the command window is:

URL: http://WSUSServername:8530

I have already looked at the Microsoft site:
http://technet.microsoft.com/en-us/l.../bb633246.aspx
but there is too much information and I don't understand what part were are
missing for just the console connection.

If the WSUS server already has SSL working for client updates and reporting,
what are the remaining steps to make the WSUS Administrative Console also
work with SSL?

"Mygposts" <Mygposts@discussions.microsoft.com> wrote in message
news:187FD8A4-38B6-44A4-B061-99F01C9561AF@microsoft.com...
> We have SSL set up on the WSUS server so that the clients connect and get
> updates over port 8531.
> This part works fine. Clients get updates and windsowsupdate.log shows
> they
> are using the secure 8531 port.
>
> I don't understand what else needs to be done so that when we open the
> administrative console, that opens with an SSL connection.

Same thing you did at the WSUS client sites.


> I have already tried running the command:
> wsusutil configuressl wsusservname.domain.local

Which only configures the SERVER.. not the console.



> I have already looked at the Microsoft site:
> http://technet.microsoft.com/en-us/l.../bb633246.aspx
> but there is too much information and I don't understand what part were
> are
> missing for just the console connection.

"Too much information" is usually a good indication that the answer is
buried somewhere within. Choosing to not read and research the question
because there's "too much information" and "I don't want to make the effort
to actually read and study because I'd rather have somebody give me the easy
answer"... well... I'm not impressed.

Reading the Deployment Guide and the Operations Guide is pretty much
*required* if you wish to be successful with this product.


> If the WSUS server already has SSL working for client updates and
> reporting,
> what are the remaining steps to make the WSUS Administrative Console also
> work with SSL?

Luckily for you, I'm going to give you the easy answer:

=== Install the certificate and point the console at the right URL ===


But may I suggest that you don't ever again post in a message asking for
help a statement that there was "too much information", and make the
implication you weren't interested in making the effort on your own when
presented with the information.






--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Instead of "too much" information, then it is "not clear enough" information.
It wouldn't matter if they had 1000 pages of info, if it was easier to find
what you need and the instructions were more clear.

I asked someone else before posting here and they referred me to the
Microsoft URL I posted in the first message.
I went to the Microsoft page, read it and still didn't understand what or
how to do just the parts needed for the console, so I posted here for more
clarifcation, then you reply with lectures.

"Lawrence Garvin [MVP]" wrote:

> "Mygposts" <Mygposts@discussions.microsoft.com> wrote in message
> news:187FD8A4-38B6-44A4-B061-99F01C9561AF@microsoft.com...
> > We have SSL set up on the WSUS server so that the clients connect and get
> > updates over port 8531.
> > This part works fine. Clients get updates and windsowsupdate.log shows
> > they
> > are using the secure 8531 port.
> >
> > I don't understand what else needs to be done so that when we open the
> > administrative console, that opens with an SSL connection.
>
> Same thing you did at the WSUS client sites.
>
>
> > I have already tried running the command:
> > wsusutil configuressl wsusservname.domain.local
>
> Which only configures the SERVER.. not the console.
>
>
>
> > I have already looked at the Microsoft site:
> > http://technet.microsoft.com/en-us/l.../bb633246.aspx
> > but there is too much information and I don't understand what part were
> > are
> > missing for just the console connection.
>
> "Too much information" is usually a good indication that the answer is
> buried somewhere within. Choosing to not read and research the question
> because there's "too much information" and "I don't want to make the effort
> to actually read and study because I'd rather have somebody give me the easy
> answer"... well... I'm not impressed.
>
> Reading the Deployment Guide and the Operations Guide is pretty much
> *required* if you wish to be successful with this product.
>
>
> > If the WSUS server already has SSL working for client updates and
> > reporting,
> > what are the remaining steps to make the WSUS Administrative Console also
> > work with SSL?
>
> Luckily for you, I'm going to give you the easy answer:
>
> === Install the certificate and point the console at the right URL ===
>
>
> But may I suggest that you don't ever again post in a message asking for
> help a statement that there was "too much information", and make the
> implication you weren't interested in making the effort on your own when
> presented with the information.
>
>
>
>
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My Websites: http://www.onsitechsolutions.com;
> http://wsusinfo.onsitechsolutions.com
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>

"Mygposts" <Mygposts@discussions.microsoft.com> wrote in message
news:26A8AA6E-C923-41C9-B670-599C27F9490D@microsoft.com...

> Instead of "too much" information, then it is "not clear enough"
> information.
> It wouldn't matter if they had 1000 pages of info, if it was easier to
> find
> what you need and the instructions were more clear.
>
> I asked someone else before posting here and they referred me to the
> Microsoft URL I posted in the first message.

Which is not only the wrong section to read to configure the console, it's
the wrong documentation for the product! The link you posted is the System
Center Configuration Manager documentation. (No real wonder you can't find
anything on the WSUS console!) -- though, as you see, it does have a section
on how to configure the WSUS WebSite to use SSL, because using WSUS is a
common practice in System Center Configuration Manager deployments.

But helping you navigate or use the Technet Library is really beyond the
scope of this forum.


> I went to the Microsoft page, read it and still didn't understand what or
> how to do just the parts needed for the console, so I posted here for more
> clarifcation, then you reply with lectures.

So, let's try the =WSUS= documentation.
Starting from the WSUS Home Page
http://www.microsoft.com/wsus

The WSUS Deployment Guide is linked in the left pane under the title "3.
Install and Learn WSUS 3.0"
http://go.microsoft.com/fwlink/?LinkId=79983

which will take you to this location in the Technet library
http://technet.microsoft.com/en-us/l.../cc720507.aspx

which is in the Systems Management | Update Management | Windows Server
Update Services leaf of the tree
rather than Systems Management | System Center | System Center Configuration
Manager where your link took you.

And the specific (correct) section on how to configure SSL for WSUS that you
want to read is this:
http://technet.microsoft.com/en-us/l.../cc708467.aspx


You may also find the WSUS Operations Guide of some use
http://go.microsoft.com/fwlink/?LinkId=81072

which will take you to this location in the Technet library
http://technet.microsoft.com/en-us/l.../cc708540.aspx


Also, the specific section of the Deployment Guide discussing how to
install/connect the Administration Console is here:
http://technet.microsoft.com/en-us/l.../cc720498.aspx


Now, as to the simple matter of connecting the MMC to the correct server, I
apologize that my simple instructions were apparently not detailed enough
(and that you had so much difficulty finding this information in the
documentation),
so here are the *detailed* instructions (which can be found in the very last
paragraph of the link given above):


1. Disconnect the "broken" (non-SSL) link to the server (if it's there), by
right clicking on the server node and selecting "Remove From Console".

2. Right click on the "Update Services" node and select "Connect to
Server..."

3. Fill in the blanks:
[a] Server name
[b] Port number
[c] And check the box next to the phrase "Use Secure Sockets Layer (SSL)
to connect to this server."

4. Close the console and say YES to the option to save the console settings.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin