7 ms·
Everybody I know who works at a university has a personal rule which is, never let the IT department touch an important computer. The workers are "required" to
by analog31 6y ago
Everybody I know who works at a university has a personal rule which is, never let the IT department touch an important computer.
The workers are "required" to buy their own computers anyway, so it's not like the university has any say over how the computers are managed.
Everybody has a story about IT ruining their computer by installing some sort of unworkable security software. There's also a familiar story of IT coming in and wiping out a computer that runs some ancient scientific instrument that isn't supported by its vendor any more. And the vendor kindly sending them an unofficial copy of the ancient software because, well, because it's happened before.
To be fair, dealing with IT at a university must be a nightmare. My workplace takes the approach of providing all work computers, of a specific brand, and retiring the old ones before they turn into a support headache.
- Turing_Machine 6y ago> There's also a familiar story of IT coming in and wiping out a computer that runs some ancient scientific instrument that isn't supported by its vendor any more. Always mount a scratch monkey. http://www.jargon.net/jargonfile/s/scratchmonkey.html http://www.jargon.net/jargonfile/s/scratchmonkey.html
- m463 6y ago> dealing with IT at a university must be a nightmare. I know someone who does this. The answer to this immovable mountain of a problem is an unstoppable force -- throw students at the problem.
- ta988 6y agoIt is a nightmare yes. I used to run machines on a network isolated from IT's network. Before then they would come and ask to inspect every machine their IP or ARP scanner found. The problem is that they send a student that know nothing but extract info from machines... try to explain them what VM on bridged networks are etc. They have destroyed more data and computers (one we gave to them, windows takes 10 minutes to boot, and they told us it is fine just let it running, no kidding) than any student ever had. In term of users machines, rotating them is fine. However for instrument computers thats not doable, many labs still run win 3.11, xp and so on... Of course you could reverse engineer the custom acquisition cards and their dos driver, but you would also have to deal with the custom oracle database and the parallel port dongle and the weird timing hacks that make the software only run on machines with a specific graphic card...
- g_p 6y agoI've seen a whole high performance shadow network running behind NAT before, in order to get around the issue you describe. It worked fairly well as the NAT router was presenting a WAN MAC address from a device that had already been "approved". Main reason was to get local 10Gbe available when the official LAN was still 100 Mbit (!!), and to enable new devices to be connected to the network without going through whatever official process was in place. I'd never risk letting official IT people image a system - I've had to send people with laptops that were missing graphics drivers to "shadow IT support" to get their system properly installed by someone that knows how to clean install a system and install the necessary drivers.
- ta988 6y agoYes I got the routers approved as firewalls nobody bothered to check them again. This allowed me to have VLANs, avoid my VMs users to attack other machines on the university network (from any plug on a wall you could talk to any machine from the building no filters so all machines were spitting tons of packets for windows and apple sharing and spotify and attacks and so on). This also yes allowed me to add new machines any time I wanted to. I had proxies and I had a couple of public facing IPs with fixed lease and opened ports. All of that while also having to do my research work... Just because I wouldnt be able to do that work if I needed to wait weeks just for getting an answer that would turn in meetings with 5 people and chains of dozens of emails going up and down the ranks...
- g_p 6y agoYes, ironically the networks is more secure when people do what you did, as you reduce the number of devices exposed to the "broadcast/multicast storm babble", and avoid contributing to it further. There's an awful lot of Spotify and Dropbox mDNS and local device discovery traffic that people never see until they run a network! Our "shadow IT" ended up so significant that we ended up able to directly request firewall changes and just send in the rule lines (in the correct format for the edge firewalls used) and they would be applied for us within the hour...
- g_p 6y agoI can go one step further, based on what I've seen - "Shadow IT" that has its own help-desk line and ticketing system... Running their own LAN with interconnects to "main IT". The end result is that nobody ever lets "main IT" near anything. Most people who have important work on the go used shadow IT. People who know what they're doing then run their own personal Shadow IT (but would use the real shadow IT if they had any issues like needing to reinstall a system, as that way it won't get connected to the main IT domain...) You are absolutely correct - it's an absolute nightmare. Many university networks originate from the era of the flat LAN, where every system got a routable public IP, reachable via the internet. There are people running all kinds of servers and services and jobs across the network. None of them are documented, some might be relied upon by important internal or external things... There's no standardisation of hardware generally. If you're lucky there's some managed desktops using standard configurations for computer labs used by students, and office administrative staff. Don't expect to be able to tell professors what they'll use - they're buying computers on their research grants for themselves and their teams. And their own NAS servers and everything. Heck the "shadow IT with a help-desk" was even offering storage and VMs on their shadow infrastructure. I've seen people trying to use Windows XP on the network because some incredibly expensive piece of equipment needs it, and they would like to be able to browse the internet while they wait on it to do its work (!) Fortunately, shadow IT were on the lookout for that, and helped them set up a second computer on a supported OS, and get the XP box offline.
- 20after4 6y agoShadow it sounds too good to be true. It hardly seems deserving of such a very derogatory title like "IT".