• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1101
  • Last Modified:

Windows Server 2012 Standard Terminal Server Users Access to Task Manager

We just recently implemented a new Windows Server 2012 Server that we use as a Terminal Server.  So I have users logging in to their RDP Sessions and all is good.  But when one of their programs causes an issue in the RDP session they don't have access to the Task Manager to end the problem program.  Is this something a Group Policy would fix?  I would like them to be able to only end their own programs.

Thanks
Kevin
0
kevin1000
Asked:
kevin1000
  • 4
  • 3
1 Solution
 
VB ITSSpecialist ConsultantCommented:
Users should have access to the Task Manager by default unless you already have a policy in place which prevents them from being able to launch it. FYI users can use the Ctrl + Alt + End key combination to launch the Task Manager as this simulates the Ctrl + Alt + Delete key combination in a remote session.

As long as your users don't have Administrator rights on your 2012 RDS server then they won't be able to end anybody else's processes but their own.
0
 
kevin1000Author Commented:
I'm probably missing something but when I sit at a users workstation and start the Task Manager from the right-click on the taskbar I get the authentication screen where I have to put in my Admin username and password.  When a user put their login information in to that screen, they get "Login Failure.  User has not been granted the requested logon type at this computer."

Thoughts?
Kevin
Thanks
0
 
kevin1000Author Commented:
Update:   I just tested the CTRL + ALT + END and it brought up the Task Manager for the workstations local side.  I need to get the users access to the Terminal Session Task Manager so they can end misbehaving programs.

Thoughts?
Kevin
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 
VB ITSSpecialist ConsultantCommented:
Sorry Kevin, missed your first response. It definitely sounds like you have policies in place restricting users from launching the Task Manager.

I can tell you now that in a vanilla 2012 RDS install, the Task Manager can be launched by default by all users.
0
 
kevin1000Author Commented:
Thanks.

Any thoughts on what group policy would do that?  Cause it really was a standard installation.

Thanks
Kevin
0
 
VB ITSSpecialist ConsultantCommented:
It's most likely an existing policy in your environment. You'll need to check what computer-level policies are applying to the RDS servers in the Group Policy Management Console itself.

Try running a RSoP query while logged into the 2012 RDS server and check Computer ConfigurationWindows SettingsSecurity Settings

I'm not too sure which exact GP setting would cause this though, I'll need to do some research on my end. I have a feeling it's something within the User Rights Assignment area.
0
 
kevin1000Author Commented:
Sorry it took so long to accept the solution.
0

Featured Post

Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now