Asked by:

New Server 2012 R2 RDS Deployent

Question

I need some help deploying a new Server 2012 R2 RDS server. It's a virtual server running on 2012 R2 Hyper-V. It is replacing an old 2003 Terminal server. All I am looking for is basic functionality, I do not need gateway services, remoteapps, etc.

What I have is about 5-10 users who need to log in to run some programs that are available on the LAN. Previously on 2003 they would login as themselves using an RDP client from Windows PCs and some Macs. Everything I am reading on 2012 just over-complicates
things and I would like to keep it a similar as they are used to now.

What is the best way to configure this? I would like them to each have their own desktop, and not have access to any server settings.

I know this is a pretty simple question, but I haven't really dealt with RDS since it was terminal services back in Server 2003, and a lot has changed.

All replies

Sanket. J Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thank you, but the replies don't really describe what I am looking for.

Basically at this point, what I am really l looking for is how to lockdown the login for users so that they cannot access Server Manager, PowerShell, etc. I would like to have their logins so that they cannot do any administrative things on the server.

Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.