Restrict AIM

[Flying Meat]

dlloyd is correct, ultimately.

Though bobw's firewall suggestions will handle many of the alternate products since they must communicate with the AIM server on a specific port (not sure about the web alternatives). But external proxie servers would allow connections through alternate ports...

The best way to handle it is to make the computer usage policy clear (regularly even) and play no favorites. Two warnings, one office administrative action, and finally, termination.

Not allowed on office premises! Can be fired for this!
(or the equivalent student punishment = banishment from the labs)

Make the policy clear and well known.

[truss64130]

Sadly, to have any sort of diciplinary actions at my office is rather impossible. Asside from murder, it is hard to actually fire someone due to those above me not able to make a stand on any issue. I'll give some of the other options a try and I'm fairly sure they will be effective. The student workers are much less knowledgeable about macs than me, (which obviously I'm no expert). I'll let you know how I make out.

[truss64130]

I finally got around to trying flying buttress. It works great except one thing. When the computer restarts, the Startup script does not load, therefore making the firewall useless. If I go into the startupitems folder and try to run the script through the Managed account, it says I need to have root priveleges to run it. Any way of running a script as the admin account when the managed account starts up?

[bobw]

Try putting a StatupItems folder in the User Account/Library and add there and see if that works.