AB Tutor Control Forum/Message Board

Azhibberd · Joined: 09 Jan 2007 Posts: 2

Ok... Here is what i am refering to as a 'bug', Basicly are school runs abtutor accross the network... for easyness they havn't set up connection passwords to each machine, So this means any user (who has a brain) can download the trial version... install it to a usb stick... take it to school run the .exe of a usb stick... and control all the network... maybe an idea that the teacher side has to have admin rights or something along those lines... if there is something already... would be good to know what... apart from setting them all to have a connection password... Or maybe they must have an admit account unless they have something within there registry... i don't know just thinking here....

Thanks
Azhibberd

meastaugh1 · Joined: 15 Apr 2006 Posts: 59

Why the aversion to connection passwords? Since you can set client connection passwords remotely from the Tutor, is it really a problem to do this? The end users wouldn't need to know/remember the connection passwords.

[quote]So this means any user (who has a brain) can download the trial version... install it to a usb stick... take it to school run the .exe of a usb stick... and control all the network[/quote]

Equally, anyone can download and run tutor and change all your client connection passwords, locking you out.

ChrisH · Joined: 09 Jan 2007 Posts: 10

You could make a hash rule to stop students runnng the control program through software restriction policies if you have a 2003 system.

Azhibberd · Joined: 09 Jan 2007 Posts: 2

Looks like the connection password is the way to go, which is what we have now done, although its kinda more of a pain as if the student manages to find out the password and well as you said it can all be done at the same time, that sounds easier than you put it as... with a network of around 300-400 computers you kinda have to have them all on at the same time etc, including latops etc.... So will be a few that get threw the net i guess. And also ye i like the idea of using a restriction policy.

Cheers
Azhibberd

meastaugh1 · Joined: 15 Apr 2006 Posts: 59

I agree, I don't like setting these things retrospectively for the reason you describe. That's why I include the connection password in the installation (transform).

Software restriction policies require Windows XP clients and can be used with Windows 2000 Server or Windows Server 2003. This would secure your domain computers, however it wouldn't prevent a user from connecting a laptop and running ABTC, unless you have sufficiently secured your network to prevent this. Imho, software restrictions are a sensible addition to connection passwords, not a replacement.