Tom Achtenberg wrote:
> On all the networks I've been part of ranging in size from 20 to 250 machines, no one has been allowed to connect a machine that was not company issue without the IT directors approval.  This has included remotely connection through VAN or Citric.  All remote machines have been required to have firewall and current anti virus software.  None of our users have been geek enough to even know what Linux is let alone have enough technical know how to use it.  We do run about 6 or 7 Linux servers but no Linux workstations.


Well, ASU has about 50,000 people come to main campus every day and 
probably about 30,000 computers (this is a guess, I really don't know 
but we have at least 2 Class B networks).  Sheer size of course 
eliminates the possibility of a single individual controlling every 
computer on campus.  Of course a heirarchy of beuracracy can take this role.

HOWEVER (here is the important point), ASU has little to do with the 
selection and purchase and administration of many of these machines for 
one very simple reason.  This reason being, unlike a corporate network, 
the money to PAY for many of the machines does not come from the 
organization that owns the network.  Research computers are paid for by 
grants that come from the federal government who pays professors to do 
research.  So, typical politics aside, each professor has his own little 
fiefdom due to the fact that he has established some independance by 
drawing outside investment.

So, ASU IT, ETS, and DATACOM are pretty much in a tough position.  They 
don't do a bad job, ,but sometimes projects a little misguided.  So, I 
guess you would have to imagine running a network where you have little 
to say about what people do on it.  Obviously, they can shut down 
anything that is really causing trouble.

Austin