Windows RDP Problem: Problems with the security certificate

[bughHD]

So while I tried to connect to one of my PC running Windows 8.1 Pro via Microsoft's Remote Desktop, this warning message came up: 

So other than just clicking the "Don't ask me again for connections to this computer", how can I solve this problem?

[thekeemo]

you get a certificate from microsoft

[bughHD]

you get a certificate from microsoft

How do I do that?

[thekeemo]

How do I do that?

no idea but I found this http://windows.microsoft.com/en-ca/windows/certificate-faq#1TC=windows-7im expecting $$$

[bughHD]

no idea but I found this http://windows.microsoft.com/en-ca/windows/certificate-faq#1TC=windows-7im expecting $$$

Should I get it? Or is it safe without the certificate that I can just ignore the message?

[thekeemo]

Should I get it? Or is it safe without the certificate that I can just ignore the message?

yea ignore it its totally safe

[bughHD]

yea ignore it its totally safe

Cool. Thanks for helping out. Btw, do you mind explaining what this whole certificate process do and why does it do it?

[thekeemo]

Cool. Thanks for helping out. Btw, do you mind explaining what this whole certificate process do and why does it do it?

I honestly have no idea and its for windows to say that THEY trust you

[1823alex]

Cool. Thanks for helping out. Btw, do you mind explaining what this whole certificate process do and why does it do it?

Certificates like these should be ignored unless you are in a high security environment generally, like a data center, or some sort of secure IT workplace. It is safe to ignore it. It is to warn you that the computer has never been connected to before and than Microsoft can not confirm or deny that the connection is safe and I would believe to keep Microsoft from being a liability. I believe the way it works is that when you RDP you have an incoming/outgoing connection so both parties are liable to some sort of damage of sorts.

TL;DR = Safe to ignore unless you work in high security workplace or somewhere like that. Keeps Microsoft from being liable to damages caused to either parties' computers, and warns you that man in the middle attack is possible (I think).