Hi,
I'm currently in the process of evaluating Windows 2012 with a view to upgrading out existing infrastructure. We current have somewhere in the region of 300 Windows 2008 R2 servers being accessed via 6 RD Gateway servers. Customers access their applications either via remote app or directly on the desktop via the RD Gateways. The servers, apps, gateways all use a common Thawte SSL123 certificate/URL (mygateway.mydomain.com). This works perfectly so I was looking forward to setting this up on Windows 2012.
Annoyances with the interface aside I am unable to sign the RDP files with my certificate from Thawte because it would appear that Microsoft have now decided the certificate should be authorised for "Client Authentication" now instead of "Server Authentication".
Can anyone confirm if this is the case and the reasoning behind it and what certificates we now need to purchase to be able to sign RDP files.
Thanks in advance.
Paul