We used Comodo for PCI scanning and although it had a dislike for the RDP port it still passed as a false positive.
Comodo have now sold their business to Sectigo and are using the Qualys engine for PCI scanning and it failed on this issue, with the solution being
Please install a server certificate signed by a trusted third-party Certificate Authority. Clearly there is a valid certificate for normal HTTPS connections.
Remote Desktop Session Host Configuration manager no longer seems to exist so pointing to a third party certificate that way is blocked.
Looking at this tutorial...
https://aventistech.com/2019/08/ssl-certificate-for-windows-remote-desktop-server/
...seemed like as solution, but it requires CA - Certification Authority Console
I installed that, but Enterprise CA was greyed out so proceeded with Standalone CA.
Turns out that Certificate Templates that I need are only installed with Enterprise CA.
Any ideas?
Thank you
======================= EDIT ==========================
Just a thought - 99.99% of the time RDP connections are only required from within our network - so limiting IP addresses to that range within the firewall for that port should block that hole. If I had to connect from outside our network would connecting to another server that doesn't have this blocked, then RDP to the restricted one work? I gather it is possible to chain RDP connections.