Another thing I just thought of is a health monitoring suite for your servers/network. Also starting to move towards virtualized servers makes dealing with both failed hardware and testing/rollout/rollback easier.

They are very set in their ways when it comes to their severs, they wont even implement Active Domain services... So virtualization may be out of the question for now.

Are the servers on any sort of UPS to enable graceful shutdown if power goes out?

Yes, the company I work for is an electrical contracting company, and specifically the branch that I'm working for is based inside a massive data center. So power wise, everything is golden.

Definitely set up revision control ASAP.

Any recommendations on the best, I have minor experience with SVN, and I've only used GIT for github related stuff. Everything here is windows based, everything. So I was even considering going with TFS, but I also have been thinking about using git out of its simplicity and robustness. Especially since I may be working from multiple computers.

Well the term 'best' is touchy, but for your use case I'd suggest trying SVN using something like VisualSVN Server and TortoiseSVN for the client(s). Simple to set up, understand and use.