2012 r2 remote desktop services rd gateway

#2012 R2 REMOTE DESKTOP SERVICES RD GATEWAY INSTALL#
#2012 R2 REMOTE DESKTOP SERVICES RD GATEWAY SOFTWARE#

RDP_TCP: An error was encountered when transitioning from StatePreparingX224CC in response to Event_ERROR_SendingX224CC (error code 0x0). RemoteDesktopServer-RdpCoreTS/Admin (this happens when trying to connect from client) Remote-Desktop-Management-Service/Admin (this appears after the reboot)Ĭonfig sync failed. When it times out I can only find the below logged.ģ6871 Schannel (this happens when trying to connect from a client)Ī fatal error occurred while creating an SSL server credential. Server Side, with TLS 1.0 disabled, TLS 1.1 and TLS 1.2 enabled and 'Use FIPS compliant algorithms for encryption, hashing, and signing' policy disabled, the client stalls at the 'Configuring remote session' phase before timing out.Īgain, I'm aware this is related to but I'm interested in single server solutions and the suggestions in that article don't seem to have Server Side, with TLS 1.0 disabled, TLS 1.1 and TLS 1.2 enabled and the 'Use FIPS compliant algorithms for encryption, hashing, and signing' policy enabled, the client connects fine via RD Gateway. (Forgot to mention, I'm testing from Windows 7 clients that are completely up-to-date and have TLS 1.2 enabledĪnd also Wind/ 1803 clients and I'm unable to connect from either)Ĭan confirm my primary testing has been with Wind(I'll worry about Windows 7 later)

#2012 R2 REMOTE DESKTOP SERVICES RD GATEWAY INSTALL#

Has anyone successfully disabled TLS 1.0 and had a single server deployment working? If I absolutely have to I can install SQL Express on another VM but I'd like to avoid it if possible. I've been using the script at to ensure that TLS 1.0 is diabled, TLS 1.1 and 1.2 is enabled, insecure ciphers are disabled and the WinHTTP options are The wizard completed without issue and successfully moved the Connection Broker Database to my new SQL Express instance butĪfter I disable the FIPS policy (so I'm again back to just TLS 1.2) I start seeing the same SCHANNEL errors again and I'm again unable to connect via RDS/RDG I've tried installing SQL Express 2014 SP2 + CU13 on the same VM and have enabled High Availability on the Connection Broker. I'm aware of the knowledge base article at

#2012 R2 REMOTE DESKTOP SERVICES RD GATEWAY SOFTWARE#

I can work around this by enabling the Local Security Policy: Use FIPS compliant algorithms for encryption, hashing, and signing BUT this isn't ideal and breaks some other software packages (such as Sage Line 50 Authentication) that we use on this server. This all works fine until I disable TLS 1.0 - after disabling TLS 1.0 I receive the following errors whenever I try to connect via RDS/RDG 'A fatal error occurred while creating an SSL server credential. It has at most 4 people connected at any time. RD Licensing, RD Web Access, RD Session Host, RD Connection Broker, RG Gateway. I have a single Windows Server 2012 R2 remote desktop deployment, all roles on one VM.

2012 r2 remote desktop services rd gateway