[sclitheroe]

I'm going to say this as a 16 year veteran:

You need to know your stuff on specific technologies. But LEARN everything you can about computers, networks, etc. By this I mean how a microprocessor works. Understand what that hex error code relates to (hint: it's the numeric representation of a defined error in a header file a developer uses), learn about electrical signalling on ethernet and what some of the issues there can be. Learn about wifi and signal reflectivity. Know how Kerberos actually works, not just that its what Active Directory uses. Learn about buffer overruns and how they work, not just how to patch a system. Understand concepts like queueing theory and how it impacts latency.

Learn as much as you can about what makes the technology tick and how high level concepts like software and operating systems drive physical silicon is key.

To use a car analogy, some mechanics can change the tranny in a Ford F-150, and they've done 100's of them. But some guys know how a transmission works, and can relate that symptom to the underlying operating characteristics, or can work in a pinch on another model of vehicle. These are the guys, with the big picture outlook, that are valuable, whether they are generalists or highly specialized - they understand IT at innate technical levels.

If you don't have a passion for that level of learning about it, I don't think its a great career - you'll be forever a "paper MSCE" or your field's equivalent - capable of operating the stuff as it comes out of the box, but the details of what is really going on under the hood will forever be a mystery to you. You'll know a product, not a technology if you only approach it at that level. Our industry is full of people that know how to make Windows or a Cisco router do something, but only within the context of pushing buttons or typing in commands they are cutting and pasting from implementation guides. Don't be that person.

Take a writing course. Take two writing courses. Maybe take a course on intentional logic (yes, that means a philosophy course). Communication in this field is key - you have to be able to logically and coherently express complex topics to people with the entire swath of technology experience and insight. You've got to be able to take complex technologies and analyze them, synthesize solutions, identify and articulate business goals, etc. Even if you can write now, take another writing course. Other complementary skills like the Tech Infrastructure Management stuff you mentioned, ITIL Foundations, etc, are all highly important - maybe not specifically on the resume, but definitely in how you come across in terms of your vision for how to conduct IT. The technology evolves rapidly and you need those kinds of skills to put together roadmaps for infrastructure lifecycles (even if your first job doesn't entail that, and it won't, you need to be able to think in those terms to align yourself with it)

You said you're a sales guy - don't forget the people skills, or presume they become less important. My rule of thumb, if you're working at a client site for an IT company, is that its about a 70/30 split people to technical skills. Being able to build trust, communicate effectively, understand a client's innate fears and concerns, anticipate their needs, develop strategies, deliver analysis, etc, are all hugely important. Whoever decided to bring you along to do their IT monkey work needs to demonstrate they made the right choice, and the human relations side goes a tremendously long way towards that. The technical work is easy by comparison, since it either works or it doesn't (and hopefully you've got the chops to make it work)