Recently my organization moved to a cloud server and everyone connects via remote desktop. I wasn't the one who set up the server and person who did is gone so I can't just ask them. We don't user the server for any web services thus we have no FQDN for it.
Just over the last few days, when users go in via remote desktop they get the warning that the computer cannot be authenticated due to problems with the certificate. It says the certificate is not from a trusted authority and if, from there choose to view the certificate, it tells me that "This CA root certificate is not trusted. To enable trust install this certificate in the Trusted Root Certification Authorities store" the valid from and to dates are current (the from date started a couple days ago, when people started getting this warning) and the from and to issuer are the same and appear to be the name of the server.
But if I ignore the warning and go on the server I don't know what to do. I tried to do what they say and install this certificate in the Trusted Root (i.e. mmc-> add snap in blah blah ) but when it gets to the point of actually adding it to the root I can't find the certificate. I tried searching the whole server for a certificate with that name or something similar and and it can't find it. Where the heck is it if it's already there and waiting to be put in the trusted root?
Then I tried buying a certificate but that didn't work either because the issuer rejects the CSR I create because we don't have a FQDN. Then they ask me to get a FQDN. If that's all required, how was it working for 3 months?
I know this cannot be that difficult but have searched for days online and can't find a solution that applies to this particular issue of apparently having (I guess) a self-signed certificate for Remote Desktop.