Hi there,
we migrated a client off of SBS 2003 to Server 2012 Standard with Exchange 2012 Standard. Note Exchange is on the machine :).
We installed Remote Desktop Gateway on this server after Exchange. This screwed over Exchange, as the bindings in IIS were messed up (exchange registered 127.0.0.1:443 and <nothing>:443 and RDGW *:443 or similar). Anyways, if we remove the additional bindings things get really interesting. IIS starts again, Exchange works (it does a lot through IIS now which is... well let's just say I'm not a fan of it, bork up IIS and you'll have no exchange, no management interface and no powershell (powershell connects through IIS, ain't that nice)) and RDGW - well, it does something.
I have the RD policies. The configuration utility of RDGW will keep on complaining there's no certificate configured. This is probably because it's missing it's own binding, since it should use the same default website as exchange (which creates 2 now - but the backend runs on 81 and 444) it should be fine with the cert attached to the site exchange created. If we try to configure the certificate from there it will go on, but it will break exchange again. We remove the additional bindings then and this error returns in the management tool.
Anyways, as I said, it gets interesting. As stated this is at a clients location. If we use XP to connect over the RDGW it will always fail with a message the remote desktop gateway is temporarily unavailable. The usual solution with the CredSSP enabling does not resolve this.
The interesting part is Windows 7. All machines we have here at our office (not on the clients site thus) can connect just fine over the RDGW. These are all joined to our domain, which still runs SBS 2011. Our 2008 R2 Terminal Server connects fine too. My Windows 7 at home and several of the clients employees with their own Windows 7 machines can not connect however. Same message as XP, the remote desktop gateway server is temporarily unavailable.
Can't seem to figure out what the difference would be between our Win7 clients at the office and the rest. It's not the firewall rules - I have the same access to their firewall at my home and it fails there.
Any ideas? It would be nice if we could just tell RDGW to use the default site (and the already existing bindings on it) too. Hope that prevents it from messing up IIS again.
TIA