<div>
This is a known issue<br />
<br />
<a href="https://support.microsoft.com/en-us/help/4036954/disabling-tls1-0-can-cause-rds-connection-broker-or-rdms-to-fail" rel="ugc">https://support.microsoft.com/en-us/help/4036954/disabling-tls1-0-can-cause-rds-connection-broker-or-rdms-to-fail</a><br />
<br />
TL;DR<br />
<br />
Set up RDS without Connection Broker for a single server installation.<br />
Do not disable TLS 1.0 on a single Connection Broker deployment.<br />
Configure a high availability Connection Broker deployment that uses dedicated SQL Server.<br />
Note Microsoft has released an update to enable SQL Server communication to use TLS 1.2.
</div>


<div>
How did you disable TLS 1.0?<br />
<br />
This should be the good point to do it.<br />
<a href="https://gallery.technet.microsoft.com/office/Enable-TLS11-and-TLS12-in-f41c9ab0" rel="ugc nofollow">https://gallery.technet.microsoft.com/office/Enable-TLS11-and-TLS12-in-f41c9ab0</a><br />
<br />
Please be specific on what you did.
</div>


<div>
What about unchecking the NLA option in the target server RDP setting ?
</div>


<div>
You mean this option.<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2018/10_w41/1392141/10-Oct-18-10-23-45-AM.jpg" target="_blank" title="10-Oct-18-10-23-45-AM.jpg (125 KB)"><img alt="10-Oct-18-10-23-45-AM.jpg" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2018/10_w41/800_1392141/10-Oct-18-10-23-45-AM.jpg" /></a>
</div>


10-Oct-18-10-23-45-AM.jpg

<div>
Dear Jose Gabriel Ortega Castro,<br />
<br />
I have disabled the SSL 2.0 SSL 3.0 and TLS 1.0 by this. <br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2018/10_w41/1392144/10-Oct-18-10-26-34-AM.jpg" target="_blank" title="10-Oct-18-10-26-34-AM.jpg (113 KB)"><img alt="10-Oct-18-10-26-34-AM.jpg" class="file-block lazyload" style="max-width: 672px;" data-src="https://filedb.experts-exchange.com/incoming/2018/10_w41/1392144/10-Oct-18-10-26-34-AM.jpg" /></a>SAME FOR SSL 3.0 and TLS 1.0<br />
<br />
<br />
And Enabled TLS 1.1 and TLS 1.2 by this,<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2018/10_w41/1392145/10-Oct-18-10-28-30-AM.jpg" target="_blank" title="10-Oct-18-10-28-30-AM.jpg (122 KB)"><img alt="10-Oct-18-10-28-30-AM.jpg" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2018/10_w41/800_1392145/10-Oct-18-10-28-30-AM.jpg" /></a>SAME FOR TLS 1.2
</div>


10-Oct-18-10-28-30-AM.jpg

10-Oct-18-10-26-34-AM.jpg

<div>
Dear David Johnson, CD, MVP,<br />
<br />
Please see that i have to disabled TLS 1.0 its MANDATORY for vulnerability.<br />
<br />
Thanks
</div>


<div>
Dear David Johnson, CD, MVP,<br />
<br />
Your link said ONE OF THE FOLLOWING METHODS so its mean any one i can choose.<br />
<br />
Can you please tell how can i do these steps.<br />
<br />
<u><i>Set up RDS without Connection Broker for a single server installation.</i></u><br />
<br />
Thanks
</div>


<div>
remove connection broker from remote desktop services.<a href="https://filedb.experts-exchange.com/incoming/2018/10_w41/1392152/2018-10-10_1-46-38.png" target="_blank" title="2018-10-10_1-46-38.png (76 KB)"><img alt="2018-10-10_1-46-38.png" class="file-block lazyload" style="max-width: 778px;" data-src="https://filedb.experts-exchange.com/incoming/2018/10_w41/1392152/2018-10-10_1-46-38.png" /></a>
</div>


2018-10-10_1-46-38.png

<div>
Dear David,<br />
<br />
I have following settings and Connection Broker is already not selected please see below screenshot.<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2018/10_w41/1392153/10-Oct-18-10-49-20-AM.jpg" target="_blank" title="10-Oct-18-10-49-20-AM.jpg (152 KB)"><img alt="10-Oct-18-10-49-20-AM.jpg" class="file-block lazyload" style="max-width: 725px;" data-src="https://filedb.experts-exchange.com/incoming/2018/10_w41/1392153/10-Oct-18-10-49-20-AM.jpg" /></a>
</div>


