Jump to content

Recommended Posts

Posted

Firstly here are all the numeric values for all drive letters:

 

A 1
B 2
C 4
D 8
E 16 
F 32
G 64
H 128
I 256
J 512
K 1024
L 2048
M 4096
N 8192
O 16384
P 32768
Q 65536
R 131072
S 262144
T 524288
U 1048576
V 2097152
W 4194304
X 8388608
Y 16777216
Z 33554432

 

And here's a caption from a System.adm file from Windows Server 2003 R2 I have customised. I recommend you make a copy and name it System1.adm leaving the existing System.adm file in place. By creating a Test OU, you can remove System.adm and import System1.adm without affecting your other OUs.

 

In this example the Numeric Value is 63 which would restrict drives A to F. You can do any combination according to your requirements. Hope this helps :)

 

POLICY !!NoDrives
		#if version >= 4
		SUPPORTED !!SUPPORTED_Win2k
		#endif

		EXPLAIN !!NoDrives_Help
		PART !!NoDrivesDropdown	DROPDOWNLIST NOSORT REQUIRED
			VALUENAME "NoDrives"
			ITEMLIST
				NAME !!ABOnly           VALUE NUMERIC	3
				NAME !!COnly            VALUE NUMERIC	4
				NAME !!DOnly            VALUE NUMERIC 	8
				NAME !!ABConly          VALUE NUMERIC 	7
				NAME !!ABCDOnly         VALUE NUMERIC	15
				NAME !!ALLDrives        VALUE NUMERIC	67108863 DEFAULT
				NAME !!Logistix		VALUE NUMERIC	63
				; low 26 bits on (1 bit per drive)
				NAME !!RestNoDrives     VALUE NUMERIC	0
			END ITEMLIST
		END PART
	END POLICY

	POLICY !!NoViewOnDrive
		#if version >= 4
		SUPPORTED !!SUPPORTED_Win2k
		#endif

		EXPLAIN !!NoViewOnDrive_Help
		PART !!NoDrivesDropdown	DROPDOWNLIST NOSORT REQUIRED
			VALUENAME "NoViewOnDrive"
			ITEMLIST
				NAME !!ABOnly           VALUE NUMERIC	3
				NAME !!COnly            VALUE NUMERIC	4
				NAME !!DOnly            VALUE NUMERIC 	8
				NAME !!ABConly          VALUE NUMERIC 	7
				NAME !!ABCDOnly         VALUE NUMERIC	15
				NAME !!ALLDrives        VALUE NUMERIC	67108863 DEFAULT
				NAME !!Logistix		VALUE NUMERIC	63
				; low 26 bits on (1 bit per drive)
				NAME !!RestNoDrives     VALUE NUMERIC	0
			END ITEMLIST
		END PART
	END POLICY

 

Anywhere under strings:

 

[strings]
Logistix="Restrict drives A to F only"

Posted

We've banned USB drives for many years and use our VLE or webmail to exchange files. Seems to work quite well.

 

I disabled autorun in GPO and made all the shared drives read only on the root, this stopped all the netsky virus type things propagating immediately. Not had a problem with them since.

Posted
Tech_guy's link looks very interesting, however in the past (as an alternative) I created a custom GPO which limits the number of drive letters available.

 

If all existing network drives are using drive letters, plugging in a USB stick will do nothing as no letter can be assigned.

 

Actually, thinking about it, the same can be achieved via the RMMC if you have CC3 or (presumably) CC4, where you can specify which drive letters are visible and/or accessible to a user.

Posted
Actually, thinking about it, the same can be achieved via the RMMC if you have CC3 or (presumably) CC4, where you can specify which drive letters are visible and/or accessible to a user.

 

Very possible, but with a little tweaking the same results can be achieved for free.

Posted
We disabled autorun on drives and then use Software Restriction Policy to blanket ban executable files from all locations other than where we whitelist. This has solved the problem for us. This also stops exe games and portable apps/TOR programs and so on.
Posted

We have usb devices disabled for students, enabled for staff & autorun disabled for all.

 

If students need to bring stuff in on a stick they bring it to us. We don't have many so this isn't a problem.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...