Solved

Remove the ability to reboot servers from helpdesk user's.

Posted on 2016-08-17
14
66 Views
Last Modified: 2016-09-07
What is your recommendations or the best way to remove the ability to reboot servers from helpdesk technicians, analysts etc?

Even if it is on a per server basis I would like to know your thoughts.
0
Comment
Question by:Dustin Poole
  • 4
  • 4
  • 3
  • +2
14 Comments
 
LVL 6

Expert Comment

by:Rob Leaver
ID: 41760254
I would deploy a GPO to remove and prevent access to the shutdown, restart, sleep, and hibernate commands
0
 
LVL 1

Author Comment

by:Dustin Poole
ID: 41760261
On a user basis or a computer basis?

And how do I allow power user's to reboot with such in place?
0
 
LVL 39

Accepted Solution

by:
Adam Brown earned 250 total points
ID: 41760264
Remove the Local administrators group from the User Rights Assignment settings "Shut Down the System" and "Force Shutdown from a Remote System". Then add just the users/groups you want to have that ability to the rights list. (This is in Group Policy: Computer Settings > Windows Settings > Security Settings > Local Policies > User Rights Assignment)

If you want to control this with a GPO, deploy a GPO that only includes the users that need those rights listed in the User Rights Assignment node in the GPO, link the GPO, then either set it to be enforced or move it to the top of the list on the OUs that have your servers in them.
0
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 
LVL 6

Expert Comment

by:Rob Leaver
ID: 41760269
You would do it through the per computer configuration, however when you add the GPO you would apply the security settings to a group so you could apply the permissions to a particular set of users, leaving your power users the capability to reboot ect as required
0
 
LVL 39

Expert Comment

by:Adam Brown
ID: 41760270
To allow power users to reboot their workstations, make sure your Computers and Servers are in different OUs and link the GPO I mentioned to the Servers OU.
0
 
LVL 8

Assisted Solution

by:Justin Moore
Justin Moore earned 250 total points
ID: 41760282
What I would do is create GPO for the for the helpdesk techs and under administrative templates remove the ability to shutdown or restart. See below.GPO.JPG
0
 
LVL 1

Author Comment

by:Dustin Poole
ID: 41760291
Jmac you're enabling the hightlighted option and applying to the helpdesk technicians OU?
0
 
LVL 39

Assisted Solution

by:Adam Brown
Adam Brown earned 250 total points
ID: 41760295
Just so you know, that particular policy doesn't prevent them from being able to shut down the computer. It just removes the GUI controls to do so. Users with only that policy set can still use the shutdown command in CMD to turn off or reboot the computer. To block that, you have to ensure that they are not a member of a group that has the user rights I mentioned earlier.
0
 
LVL 8

Expert Comment

by:Justin Moore
ID: 41760296
Yes you would enable that option.
0
 
LVL 8

Expert Comment

by:Justin Moore
ID: 41760297
Adam, your right but you can also remove the run command in that group as well. Or you can edit the security properties of the shutdown.exe and deny it for any user you want.
0
 
LVL 39

Assisted Solution

by:Adam Brown
Adam Brown earned 250 total points
ID: 41760361
Neither of which also removes the ability to perform a remote reboot on a server or workstation from a computer that doesn't have those options removed. All of those methods are cosmetic changes that don't actually remove the permission to shutdown systems. In essence, they are providing security through obscurity. The proper way to set the permission is to limit the User Rights assigned to the technicians. It takes more thought and consideration to configure systems that way, but it is significantly more secure because it completely removes the ability to shut down a computer without physical access.
0
 
LVL 8

Expert Comment

by:Justin Moore
ID: 41760392
Hey Adam, just so you know... I agree with you and had I saw your post before I posted, I wouldn't have posted my solution but geeze you don't have to be so snarky dude.
0
 
LVL 80

Expert Comment

by:David Johnson, CD, MVP
ID: 41760538
A helpdesk user doesn't need for a lot of tasks to logon to the server, they can do all of the management through RSAT tools.
0
 
LVL 1

Author Closing Comment

by:Dustin Poole
ID: 41788152
I was able to utilize Adam Brown's solution to resolve my problem.
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

The article will show you how you can maintain a simple logfile of all Startup and Shutdown events on Windows servers and desktops with PowerShell. The script can be easily adapted into doing more like gracefully silencing/updating your monitoring s…
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question