Academic IT departments are very different beasts. The bureaucracy to get things done can be much more complicated, the resources much scarcer, and the variety of tasks that people need to do/think they should have a right to do/assert that IT is born to do is vastly greater.
The more the IT people lock things down in an academic environment, the more rogue operations there are. If they go after the rogue operations, then the bureaucracy increases as the rogues fight to take the power away from centralized IT.
On the other side, if I want something done on an academic network, dealing with support in an IT department built to have work-study students explain to incompetent professors how to bring back a menu bar in Outlook (or Thunderbird, or whatever Macintoshes use, and, of course, professors will insist on the choice of which one) can be a nuisance. It'll waste a half-hour of my time (more in the phone queue), and a half-hour of thir time. On the other hand, if I screw up the MAC cloning on the rogue device I'm jacking in, or if I put it into an unauthorized drop, the competent person calls me, and we can sort the issue out. Nobody wastes any time. Of course, they'll also call me if I run an IRC client, and tell me that my PC is botted.
So, yeah, if they want a login on the box, good for them. They won't have the interest or money in administrating it. Naturally, they could be just collecting the data they need to bring a complaint.