Windows Server 2012 Termsrv.dll 53 !!HOT!!

If you want to connect to a Windows Server 2016 or later version of Windows Server Essentials, then you will have to use the RDS client that comes with Windows Server 2019 and Windows Server OS-based hypervisors. If you want to use the RDS client of Windows Server 2012, then you'll have to use the RDS client of Windows Server 2016, which is released as a standalone executable.

The RDS client that comes with Windows Server 2016 and later versions is also incompatible with Windows Server 2019 and Windows Server OS-based hypervisors. You can only connect to Windows Server 2016 or later versions of Windows Server Essentials (the free edition, and not the enterprise edition) or Windows Server 2019 and Windows Server OS-based hypervisors.

When I was asked whether I could confirm that the TS version of the RDS client would be compatible with Windows Server 2016 Essentials (and that it would work with Windows Server 2017, too), I immediately replied that I haven't tested it and it is entirely possible that some changes were made to the TS client that would make it incompatible with Windows Server 2016 and later. At the time of writing, there is no specific documentation in the MSDN or other official documentation regarding the RDS client in Windows 10, but the TS version of the RDS client appears to be a stand-alone executable and not part of the Windows 10 (RSAT) or the Windows 10 for business (WSAT) or Server Core installations.

I got used to tsconfig.msc and tsadmin.msc (aka Terminal Services Configuration / Terminal Services Administration MMC snapins) from the previous Windows versions and thus profoundly hate the new-style RDMS user interface which is intended as the replacement according to the documentation (Hyper-V as a requirement? Why would I ever need Hyper-V on a terminal server?!). 827ec27edc