Need to ask someone that works in IT a handful of questions for this module, would be greatly appreciated if someone on QGL could help me out so I don't have to hit up randoms :)

Very short, just need key points, nothing detailed... questions are:
-Organisation mission/goal
-Core business/activities
-Structure (teams/departments/divisions etc.), any sort of detail here so I can make a rough organisation chart would be greatly appreciated.

-Key IT positions
-3-4 IT policies/procedures (email, internet use etc.) + how they're communicated to the employees
-What OS/software/hardware used
-General locations of hardware (don't quite see the point of this question?)
-Relationships with vendors
-How systems are serviced maintained

Hit me up via PM if someone can spend ~5-10 mins blasting out some answers.

Thanks a tonne in advance, I can't stand modules like this.

Organisation mission/goal

Fluff

-Core business/activities

Fluff

-Structure (teams/departments/divisions etc.), any sort of detail here so I can make a rough organization chart would be greatly appreciated.

ITIL is a good start - but basically big arse chart with fancy titles on it and everyone levels of responsibility and their skill sets

-Key IT positions

I read this is as part of the above and who fixes what when it breaks

-3-4 IT policies/procedures (email, internet use etc.) + how they're communicated to the employees

Standard Documentation + Fluff

-What OS/software/hardware used + General locations of hardware (don't quite see the point of this question?

Do the following
First Site Audit - What have you got? whats running? whats it running on?
Whats broken and rank it from mission critical backwards
Tag each item with an asset number so you can set each item apart from one another
Normally I break it up to workstations / laptops / Peripherals / Servers
Then Find out what OS + Software / Firmware / IP is running on each item yes even the stupid modems and printers
Then find out what backups are running - are they working have they been tested
Draft a floor plan of the building layout with a rough idea where each asset is
Draft a diagram of the rack
Draft a diagram or the clients WAN and LAN topology
Take photos of the most important bits of kit - ie the server room (because explaining to the receptionist at 6am in the morning what a UPS looks like and where the power button is can be a nightmare if the server was shut off after a power cut
Find out who hosts their DNS / MX etc etc
Find out their ISP usernames / passwords
Find out if any third parties manage their equipment i.e Telstra business as an example and who to contact (get your firm listed as able to request adds / changes / removes)
If possible get their usernames and passwords but up to your security policy
Label everything
Document everything

GOLDEN RULE - Shit is no good in your head to other techs or you may forget it. So Document everything

-Relationships with vendors

Unless your the CFO / CIO then who cares

-How systems are serviced maintained

What ever suits really

last edited by HerbalLizard at 21:22:30 29/Sep/11

You would hate it at my work then