Skip to main content

When you remove the Run command from the start menu in a GPO, does it also remove it from the task manager?

By

Years back during the NT4/Win95 days, you were able to remove the users ability to run programs using the Windows NT4 system policies. The problem was that there were multiple ways to execute a program that the system policies did not address. Flash forward to Windows Sever 2008. By setting the Group Policy setting of User Configuration\Administrative Templates\Start Menu and Taskbar\

Remove Run menu from Start Menu to Enable, you will do the following.

· The Run command is removed from the Start menu.

· The New Task (Run) comm.

· and is removed from Task Manager.

· The user will be blocked from entering the following into the Internet

· Explorer Address Bar:

o A UNC path: \\\

o Accessing local drives: e.g., C:

o Accessing local folders: e.g., \temp>

David discovered that you can still get to the CMD window with this procedure:

· [Window Key] E will open Windows Explorer.

· Browse to C:\Windows\System32

· Launch CMD.exe.

To help curve any “work arounds”, set the following group policy objects in the appropriet place for your organization:

· User Config \ Admin Templates\ System\ Prevent access to the command prompt

· User Config \ Admin Templates\ System\ Ctrl+Alt+Del Options! Remove Task Manager

That prevents CMD.EXE but Command.com worked. OK, now we must set a software restriction policy to prevent Command.com for executing, no matter where the user moves it. For that, we will use the Hash software restriction policy:

In your Group Policy:

· Copy COMMAND.COM to your server at c:\Windows\System32.

· Computer Configuration à Policies à Windows Settings

· Right click Software Restriction Policy and click New Software Restriction Policies.

· Right click Additional Rules à New Hash Rule.

· Click Browse to C:\Windows\System32\Command.com

· Click OK

· To allow administrators to still be able to use the software that you have restricted:

o IN the Software Restriction GPO.

o Double click Enforcement

o Select All users except local administrators.

Since we used a Hash rule, moving or even renaming the file will not allow it to run.

Labels:

Comments

Post a Comment

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Set up your Environment to utilize Invoke-GPUpdate

By
I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...
Post a Comment
Read more

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
Read more