Microsoft remote desktop connection client for mac osx

#Microsoft remote desktop connection client for mac osx full#
#Microsoft remote desktop connection client for mac osx windows 10#
#Microsoft remote desktop connection client for mac osx Pc#
#Microsoft remote desktop connection client for mac osx windows#

Some articles will walk through this configuration and recommend removing the Server Authentication policy however, the certificates will then not work on non-Windows clients. This was key for OS X clients - both of these policies must exist.

#Microsoft remote desktop connection client for mac osx windows#

To configure a certificate for use with Remote Desktop Services (or RDP into any Windows PC), youвЂ™ll need to create a new certificate template and enable both the Server Authentication and the Remote Desktop Authentication application policies.

Using certificates in Remote Desktop Services.

Enterprise PKI with Windows Server 2012 R2 Active Directory Certificate Services (Part 2 of 2).

Enterprise PKI with Windows Server 2012 R2 Active Directory Certificate Services (Part 1 of 2).

I wonвЂ™t cover installing and configuring an enterprise certificate authority here however, here are a number of articles worth reading on this topic: The new Remote Desktop Universal app on Windows 10:ДЄnd the Remote Desktop client on OS X 10.11: First up the original Remote Desktop Connection (mstsc) on Windows: Here are the client certificate warnings on various Microsoft Remote Desktop clients, including OS X. Client Warnings for Untrusted Certificates While I may only be configuring certificates in my lab environment, thereвЂ™s not much effort required to remove these certificate warnings. To get OS X clients to accept the certificate takes a little extra configuration not required on Windows clients. An environment with an enterprise certificate authority can enable certificate autoenrollment to enable trusted certificates on the RDP listener, thus removing the prompt.

#Microsoft remote desktop connection client for mac osx Pc#

When connecting to a Windows PC, unless certificates have been configured, the remote PC presents a self-signed certificate, which results in a warning prompt from the Remote Desktop client.

But this is macos limitation.Windows has supported TLS for server authentication with RDP going back to Windows Server 2003 SP1.

#Microsoft remote desktop connection client for mac osx full#

Also annoying is that control left/right arrow to move cursor is not possible as macos intercepts it for switching between full screen apps. No stars off from this, but it would be nice if modifier key remapping was possible, as control/option/start button/alt are in annoying places. Probably also due to the scaling is image being blurry in some cases. Sometimes DPI is messed up and Windows target shows massive fonts, but if I exit and re-enter full screen it will resolve. I suspect this is the issue with the slowness, that both sides cannot agree consistently on DPI and resolution settings so there is a lot of scaling going on on both sides. Setting up resolution too a lot of manipulating with choosing 'optimize for retina' vs. All 3 are using 4k resolution (at 4k though even Windows RDP client has some noticeable lag but nothing compared to macos RDP client).

#Microsoft remote desktop connection client for mac osx windows 10#

Using Windows 10 RDP client to same Windows 10 target on same network is dramatically faster. Connecting to a local Windows 10 machine over 1 gbps Ethernet has very noticeable lag and low framerate. MacOS version works but has horrible peformance compared to the Windows version. Also, while I appreciate the option that allows the Apple key to be interchangable with ctrl for edit operations and find, it doesn't seem to work consistently, and as everyone who has ever switched back and forth between the Mac and Windows knows, confusion over which meta key to use in editing will eventually cause brain damage and is likely to send hardware on ballistic journeys through windows (not Windows). So properly-speaking, this probably a complaint about the service and not the client app, but the entire eco-system is failing me in small ways. Now, I'm sure there really IS such a way, but the internet is not my friend in helping me find it. Since there are some operations that cannot be performed via RDP - attaching to a VPN being one of them - it would be nice if I could just leave the PC logged in and operate it via Remote Desktop at the same time. This works reasonable well except that the Remote Desktop Service on the PC requires that I can only be logged in either via the Remote Desktop app OR the PC itself. I don't want to keep changing physical keyboards, so despite the fact that the two physical machines are next to eachother beneath my desk, I use remote desktop to view and operate the PC while working on the Mac.

I have a specific usage case - I work in a multiplatform environment in which I work on the Mac and on the PC.