a small update to this.
i now have a windows 2012 server in a test environment.
IIS8 has been set up with 8 “sites”, but in this instance they are all the same domain but set up as individual sub-domain sites.
this now gives me the “require server name identification” field that can be enabled on each site.
at the moment all the sites have this disabled and they are configured solely for HTTP on port 80.
so is my next step to enable SNI on each of the sites?
do i need to add an HTTPS binding to any of them?
Indeed, but it’ll still be 1 IP with multiple SSL sites, so unless iis8 now lets me add Https bindings to all the sites I’ll still have the same issues?
Yes, IIS 8 will allow you to add HTTPS bindings to individual Web Sites, whereas the IIS 7 you were using before only allowed you to add HTTPS bindings to IP addresses.
Note that Let's Encrypt clients for Windows like Certify and win-acme will automatically configure the binding for you based on your domain name when you request a certificate, so you usually don't need to configure this manually.
even if there is more than 1 domain name?
this test server only has 1 domain (albeit several sub-domains of the same domain).
but the end result will be a server with several different top-level domains (with sub-domains of some of them).