I started out in IT after graduating with a Bachelor's of Business Administration in Information Systems. Sneaker-net / phone support / ripping apart computers / etc. I worked my way up to server admin (earning MCSE in the process) with a dabbling in network admin (earning CCNA in the process). Programming wasn't anywhere near a major part of my work other than shell scripting.
But I saw the writing on the wall: the systems were becoming more and more stable; it was easier and easier to defend against computer attacks; it took less IT people to support more and more users/servers. IT also is an expense -- and expenses are to be minimized in the business world.
Hence I went back to school, got a BS and then a MS in Information and Computer Science so I could become a revenue source -- and finally fix the bugs that I had been finding. The problem was, though, that my decade-long IT experience meant nothing in the programming industry, other than leadership experience because I had become a supervisor and then a manager while working in IT.
So I started out as a junior programmer; after 3 years of learning a heck of a lot that they DO NOT teach in school, I finally had enough programming experience to land a job as a lead contract engineer. After 7 months of that, I'm now a senior developer at my current position.
IT experience is almost completely different than CS experience; only at a small company will there be overlap. At medium to large companies, specialization is the key and often the IT folks and CS folks don't trust each other.
So be careful. If you do end up taking an IT job -- hey, you have to eat -- make sure to get some programming in on the side. Join an open source community and start contributing code -- it's valuable experience that will get you portfolio material for when you apply for a CS position.