Skip to main content

How to prevent USB memory devices from being used through Group Policy

By

USB devices have made transporting data extremely fast and easy.  The down side is that they also have the potential of spreading computer viruses just as fast and easy.  For this reason, you may want to restrict a computers ability to read data and execute programs from a USB drive.  Also potentially damaging is the ability for a user to remove large amounts of data for your networks.  You may also want to restrict the writing of data to these drives.  Group Policy provides you with options to help manage USB memory device usage.

 

This first option is for users of Vista.  You can scope this one to either a computer or to a user.  In your GPO, expand. Policies \  Administrative Templates \ System \ Removable Storage Access.  There you will find 4 GPO settings to help you deny read, write, and execution from USB devices.

image

 

For Windows 7 clients, you can also set a condition based on Windows BitLocker.  In your Group Policy, expand Computer Configuration \ Administrative Templates \ Windows Components \ Bitlocker Drive Encryption \ Removable Data Drives.  Two GPO settings will help you out here.  First, disable Control use of Bitlocker removable drives.  This will prevent users from BitLocker protecting their USB devices to get around the next setting we are going to enable. Second, enable Deny write access to removable drives not protected by BitLocker.  Also check Do not allow write access to devices configured in another organization.  This will not completely block the USB device, but it will only allow USB BitLocker devices created previously by the client to be used.

 

For Windows XP client, check this blog post from Daniel Petri on a possible method to help with XP clients.

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more

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

Where did a User’s Account Get Locked Out?

By
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...
18 comments
Read more