Solved

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

Posted on 2016-08-17
14
61 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
NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

 
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 7

Assisted Solution

by:jmac44
jmac44 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 7

Expert Comment

by:jmac44
ID: 41760296
Yes you would enable that option.
0
 
LVL 7

Expert Comment

by:jmac44
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 7

Expert Comment

by:jmac44
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 79

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

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

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

What to do when Windows Update is not working correctly? What tools can I use to detect the cause of the malfunction problem? What does this numeric error code mean? These and other questions that you have been asking in the past are answered here (…
While rebooting windows server 2003 server , it's showing "active directory rebuilding indices please wait" at startup. It took a little while for this process to complete and once we logged on not all the services were started so another reboot is …
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

809 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