Navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
Set UseWUServer = 0x00000000 (0)
Josh also suggested a server restart, which I did not do, and the change in the setting was apparently sufficient as the server would now accept the command and not spit it back at me.
As a final check, before continuing with configuration of the OpenSSH server, I ran this PowerShell command to check if it was installed as expected:
PS C:\windows\system32> Get-WindowsCapability -Online | Where-Object Name -like 'OpenSSH*'
Name : OpenSSH.Client~~~~0.0.1.0
State : Installed
Name : OpenSSH.Server~~~~0.0.1.0
State : Installed
So that now looks better than the red error lines. Now to get on with configuring.
Final thoughts: Why would WSUS be configured for a stand-alone server? and if it is then surely it is just a proxy for getting updates in any case, and should be used auto-magically. Apparently what is happening here is that in the Microsoft ‘user-friendly pretty picture interface’ WSUS works quietly in the background doing the updates, but if we step into the dark-side of command lines, the ‘GetWindowsCapability’ command is not intelligent enough to know that it might want to check-in with WSUS first before doing a dummy-spit.
“At least one other site is using the same HTTPS binding …..” is a prompt that every Windows Server IIS administrator has come across at some point. It arises when trying to change or update an SSL certificate on Windows server IIS platform where there are multiple websites and potentially multiple certificates.
Multiple Sites Using Same IP and SSL
Multiple sites sharing an IP address use a process of host-header recognition in order to accept the in-bound connection. Where this is on port 80 (http) there is no issue.
However, with port 443, the IP address and port number are also bound to a certificate and changing one site certificate will impact all the other sites on the same IP address and port combination. Hence the following Alert (error) message is displayed.
IIS SSL Multiple Sites Alert
Accepting or rejecting really depends on your server and what sites and certificates are actually in use. However, this may impact on the other sites and my past experience has been that other sites can be left in an unstable state either without a binding, a certificate, or a mix-up on which certificate.
Change SSL Certificate for Multiple Sites
Use the following steps to prepare manual change at the command line in order to avoid the above error message and address all sites using the same IP address : port and certificate at the same time.
All the detailed information has been sanitised to use dummy data, you will need to substitute the relevant information for your certificates and server.
First examine the certificates in use opening a command prompt – this is all read activity so Run as Administrator is not required, yet.
certutil -store My
This will display lists of certificates and applications like the following. I selected the 2 that I was looking for as follows:
the old certificate – based on NotBeforeDate – you need the highlighted hash from each certificate
================ Certificate 7 ================
Serial Number: 1234567890abcdef1234567890abcdef1234
Issuer: CN=AlphaSSL CA – G2, O=AlphaSSL
NotBefore: 01/01/2014 11:27 AM
NotAfter: 31/12/2016 11:27 AM
Subject: CN=*.yourdomain.tld, OU=Domain Control Validated
Non-root Certificate
Template:
Cert Hash(sha1): 12 34 56 78 90 ab cd ef 12 34 56 78 90 ab cd ef 12 34 56 78
Key Container = 12345a8277cd156abcd09d20dcba5c31_g3239vv5-8181-1234-b6ba-bbbb
78ccd34
Provider = Microsoft RSA SChannel Cryptographic Provider
Encryption test FAILED
CertUtil: -store command completed successfully.
and the new certificate – based on NotBeforeDate
================ Certificate 4 ================
Serial Number: 67890abcdef12341234567890abcdef12345
Issuer: CN=AlphaSSL CA – SHA256 – G2, O=GlobalSign nv-sa, C=BE
NotBefore: 01/01/2015 9:02 AM
NotAfter: 31/12/2016 11:27 AM
Subject: CN=*.yourdomain.tld, OU=Domain Control Validated
Non-root Certificate
Template:
Cert Hash(sha1): 78 90 ab cd ef 12 34 56 78 90 ab cd ef 12 34 56 78 12 34 56
Key Container = 1234abcd54d7161def4863d4d6b96633_f3239aa5-8080-1234-b6ba-abcd
78ccd34
Provider = Microsoft RSA SChannel Cryptographic Provider
Encryption test FAILED
Next, identify the ip address that is in use and, assuming that standard https is being used, port 443. This could be done by checking within IIS first to check which common IP address is being used.
netsh http show sslcert
Which will show all the ssl certificate bindings, or if you know which ipaddress, then be selective
netsh http show sslcert ipport=223.27.11.71:443
Will show the results like:
SSL Certificate bindings:
————————-IP:port : 223.27.11.71:443
Certificate Hash : 1234567890abcdef1234567890abcdef12345678
Application ID : {34567812-3456-7890-abcd-ef123456789d}
Certificate Store Name : MY
Verify Client Certificate Revocation : Enabled
Verify Revocation Using Cached Client Certificate Only : Disabled
Usage Check : Enabled
Revocation Freshness Time : 0
URL Retrieval Timeout : 0
Ctl Identifier : (null)
Ctl Store Name : (null)
DS Mapper Usage : Disabled
Negotiate Client Certificate : Disabled
The application ID is what is needed from the above but check that the correct certificate hash (the old one) is associated with this binding.
Now select all the relevant information from the results as shown
Old certificate hash (with spaces removed)
1234567890abcdef1234567890abcdef12345678
New certificate hash (with spaces removed)
7890abcdef1234567890abcdef12345678123456
and the AppID
{34567812-3456-7890-abcd-ef123456789d}
The following two steps will need a new elevated command window selected with ‘Run as Administrator’
Looking to deploy RDS on a stand-alone Windows 2012 Server I found a wealth of information where the authors make the assumption that you will use an Active Directory / Domain connected server.
A Microsoft team blog reference makes what I consider to be a fatal assumption in this reference RD Quick Start on a Domain Connected Server in stating that the instructions are suited to a small office deployment or as a proof of concept deployment. My take on a proof of concept is that a domain configuration is a lot of extra work for little value.
Assumption: Using a single server for a small office and limited user environment. A larger office, more users, more management option would require more than 1 server and separation of server roles.
Two methods depending on the server status of domain connected or stand-alone.
Deploy RDS on a stand-alone Windows 2012 Server using Role Based installation
This installation method assumes that the server is not connected to a domain.
2. Deploy the RDS 2012 Session Host Role and the RDS licencing role
3. This will provide the role of Remote Desktop Services and 2 role services of Session Host and Desktop Licensing.
This method will not provide some features for management that are commonly referenced for ‘best practice’ as the vast majority of documentation assumes a domain based server has been used.
Deploy RDS on Domain connected Windows 2012 Server
As per the heading this installation assumes that the server is domain connected with an Active Directory. These steps are taken from the Microsoft reference and are included here for comparison to the above stand-lone server deployment method.
1. On the server that will become the Connection Broker, logon with a domain account that is an administrator and start Server Manager. FromManagemenu item, selectAdd Roles and Features.
2. SelectRemote Desktop Services installation.
3. SelectQuick Start.
4. SelectSession-based desktop deployment.
5. Add your local server to theSelectedlist forSpecify RD Connection Broker server.
6. On theConfirm Selectionsdialog, checkRestart the destination server automatically if required.
7. The RDS session deployment will now begin the install to all the servers and components selected. A progress dialog will be shown and the server will reboot.
8. After reboot, log in and the progress dialog will be shown again and installation will continue.
9. After installation is complete, in the Server Manager Dashboard, there will be aRemote Desktop Servicesrole listed in the left navigation pane.
10. SelectingRemote Desktop Serviceswill display theOverviewof the new deployment. From this page, the next steps would be to add / specify both the license server and RD Gateway if needed.
A simple resolution that worked for me was to use the Microsoft Remote Desktop v 8.0.14 app from the App store rather than this Microsoft Remote Desktop Connection Client for Mac
