大网数据广告活动
服务器运维问答

How to disable TLS 1.0 without breaking RemoteApps on server 2012 R2

· 52CE 我爱测

Please note, this scenario is different from asimilar one: How do I disable TLS 1.0 without breaking RDP? The linked question is about RDP and disabling TLS 1.0. This question is about RemoteApp's and disabling TLS 1.0 I already …

问题原文

原帖链接 · Phil Sayers · CC BY-SA 3.0

Please note, this scenario is different from asimilar one: How do I disable TLS 1.0 without breaking RDP?

The linked question is about RDP and disabling TLS 1.0.

This question is about RemoteApp's and disabling TLS 1.0

I already have straight RDP over port 3389 working with TLS 1.2.

We have a 2012R2 Server hosting RemoteApp's.

We have the RD Gateway, RD Web Access, RD Connection Broker, RD Session Host roles installed on this server.

RemoteApp's are served through the RD Gateway over https. The only public port we have open is 443.

We have a public CA supplied wildcard SSL certificate installed in all of the RD Roles and IIS, so everything traces back to a trusted root cert.

The cert supports TLS 1.2, I see this in a webbrowser when I view the RDWeb website.

We are tying to disable TLS 1.0 on this server to tighten up the security. We are using IISCrypto 2.0 to disable TLS 1.0

When we disable TLS 1.0 two things are observed:

1.The RemoteApp's stop working. They cannot be launched from an end user machine.

2.Straight RDP connections work just fine.

When we re-enable TLS 1.0 the RemoteApp's work again.

SChannel logging confirms that RemoteApps are using TLS 1.2, so I would expect the RemoteApps to continue working when TLS 1.0 is disabled. However that is not what I am observing.

All client's are using fully updated/patched versions of Windows 8.1 and 10.

已采纳解答

原帖链接 · cardiothoracics · CC BY-SA 3.0

After almost a year, I finally figured out a working solution for disabling TLS 1.0/1.1 without breaking RDP and Remote Desktop Services connectivity.

Run IISCrypto and disable TLS 1.0, TLS 1.1 and all bad ciphers.

On the Remote Desktop Services server running the gateway role, open the Local Security Policy and navigate to Security Options - System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing. Change the security setting to Enabled. Reboot for the changes to take effect.

Note that in some cases (especially if using self signed certificates on Server 2012 R2), the Security Policy option Network Security: LAN Manager authentication level may need to be set to Send NTLMv2 responses only.

Let me know if this works for you as well.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2017-01-17)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。