Systems Engineer

Thomas NZ

<div>
<div class="content wysiwyg-content">
Hello,<br />
<br />
Got a rather odd situation here.<br />
<br />
There is three servers and the setup is this -<br />
2019 Domain Controller<br />
2019 Connection broker running RD Gateway and RD licensing server<br />
2019 Remote desktop session host<br />
<br />
This is a brand new environment setup from scratch. The 2019 1809.2 ISO was used for all Windows installation.<br />
<br />
When I open up RD licensing diagnoser on the RDSH, it thinks that my session host is running 2016 when there are no 2016 servers anywhere (attached screenshot). The same thing happened to all 2019 environments I've come across so far as well. All relevant regkeys, group policies, etc are pointing the session hosts to use the correct RD licensing server. In all cases, the RD licensing servers are issuing 2019 RDS user CALs correctly as well.<br />
<br />
We have done hundreds of RD environment setups with 2012 and 2016 before and had never encountered this. Our RDSHs are all domain joined.<br />
<br />
I've done some Googling already and looks like I'm not the only one seeing this, but I can't see any solution so far. Is this a new bug with 2019?
</div>
</div>


Hello,

Got a rather odd situation here.

There is three servers and the setup is this -
2019 Domain Controller
2019 Connection broker running RD Gateway and RD licensing server
2019 Remote desktop session host

This is a brand new environment setup from scratch. The 2019 1809.2 ISO was used for all Windows installation.

When I open up RD licensing diagnoser on the RDSH, it thinks that my session host is running 2016 when there are no 2016 servers anywhere (attached screenshot). The same thing happened to all 2019 environments I've come across so far as well. All relevant regkeys, group policies, etc are pointing the session hosts to use the correct RD licensing server. In all cases, the RD licensing servers are issuing 2019 RDS user CALs correctly as well.

We have done hundreds of RD environment setups with 2012 and 2016 before and had never encountered this. Our RDSHs are all domain joined.

I've done some Googling already and looks like I'm not the only one seeing this, but I can't see any solution so far. Is this a new bug with 2019?

RD licensing diagnoser is saying my 2019 RDSH is running 2016

Remote access may refer to the connection to a data-processing system from a remote location, for example through a virtual private network remote desktop software, terminal emulation, or the activation of features of a business telephone system from outside the business's premises.

Remote Access

remote desktop farm

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.