10-Oct-18-10-49-20-AM.jpg

<div>
I had a similar bug on my script but it was solved &nbsp;On this question:<br />
<a href="https://www.experts-exchange.com/questions/29055597/Remote-Desktop-TLS-1-0.html" rel="ugc">https://www.experts-exchange.com/questions/29055597/Remote-Desktop-TLS-1-0.html</a><br />
<br />
So it's safe to use this script, it has all the documentation in it.<br />
<a href="https://gallery.technet.microsoft.com/scriptcenter/Solve-SWEET32-Birthday-d2df9cf1" rel="ugc nofollow">https://gallery.technet.microsoft.com/scriptcenter/Solve-SWEET32-Birthday-d2df9cf1</a>
</div>


<div>
Have you installed this update.<br />
<br />
<a href="https://support.microsoft.com/en-us/help/4074621/add-rds-support-for-tls-1-1-and-tls-1-2-in-windows-server-2008-sp2" rel="ugc">https://support.microsoft.com/en-us/help/4074621/add-rds-support-for-tls-1-1-and-tls-1-2-in-windows-server-2008-sp2</a>
</div>


<div>
Dear Zaheer Iqbal,<br />
<br />
We have resolved the problem on windows 2008 r2. This is not an issue.<br />
<br />
PROBLEM is with Windows 2012 R2.<br />
<br />
Thanks
</div>


<div>
Dear Jose Gabriel Ortega Castro,<br />
<br />
Can you please confirm how to revert the SCRIPT if any thing bad happens on PRODUCTION SERVER. ??
</div>


<div>
Dear Jose Gabriel Ortega Castro<br />
<br />
I run the script but still error is same.<br />
But after the script TLS 1.1 has also disabled. &nbsp;Now only TLS 1.2 is enabled in whole server . TLS 1.0 and TLS 1.1 is disabled.<br />
<a href="https://filedb.experts-exchange.com/incoming/2018/10_w41/1392187/10-Oct-18-12-38-00-PM.jpg" target="_blank" title="10-Oct-18-12-38-00-PM.jpg (128 KB)"><img alt="10-Oct-18-12-38-00-PM.jpg" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2018/10_w41/800_1392187/10-Oct-18-12-38-00-PM.jpg" /></a>
</div>


10-Oct-18-12-38-00-PM.jpg

Netsol-NOS

<div>
Its Works.<br />
After install below updates on &nbsp;Windows 7 &nbsp;my workstation starts connecting Windows 2012 R2 through RDP.<br />
1) &nbsp;Windows6.1-KB2574819-v2-x6<wbr />4<br />
2) &nbsp;Windows6.1-KB2592687-x64<br />
<br />
Note that on Windows 2012 R2 TLS 1.0 is disabled and TLS 1.1 and TLS 1.2 is enabled.
</div>


<div>
<div class="content wysiwyg-content">
Dear EE,<br />
<br />
Remote Desktop has been disabled after i perform following settings on Microsoft Windows 2012 R2.<br />
<br />
DISABLED TLS 1.0<br />
ENABLED TLS 1.1<br />
ENABLED TLS 1.2<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2018/10_w41/1392134/10-Oct-18-10-02-53-AM.jpg" target="_blank" title="Error (29 KB)"><img alt="Error" class="file-block lazyload" style="max-width: 493px;" data-src="https://filedb.experts-exchange.com/incoming/2018/10_w41/1392134/10-Oct-18-10-02-53-AM.jpg" /></a><br />
Please see attached error<br />
<br />
Thanks
</div>
</div>


10-Oct-18-10-02-53-AM.jpg

Dear EE,

Remote Desktop has been disabled after i perform following settings on Microsoft Windows 2012 R2.

DISABLED TLS 1.0
ENABLED TLS 1.1
ENABLED TLS 1.2



Please see attached error

Thanks

RDP Lost after Disable TLS 1.0 on Windows 2012 R2

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

A desktop computer is a personal computer designed for use at a single location due to its size and power requirements, usually by one person. The most common configuration has a case that houses the power supply, motherboard, disk storage (usually one or more hard disk drives and optical disc drives); a keyboard and mouse for input; and computer monitor and printer for output. The case may be oriented horizontally and placed atop a desk or vertically and placed underneath or beside a desk.