Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have just finished an upgrade from Exchange 2003 to Exchange 2010. My final step is to cross-train those on my team who would be responsible for Exchange when I am absent. What are some (5 to 10 items) of the top items that anyone who touches Exchange 2010 should know?


locked by HopelessN00b Jan 21 '15 at 21:53

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

closed as off-topic by HopelessN00b Jan 21 '15 at 21:53

  • This question does not appear to be about server, networking, or related infrastructure administration within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

Not an Exchange guy, but +1 for having the foresight to train people to fill in for you. In addition to the training you should compile an operations runbook for your Exchange environment, that way if your fill-ins forget what you taught them they know where to look :-) – voretaq7 Feb 3 '11 at 5:27
This question is off-topic under current topicality rules. – HopelessN00b Jan 21 '15 at 21:53
up vote 2 down vote accepted
  1. Mail flow troubleshooting
  2. Maibox creation/management
  3. changes with 2003 vs 2010, for those hwo are already familiar with the pre-upgrade state of things
  4. Backups - config, how to test they worked and how often to test, how to restore form backups
  5. DR - what is implemented, and how it should be used
  6. Company wide policies - for example: if a user can't send an attachment, an admin will know what sizes are restricted and wil adise the user directly, instead of searching the configs to find out it's not an error the user just ran into

1) How to safely start up and shut down exchange services

2) What important files are to exchange (Hey the hard drive's full, I'm just gonna delete all those log files...)

3) How to deal with queries about stuff caught in your spam filters, even if that's not handled by exchange itself


Not the answer you're looking for? Browse other questions tagged or ask your own question.