Too much ACO/IST experience to handle!
This is just some complaining -- I think I can handle it:

I need to whittle down my list of experience from my computing jobs on campus. The thing is, I don't want to compromise my customer-service type experience (like all the detail I go into with the moving people over to roaming profiles) because it's my real skill.

Geeks with vast UNIX and other backend knowledge don't got NOTHIN' on my awesome ppl skilz at putting admin assistants at ease updating their websites (or explaining to 60-year-old profs the difference between attachments and email bodies).

But, since I have so little of that technical knowledge, I have to list it all.

WHICH LEAVES ME WITH THIS REALLY, REALLY LONG LIST.

At the student-run faculty-level helpdesk, as part of a three or four person team of co-op students (backed up by a staff of 8 permanent staff administrators):

Offered user-end support of Active Directory domain for students, staff, and faculty
- dealt with Windows XP on an AD domain with mapped network drives, network printers, roaming profiles

Maintenance of the department's website
- kept information up-to-date concerning student lab facilities

Authored and presented software courses for staff and students
- Introduction to Excel, and OpenOffice.org for Microsoft Office users

Updated staff and faculty to our roaming profile domain and new machines from local configurations (specializing in the customer service aspect)
- loading new machines with an image including Windows XP and most of our default settings
- customizing machines for their personal needs (e.g. with particular software packages)
- explaining how their workstations would change (and how this would improve their work environment)
- taking special note of their personalized workstations (screen resolution, desktop, bookmarks, and physical placement of the machine) and making sure the transition was seamless and their work environment intact
- leaving direct contact information in case any problems arose

General software support
- Help using, or problem solving with, Microsoft Office and other software (e.g. "How can I print my courses slides many to a page?", "I want to write a resume in Word", etc)
- Troubleshot campus applications (webmail and course environment)

Created websites using pre-existing Dreamweaver templates and CSS to create departmental homepages
- educate users on how to update content using Adobe Contribute
- troubleshoot bugs that crop up with such programs by working with raw HTML

Documented personal progress and procedures and tips for future helpdesk employees using an internal Wiki


At the campus-wide helpdesk, as part of a team of 4-5 permanent staff and two co-op students:

Prepared and presented CANHEIT talk "How Students Communicate" with fellow co-op students
- Talk consisted of introductions to Facebook, MySpace, instant messaging, text messaging, and blogging
- I prepared and presented the blogging portion and assisted with preparing the instant and text messaging portions
- Talk was originally presented for University technical support staff December 2006, and repeated by two of us at the CANHEIT conference May 2007 at Wilfred Laurier University

Worked as front-line hardware and performance support at "urgent clinic" type helpdesk
- diagnosed problems as either software or hardware
- performed common fixes to poor performance (e.g. virus scrubbing)
- performed emergency data backups
- if necessary, reinstalled Windows XP and drivers
- troubleshot campus applications (webmail and course environment) and campus wireless network

Composed answers to frequently asked questions for the student-aimed Wiki

Brainstormed marketing solutions to raise student awareness of our services




(this is just a draft of skilz, so, although not resented, style or spelling suggestions will probably (hopefully) be caught in the next step of actually putting this in my resume)