i agree. an internship is exactly what you make of it. i've had both IT and non-IT interns work for me and universally i'd rather hire the intern who works hard, asks questions, and realizes that some of the stuff they are doing is menial crap that we all had to do when we started out. you can do your internship just to say you did one (which honestly won't matter to most potential employers that much) or you can really try, ask questions, try to be involved, etc. a lot of the busy work they ask you to do does help, but mostly it's to keep you busy while they work on important stuff. if you show you can be trusted (even just to grab a screwdriver when needed) they'll start bringing you along for fixes, start showing you the ropes, etc. if you pay attention you'll likely be surprised that you can be an asset relatively quickly.
when you're standing in the server room looking over someone's shoulder, pay attention to what they're doing. it's easy to let your mind wander but you might just happen to notice the thing the guy in charge is missing. if you're smart, you'll notice it, let him/her know by asking something like "is that screen configured correctly? i've never done it before", and then reap the benefit of having helped without seeming like a know-it-all. in my experience it's a tight-rope walk at first to be accepted as knowledgable without coming across as someone "dangerous" to everyone else, but if you can be helpful, personable, and willing to spend several months doing gopher stuff you'll be fine. just my 2 cents, your mileage may vary, etc.