It is actually a great protection.
Our network is doing okay because we have multiple layers
of protection. I've considered doing the same thing but
haven't yet.
If a tech inserts a line in the HKLM Run key that launches
a batch file. This could be put on every departmental PC.
Next, the tech could distribute a batch file to every PC.
Between the reliable reg/run and the batch file, there's
all sorts of forced options that can be enforced.
In class, changing just one Group Policy setting caused a
very noticable slow-down in boot-up times. (It's already
slow enough with SMS, auditing components, antivirus,
etc.) A tiny batch script runs so fast it usually never
shows on the screen. I killed Hotbar and Gator on one
belligerant user's PC this way until she gave up trying to
install them.
Whenever the tech wants to add or change anything, they
just edit the batch script and copy whatever else is
necessary. It would be better to keep the batch script and
any packages in a hidden folder.
Taking what Dave Patrick said and using a batch script to
import a reg file, the batch code might look like this:
regedit /s C:\WINNT\DEPT\KillIt.reg
KillIt.reg would have your entries that delete the keys or
values. REGEDIT /s is the silent mode. It'll happen so
fast, nothing will even flash on the screen.