Allow me some credit lol, all passwords are in a signed envelope as well as spare rack keys etc. and will be in a safe. but thanks for your concern.
Mr advice is don't change a thing for the first 6 months. Learn the system and its benefits and flaws, then produce a plan for the future.
This will take time, especially if you are not even on Windows 7 yet!
My advice would be go back to your old boss and tell him you made a mistake and want your old job back..
Lots of love,
Your old boss
HaHa See you on Friday for football
I would second the advice not to change anything major (e.g. the Exchange to Office 365 move you mentioned). If email is okay (not perfect, but okay) then leave it alone until you now what out there doesn't work at all. Your first priority is finding out what your second priority is! Also, people get very attached to their email, so even the tiniest change can upset or confuse them (much like the Facebook news feed!) and right now, you need a clear channel of communication to people, so don't mess with that.
If you don't already have one, get a helpdesk set up so that people can easily report issues, you can see them all in one place and prioritise accordingly; linked to that, don't let people stop you in the corridor or phone you to report problems (unless all you do is write it down and add it to the helpdesk).
Get Spiceworks or similar in place, so you can find out what kit you have and what software is installed (noting that Spiceworks also picks up local installs, so is better than just checking Group Policy). Then, get a large pad of paper and walk round every classroom, noting down all the things which Spiceworks didn't/can't see, e.g. projectors, locally-attached printers, scanners, visualisers, etc.
Then, arrange a meeting with each head of department and ask them what their biggest concerns are, what they use (note, this may differ dramatically from what they have installed!) and what they would like to change.
And keep coming back to Edugeek - there are lots of people on here who have been in a similar position and can help you out.
Make sure your backups work if there is any, at least you will then have data if anything does wrong.
K!ll yourself now.
If somene asks "how long" for a job to be done always add in some fat (f***ing about time)
Definately go for a site licence, with Microsoft it's based on the number of staff (FTE) and not the number of computers, that way you can always have up-to-date software on your computers.
About 9 months ago, I inherited a network that seemed to have had a small thermo-nulear bomb explode in it's midst. I am now in the final stages of building a brand new network from scratch (everything will be killed, with the exception of the SIMS database, e-Mail databases and user data. the servers that they reside on though, are being rebuilt). I will be switching over during the easter holidays.
That in mind, I would say not to leave things until you know everything, when there is an obvious improvement that can be made to make life that little bit easier, whilst not being a dangerous move. One of the things that I did was to implement quotas on the file server (yes, there were no quotas at all for staff or students...).
Other than that, as has already been said, Documentation! The idea of running around with a notepad, cataloging everything may not seem very appealing or worthwhile, but will save you a lot of hastle later on. I say that as someone that has yet to do so!