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

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.

Comments

Sticky Key problem between Windows Server 2012 and LogMeIn

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 .

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Backup and Restore AD LDS with DSDBUTIL.exe

Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services. The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database. Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet. Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS. You may want to make sure the database is being backed up and also have a restore plan in place. Should the database become corrupt, the application that uses that database will fail. This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...

Jason Yoder, MCT

Search This Blog