Windows Server 2012 Remote Desktop For Mac

Windows Server 2012 Remote Desktop For Mac Average ratng: 6,8/10 1788 reviews
  1. Windows Server 2012 Remote Desktop Services 5-device Cal

I'm trying to remote onto a Windows 2012 Server using Remote Desktop Connection for Mac. Using the same credentials, it works from my Windows PC (using Remote Desktop for Windows), but trying to do it from my Mac I get the error: Remote Desktop Connection cannot verify the identity of the computer that you want to connect to. Try reconnecting to the Windows-based computer, or contact our administrator.

• Instant Digital download access to everything you purchase. • Free best-in-class customer support with real representatives waiting to provide assistance. Microsoft office for mac.

Canon mp620 driver for mac 10.9. I'm trying to have a RDP client on Windows Server 2012 But still no success, I don't understand why something that easy is so cumbersome on winserver 2012 I just need to install the feature to co. Adobe photoshop cs5 extended.

Windows Server 2012 Remote Desktop For Mac

Is it possible that the remote server allows connects from only Windows clients? Any help greatly appreciated. I doubt this a 'problem' with the mac as such nor does it have anything to do with Remote Desktop for Mac which is an entirely different product and for which this forum is for. Questions about RDC for Mac should be put on the relevant Microsoft forum rather than here. However your problem may be with your understanding of the secure remote connections requirements between your server and remote connections. I doubt you'd be aware of any of this as generally server administrators won't necessarily discuss them.

By default a mac will not have server-client trust certificates installed simply because the exchange won't happen transparently between an MS based server and non MS-OS such as OS X. You begin to solve the problem by asking your server administrator for the server's root certificate. He/she has to export this using the built-in tools. They should know how to do this? Once exported save it to a memory stick, insert it into your mac, double click on the.cer file and when prompted install it as a system keychain. On further prompts make sure you select 'Always Trust'. Launch RDC for Mac and you should be OK?

If your server administrator does not know how or, worse still, won't do this for you, then you have far deeper problems that go well beyond OS X in particular and IT as a whole in general. I doubt this a 'problem' with the mac as such nor does it have anything to do with Remote Desktop for Mac which is an entirely different product and for which this forum is for. Questions about RDC for Mac should be put on the relevant Microsoft forum rather than here.

However your problem may be with your understanding of the secure remote connections requirements between your server and remote connections. I doubt you'd be aware of any of this as generally server administrators won't necessarily discuss them. By default a mac will not have server-client trust certificates installed simply because the exchange won't happen transparently between an MS based server and non MS-OS such as OS X. You begin to solve the problem by asking your server administrator for the server's root certificate.

He/she has to export this using the built-in tools. They should know how to do this? Once exported save it to a memory stick, insert it into your mac, double click on the.cer file and when prompted install it as a system keychain. On further prompts make sure you select 'Always Trust'.

Windows Server 2012 Remote Desktop Services 5-device Cal

Launch RDC for Mac and you should be OK? If your server administrator does not know how or, worse still, won't do this for you, then you have far deeper problems that go well beyond OS X in particular and IT as a whole in general. I have been fighting this since first installing windows 10 on one of my test systems.i FINALY have the solution. So i HAVE been using CORD to log into my PCs from OSX. But it was not working on the Win10 box. I was in the insiders Beta program. And after some update CORD finaly started working.