Category Archives: Windows Servers

Anything related to Windows servers

At least one other site is using the same HTTPS binding

“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

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’

Delete old binding

netsh http delete sslcert ipport=223.27.11.71:443

Then add new using hash and appid

netsh http add sslcert ipport=223.27.11.71:443 certhash=7890abcdef1234567890abcdef12345678123456 appid={34567812-3456-7890-abcd-ef123456789d}

which should result in

SSL Certificate successfully added

And finally if you want to check that it has been applied

netsh http show sslcert | findstr /R "7890abcdef1234567890abcdef12345678123456"

or to check that the old certificate hash is not still in use on another ipaddress:port binding use the above with the old certificate hash.

 

Reference: http://serverfault.com/questions/610841/replace-wildcard-certificate-on-multiple-sites-at-once-using-command-line-on-i

Deploy RDS on a stand-alone Windows 2012 Server

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.

So I searched some more and arrived at Ryan Mangans’ blog and his post on the simple Setup Windows stand-alone RDS server.

Deploy RDS on a stand-alone Windows 2012 Server

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.

Ref: http://ryanmangansitblog.com/2013/10/30/deploying-a-rdsh-server-in-a-workgroup-rds-2012-r2/

1. Using the Add Roles & Features Wizard

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.

Ref: http://blogs.technet.com/b/askperf/archive/2015/04/09/remote-desktop-services-rds-2012-session-deployment-scenarios-quick-start.aspx

1. On the server that will become the Connection Broker, logon with a domain account that is an administrator and start Server Manager. From Manage menu item, select Add Roles and Features.

2. Select Remote Desktop Services installation.

3. Select Quick Start.

4. Select Session-based desktop deployment.

5. Add your local server to the Selected list for Specify RD Connection Broker server.

6. On the Confirm Selections dialog, check Restart 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 a Remote Desktop Services role listed in the left navigation pane.

10. Selecting Remote Desktop Services will display the Overview of the new deployment. From this page, the next steps would be to add / specify both the license server and RD Gateway if needed.

Mac Windows Remote Desktop connection error licensing problem

Take a Mac PC or notebook and try to connect to a Windows server using the Version 2.1.1 of Microsoft Remote Desktop Connection Client for Mac.

It may (should) connect ok with a server that only has the administrative access remote desktop enabled.

But, it fails to work with a Remote Desktop Server (aka Terminal Services server).

2015-03-24_13-09-22_RDC_Error1

When you exit the application with Cancel rather than Reconnect, you may get a Microsoft Error Reporting prompt:

2015-03-24_13-09-22_RDC_Error2

and checking for More Information shows:

2015-03-24_13-09-22_RDC_Error3

which shows error details as follows:

*****

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2015-03-24 02:32:36 +0000
Application Name: Remote Desktop Connection
Application Bundle ID: com.microsoft.rdc
Application Signature: MSRD
Application Version: 2.1.1.110309
Crashed Module Name: libobjc.A.dylib
Crashed Module Version: unknown
Crashed Module Offset: 0x000010a7
Blame Module Name: TSClient
Blame Module Version: 1.0
Blame Module Offset: 0x000dcd5a
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409
Crashed thread: 13

****

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

Windows 2012 server and Public vs Private network change Location

First up I have to thank http://www.jenovarain.com/2012/09/server-2012-network-location/ for the starting point on this.

A Windows server without a domain was installed but it had both ethernet interfaces listed as Public networks which meant that specific firewall issues existed, including being unable to connect as a remote desktop user. Turning off the Windows software firewall was one option that did allow the RDP connection to be completed, but this was sub-optimal and not persistent after a reboot.

The above-mentioned URL held out the section of the Windows Server Tools that was needed to setup more open access to allow the user to change the network location from Public to Private.

  • In “Server Manager” open the “Tools” menu and select “Local Security policy”.
  • Select “Network List manager policies” in the console tree.
  • Open “All Networks” properties.
  • Change “Network location” to “User can change location”
  • Now reboot to apply the changes, or at a command prompt use gpupdate /force

But it did not work for me. What I found was that the existing network connection settings were not over-written with the global settings after the reboot.

In the same “Network List manager policies” section, I had to select the specific Network Location and apply the changes there as well. Once that was done, the location could be changed from Public to Private, and my server was accessible with the firewall turned on.