The suggestion to ensure the correct permissions are implemented to any network folders is valid it doesn't resolve the problem for Netlogon, which is set for student to have read access. The problem is that someone could potentially look at scripts that may be in the netlogon folder, and use any information gained to cause havoc on a network.
It just seems to be an oversight within Office '03 that should have a work around to lock it down completely?
Thanks for the response and suggestion though!