Remote desktop connection for mac windows server 2012 r2 windows 7#

Also allows Windows 7 & 8 desktops to connect using the RemoteApp and Desktop Connection.

Remote Desktop Web Access : This role provides a web portal to access the RDS environment.

Also allows disconnected users to reconnect to their existing sessions without starting a new one.

Remote Desktop Connection Broker : This role handles user sessions by load balancing among the RD Session Host servers.

Remote Desktop Session Host : Applications are installed and published from the Session Host servers.

There are three core roles to setup a RDS environment and are as follows:

Setup RD Gateway Role on Windows Server 2012 R2.

Setup RD Licensing Role on Windows Server 2012 R2.

Setup Remote Desktop Services in Windows Server 2012 R2.

In this post I will document the implementation of RDS in my home lab using an ‘all-in-one’ configuration. Microsoft RDS is the new expanded and renamed Microsoft Terminal Services. Until I fix this issue, I'll be using the old client.Microsoft Remote Desktop Services allows users to access centralized applications and workstations in the data center remotely. More annoyingly it does not store the connections I create and shows a 'new features popup' every time I open the app though it is not new anymore.

Remote desktop connection for mac windows server 2012 r2 update#

I was using the new RDP client and it was working well until a recent update happened and it lost all my connections. I don't know if this is an unsecured way of doing it but for my home network I did not mind changing the settings.

Close Group Policy Editor and reboot the machine for changes to take effect.

Change Require user authentication for remote connections by using Network Level Authentication to Disabled.

Select Security Change Require use of specific security layer for remote desktop (RDP) connection' to Enabled and select RDP in the Options pane.

The Group Policy Editor will open In the left hand side bar, expand Computer Configuration>Administrative Templates>Windows Components>Remote Desktop Services>Remote Dekstop Session Host.

Click Start>Run Type gpedid.msc and click 'OK'.

Verify that the firewall allows remote desktop connections with RDP.

I use CoRD which supports OS X 10.5-10.8), as there may be unexpected behavior from using Microsoft's old software.įor those of you still using the old RDP application, doing the following helps:Įnable RDP security layer in Group Policy on the machine: I would suggest using a newer client (e.g.

Remote desktop connection for mac windows server 2012 r2 mac os x#

As it says, 'Microsoft Remote Desktop Connection Client for Mac (version 2.1.1) is not intended for use with Mac OS X v10.7 (Lion) or later.'Īlso note that that page does not list Windows Server 2012 at all under the 'System Requirements.'

Remote desktop connection for mac windows server 2012 r2 download#

(If you wish to make the old client work you can follow the steps to get Mac RDP client 2.1.1 (110309) working or try the 2.1.2 unreleased build of the old client (please someone edit this answer))Īccording to Microsoft's Download Center page, the Remote Desktop Connection client for Mac was last updated on, over 2 years ago. Why this information isn't listed on the What's New in 2012 R2 Remote Services page I don't know. The good news is that the new OS X Microsoft Remote Desktop 1 (Mac App store only though - grr) does work with Windows 2012 R2. Who knew and why did it make me report all those crashes?)

(Brief aside - Microsoft have a little note that says the 2.1.1 client is not supported on OS X v10.7 or later. Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.Ī (regular) Windows 2012 Remote Desktop client doesn't have this problem. For me it fails with the following error message: Watch out - the old OS X Microsoft Remote Desktop (version 2.1.1) that comes with Mac Microsoft Office 2011 no longer works with Windows 2012 R2 (it does work with plain old Windows 2012).