Unfortunately, my understanding of NAP is fairly limited at this stage so I don't know where to start there. It's only happening via the public internet.
#2012 r2 remote desktop services ssl certificate mac os x#
It only happens to this one user (and it was working previously for him), and I can still connect via other Windows 7 and Mac OS X clients.ĮDIT: This also does not happen when this user is on our LAN or tunnelled in via a VPN. I cannot work out what is causing this issue. Contact your network administrator for assistance." Web Certificates would result in secure and encrypted communication, both internal or external. A Windows 8.1 client (not on my domain) gets the following error message when trying to connect to RemoteApps: "Your computer can't connect to the remote computer because your computer or device did not pass the Network Access Protection requirements set by your network administrator. Step by step guide to install and configure SSL Certificate.
This was all working fine until recently. Previously called Terminal Services prior to Windows 2008 R2, there are many more features and it provides a much more robust environment than previous versions. By Default, in Windows 2012 R2 (IIS 8.5) if you generate the Self-Signed Certificate from the IIS Manager Console it will provide a Self-Signed Certificate with the Signature hash algorithm as sha1. I've also installed a "real" SSL certificate (using the server's external FQDN, not the internal one). Remote Desktop Services enables virtual desktop infrastructure, session-based desktops, and applications, allowing users to work anywhere. But he wants to use the Self Signed Cert with the sha256 Signature Hash algorithm on Windows Server 2012 R2 as sha1 is retired. I've accepted the default values pretty much all throughout the setup process.
It has the basics: RD Gateway, RD Web Access and RD Connection Broker.
I have installed Remote Desktop Services on a fresh Windows Server 2012 R2 Datacenter VM.
0 kommentar(er)
