Xref: utzoo comp.sys.mac.misc:13233 comp.sys.mac.comm:4282
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!vacs.uwp.edu!datta
From: datta@vacs.uwp.edu (David Datta)
Newsgroups: comp.sys.mac.misc,comp.sys.mac.comm
Subject: Re: Tips for Macs on a student network
Message-ID: <13187@uwm.edu>
Date: 17 Jun 91 19:05:21 GMT
References: <1991Jun17.165139.575@groucho>
Sender: news@uwm.edu
Reply-To: datta@vacs.uwp.edu (David Datta)
Followup-To: comp.sys.mac.misc
Organization: University of Wisconsin - Parkside
Lines: 49

In article <1991Jun17.165139.575@groucho> martyz@idui1.csrv.uidaho.edu (Marty Zimmerman) writes:
>Any tips for setting up Macs (LCs in this case) on a network in a student lab?

Have fun, I installed a lab full of MAC SE30s last year, here is the
results:

  You cannot make the mac boot from the network or use system files
  from the network. I have bitched and moaned to our apple reps and
  they finally told me, "you can't do it, period." (after much hemming
  and hawing.)

  Be ready to re-install about 2-3 machines a week unless you hide and
  rename the system folder. If the lab is in a public access area,
  things will be erased on a regular basis.

  Lock all of the files in the system folder that you don't want messed
  up, (I.E. EVERYTHING) put gatekeeper and gatekeeper aid on all of
  them and lock out the disable buttons.

  Modify the control panel so that none of the settings will work.
  (Leave the buttons for the values you want things to be active so you
  can re-set them if someone boots from their own floppy.)

  Don't install neat things such as kolor. You will find that wise-ass
  students like to change EVERYTHING to the same color so you can't see
  anything.

  Many packages that advertise "networkable" aren't, ask for a preview
  copy before buying 10 licences for your favorite package.

  If you keep software on the hard disks, be prepared to have it erased
  by students who are trying to install their favorite game that "won't
  fit" because of the stuff you installed. Keep a master backup of the
  hard disks, it is usually easier to configure everything the same and
  if someone messes something up, to erase the hard drive and start
  over. We keep an image of the hard drives on the server (in a folder
  that users cannot access) and boot the machine with a clean system
  disk when things get messed up.

  Be VERY aware about software incompatibilities, in the last few
  months, we have had students installing Sound Master and other things
  that eat up the RAM and make other programs not work. (Also it is
  recommended to turn off RAM cache from the control panel, some
  packages don't work with it.)

--
-Dave datta@vacs.uwp.edu. 

So, are there any words that rhyme with orange?