Certificate error when connecting via RDP: how to update/replace it?

Question

System administration

Good afternoon friends!

There is an RDP server based on a broken Windows 7.
It just so happened that on the server, for the correct operation of one tricky application, I had to set the system date to 2017 (in order to get rid of annoying pop-ups asking for an update).

In this regard, since the system date on the server is as much as 3 years behind, when connecting via RDP, the client swears that the certificate is bad, expired, and so on. Actually, if you look at the certificate received from the server, then yes: it was released in 2017. ends in 2018, but in reality on the client the year is 2020... Expired.

Question: how to change the certificate on the server (and where does it even lie and how is it generated) in such a way that it lives and does not grieve for at least 5 years ...? Is it possible?

Another version of perversions - if you suggest, I will be glad and grateful!

Answer 1

The problem was solved by editing the client RDP file. The certificate warning has fallen off. Turning off the authentication warning solved the problem. All the same, work on VPN is in progress, it is not critical.

Answer 2

return the correct date to the server.
crooked application - transfer to a virtual machine, or download a fake one)