Network and Classroom Management Thread, Solution to stop people disconnecting network cables (Testers wanted please) in Technical; Note: This is in test currently, Not for live deployment!
Hey,
As from the amount of posts in the scripts ...
Solution to stop people disconnecting network cables (Testers wanted please)
Note: This is in test currently, Not for live deployment!
Hey,
As from the amount of posts in the scripts forum about getting help with disabling a computer once someone disconnects the network cable, I decided to go about writing a little free program designed to easily do this.
The main idea of the program being able to totally lock the student out of the computer while it's disconnected from the network. Thus stopping any issues with GPOs not applying, games not being blocked, etc etc.
Hopefully few people wouldn't mind testing it for any holes/bugs, I might have missed
How's it look:
The program "should" run unseeable during normal use, and like this during lock (aka disconnected network):
Locks the computer screen on a disconnection from network.
Relocks the screen if a teacher unlocks the program while it's still disconnected from network.
Checks the network connection on program load, so even if it's already disconnected it will lock.
Unlockable through simple password on lock screen.
Records time of lock.
Records attempted bypasses, and password entries. (In debug only currently)
Status:
Windows XP: FN-GM Tested (Didn't work, but think it's due to not having .NET framwork installed)
Windows Vista: Tested (But would like more tests if possible)
Windows 7: FN-GM Tested (But would like more tests if possible_
Wireless: Not Tested
Wired: Tested (But would like more tests if possible)
Known Issues:
If you have any secondary network connections, e.g. hamachi it still classifies this as a network connection, so won't lock. As "officially" you're not disconnected :P (Trying to fix this, but I assume most school computers don't use multiple connections anyway, at least not that I've worked with) (If you're not getting locked, good idea to check this, and disable 2nd connection while testing program)
Bypass attempts don't update during graphics update (but looking to sort this)
Very dark/hard to see colours. Due to it being totally random in choosing colours currently, it will sometimes pick stupid colours. This will be sorted shortly!
FAQ: Q: What can disable this? A: Obviously items like taskmanager, and/or WMI scripts "can" kill the program, but this shouldn't be available to students anyway.
Q: Red Buttons on program? A: Aren't shown in proper release, just there for debugging. Kill switch (Incase i/you break something major and can't get out :P) and Force Redraw just for testing.
Q: What's the password?!?!?!?!? A: test
Any and all testing on it would be appreciated, Would be nice to get a final live version up and sorted :P If you have ANY suggestions, feedback etc would all be greatly welcomed.
(Also I've only tested this on a computer with Visual Studios on, so would be nice to know if it requests any installs to work)
Many thanks,
Steve
Change log:
v2 - Added secondary admin login, and enabled auto-unlock
v1 - Original
Last edited by Steve21; 16th April 2011 at 05:23 PM.
On Windows XP the program wont run at all i get the attached.
Tested on Windows 7 32 bit seems ok.
The fact it locks itself very soon after you have put the password in is a little annoying because if there is another problem like the wireless disconnecting it cant be fixed. If that can be stopped?
Also would be good if the screen unlocked itself after the cable has been reconnected.
Also how do you recommend the program is run from?
One other comment i would say is improve the UI.
Thanks
Last edited by FN-GM; 16th April 2011 at 04:52 PM.
On Windows XP the program wont run at all i get the attached.
Tested on Windows 7 32 bit seems ok.
The fact it locks itself very soon after you have put the password in is a little annoying. If that can be stopped?
Thanks
Err, That was sort of supposed to be like that :P It relocks itself if a teacher unlocks it while network cable isn't plugged in. aka so they need to put cable in before it unlocks
On Windows XP the program wont run at all i get the attached.
Do you have the .NET framework installed on that pc? (That error usually means you don't)
Tested on Windows 7 32 bit seems ok.
Good to know, Thanks
The fact it locks itself very soon after you have put the password in is a little annoying because if there is another problem like the wireless disconnecting it cant be fined. If that can be stopped?
Certainly can do, Two options I guess, make it longer but then how long is the issue, or simply don't relock it. But then random teachers who just type password in without checking cable, will allow access to games etc :P
Also would be good if the screen unlocked after the cable has been reconnected.
Could put it in as an option, as a few said in the scripts forum they wanted it locked until someone opens it :P
Also how do you recommend the program is run from?
As in? :P I'm assuming easiest way is copying it over to the computers, and doing it as a startup. Bearing in mind if they disconnect network it wouldn't be able to pull it from the servers etc.
One other comment i would say is improve the UI.
Aye, Only set for debugging currently :P Guess it needs an adminy side UI. What else would you like on it? Just config settings or?
Out of curiosity, did you try on wireless or wired?
Thanks Steve
Last edited by Steve21; 16th April 2011 at 04:55 PM.
Certainly can do, Two options I guess, make it longer but then how long is the issue, or simply don't relock it. But then random teachers who just type password in without checking cable, will allow access to games etc :P
Personally i wouldn't give teachers the password. If it automatically unlocks the screen after the cable is connected again there is no need for them to have it.
I tried in a virtual machine.
Last edited by FN-GM; 16th April 2011 at 05:01 PM.
an admin password that disables the program
a teacher password that temporarily disables and re-locks if the network cable is still disconnected after say 5 mins
if you you have the auto unlock, if a student unplugs the cable during logon. Onces its done the screen will lock. If you have the auto unlock on they could then just connect back up and get access to the full machine. If you did a auto gpupdate once the cable is back in it should stop that.
Could of done with this when I was running an old CC2 network, some of the kids figured out that if the cable was pulled during logon it wouldn't pull down any scripts/GP Settings so they'd get a bit more freedom on the machines, I'm going to test this next week on VM.
Added a second password login, So if an admin logs in (currently test2) it'll unlock the computer, and disable the relock timer.
Also added auto-unlock on putting the cable back in. However as discussed above, this could cause issues with GPOs, so will need to look into this, or just don't allow auto unlock
New version should be up in a minute :P
Also FN-GM what bit of UI were you referring to? Know its pretty basic currently, but not sure what bit you actually mean :P Is it admin side? whole thing? or what
LinkBack URL
About LinkBacks
Originally Posted by FN-GM 
