
Many good and many funny comments.
My advice is to have an execution attitude. In other words, get things done. Your boss will love you if he knows that he can give you something and know that it will get done.
I am a fan of the practice of alluding to other well know literature. I think it is a great way to communicate complex ideas efficiently and capture big thoughts and ideas easily. Who doesn't know what 30 pieces of silver signifies? I love the statement "we are standing on the shoulders of giants". Such devices make progress in literature much more possible.
Those are well known samples. It is good to give credit but not always necessary. Otherwise credit should be given. If it is not it is plagiarism.
What you are looking for is controls that keeps your sysadmin from doing anything bad to your company, data, network, etc. One control is to have them onsite. But how many employees have caused the harm you describe while onsite? You need to look at different types of controls than proximity. What does your contract with the outsourcer say? Are their employees subject to your company policies? Do you have company policies? Has the sys admin read them and signed something saying that he agrees to abide by them? Have you run a background check on your sysadmin? These are all things you should have thought of a long time ago.
There is also an Intalio Foundation that contributes user accounts to nonprofits.
http://itredux.com/2009/05/21/intalio-foundation/
Try Intalio|CRM. (http://www.intalio.com/products/crm/) It is a full featured CRM. It is free for up to two users. It has Outlook sync capabilities.
The real question is what do you want to do? You might not have a good idea yet. Thus you ask thousands of slashdot readers you have never met.
I got a Mech. Engineering degree but got my first job as a staff consultant at Price Waterhouse, before it was PWC. That is a good way to go if you are not sure what you want to do. Consultants, especially entry level ones, end up doing whatever the client needs them to do. I wrote requirements, test plans, reports, did testing, maintained code, programmed, presented to clients. Just about everything. It was a great experience.
You may also want to try to become a business analyst. If you can understand the business guys and translate their needs to programming specifications. You may also want to look at business process management tools. Check out www.intalio.com. With understanding of BPMS you can take business requirements and weave them into high level executable processes.
Is your job running? You'd better go catch it!