#Microsoft remote desktop services 2012 how to
#Microsoft remote desktop services 2012 install
#Microsoft remote desktop services 2012 trial

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

Verify that the firewall allows remote desktop connections with RDP.

(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))ДЇor those of you still using the old RDP application, doing the following helps:Д®nable RDP security layer in Group Policy on the machine: 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:

On the Select deployment type screen, select Standard deployment and click Next.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).

On the Select installation type screen, select Remote Desktop Services installation and click Next.

In the Add Roles and Features Wizard, click Next on the Before You Begin screen.

Select Add Roles and Features from the Manage menu.

Additionally, the RD Connection Broker role canвЂ™t be installed on a domain controller.

#Microsoft remote desktop services 2012 install

YouвЂ™ll need an Active Directory domain and an account that has permission to install the server roles on your chosen server(s). For more info, see Managing Windows Server 2012 with Server Manager on the Petri IT Knowledgebase. Servers that you want to use in your RDS deployment need to be added to the Server Pool in Server Manager before you start the process below. RD Licensing is installed like any other server role, and you donвЂ™t need to use the special RDS deployment option in Server Manager.

#Microsoft remote desktop services 2012 trial

If you want to use your RDS deployment beyond the 120-day trial period, youвЂ™ll need to install the RD Licensing role, add your license, register the licensing server with Active Directory, and then add RD Licensing to your RDS environment.

The Windows Internal database is installed as part of the process to support the RD Connection Broker role, as are some IIS components for RD Web Access, which provides access to RemoteApps or desktops from the Start menu or a web portal.

The Quick Start deployment model is useful in testing scenarios or in small branch offices where only a single server is available. Standard deployment is the default deployment model, and while for the purposes of this demonstration IвЂ™ll install the three server roles on one server, thatвЂ™s not best practice. IвЂ™ll use the standard deployment model, which allows the RD server roles to be distributed or installed on a single server.

#Microsoft remote desktop services 2012 how to

In Remote Desktop Services Deployment Options in Windows Server 2012 R2 on Petri, I walked you through the available deployment options, but in this article IвЂ™d like to show you how to use Server Manager to deploy RDS. In todayвЂ™s Ask the Admin, IвЂ™ll show you how to install RDS in Windows Server 2012 R2.