Link to home
Create AccountLog in
Avatar of mrmut
mrmutFlag for Croatia

asked on

Remote Desktop configuration on 2012 R2

Hello all,

   I am having some trouble getting up 2012 as a Terminal Server; we are configuring 2012 after upgrade from 2003 (as a new domain/server).

   What I would like to do is to create a classic Terminal Server, however it seems I am bumping around with changes.

   Could someone give me a link, or maybe a write up of a step-by-step installation and configuration of RDP server on 2012?



Thanks
Avatar of Zsolt Pribusz
Zsolt Pribusz

Terminal Services in 2012 is named Remote Desktop Services.
You need to install some Windows roles/features to your servers.
If you want only one server, then you need to do this:

Open Server Manager. Click on Manage. Select Add Roles and Features.
Select Role-based or Feature-based installation.
Search Remote Desktop Services, choose Remote Desktop Licensing and Remote Desktop Session Host role services.
Do the installation

After that, add your server to the Terminal Server License Servers group, activate the License Server, and add your CALs to the server.
Add terminal server users to the Remote Desktop Users group.
Configure RDSH role to use the licensing server.


If you need more than one Session Host server, then consider installing  the Remote Desktop Connection Broker role to another server to provide access to the complete functionality with Remote Desktop Services.

This link gives you a step by step guide:
http://support.microsoft.com/kb/2833839
Avatar of mrmut

ASKER

Thanks, and I did done more or less all of this, however - how do I configure RDSH? I'was looking for the tool and I can't find it.

RD Licencing Diagnoser is telling me that:

The licensing mode for the Remote Desktop Session Host server is not configured.
The Remote Desktop Session Host server is within its grace period, but the RD Session Host server has not been configured with any license server.


  - and the licencing manager is activated, licences installed and made available.
ASKER CERTIFIED SOLUTION
Avatar of Zsolt Pribusz
Zsolt Pribusz

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of mrmut

ASKER

Bless you, it worked.

Now, would you mind to tell me why did Microsoft fu*ked up TS management this badly? in 2003 it was a breeze.
I don't think, it is fu*ked up, just different. If you just moved to 2012 from 2003 then you will need to learn new methods.
MS is using PowerShell in administration more, and more. Earlier in MS softwares you can change every options from GUI, and some can be changed from PS. Now sometimes they only create basic interface for options in management utils, and everything else need to do from PS.
Avatar of mrmut

ASKER

Yes, I know they invested a lot in power shell, but I have never been very attracted. What benefits does power shell offers to me? Would you mind explaining what in power shell is so "powerful"?

As I see it, I would need to learn loads of commands for a proprietary peace of software that will be obsolesced fairly quickly. Than, why bother with Windows at all? This RDP issue is just a proof of their "care" with compatibility.
I think power of powershell in automation and configuration management can be seen on large environment. In maintaining few servers may seem superfluous.
Avatar of mrmut

ASKER

I think you are right regarding intended usage, however taking GUI tools from admins is cretinism. It is like they are forcing users to look at alternatives, and to be honest if not for Terminal Server, they would be history on most of my networks.