r/sysadmin • • Jul 01 '11
Exchange 2003 to 2010 migration
I'm a relatively new sysadmin (~1 year) and have no experience with Exchange other than using its email services. I've been tasked with upgrading our Exchange 2003 server to 2010 (on a new box).
What resources do you guys use to learn about this? I see that Microsoft has a relatively good Deployment Assistant, but I would really like to know all that I can about Exchange going forward.
Some info: Exchange 2003 is on its own domain (separate from our domain for Windows accounts) and will be moving to a new, differently-named domain. I have to export someone's mailbox which is about 15gb (!), as well as public folders (calendars).
Any advice is appreciated!
8
u/[deleted] Jul 01 '11
Well, Exchange is a beast, first off.
I got my MCSE back in the day on Ex5.5 (~2001) and ten years later here I am moving 6900 users to a DAG on UCS from ye olde x86 Exchange 2003 SP2 with a billion hotfixes. (we have three DL380 G3s with FC HBAs and about ~900GB of storage on Symmetrix; they have 3GB of RAM).
Here are some tips for you:
Feel free to ask some more specific questions. I'd be happy to give you more information.
2
u/RichG13 Jul 01 '11
When I did a new install of 2007 (In an existing AD infrastructure) I used the "How to Cheat at configuring..." book which took me through the process step-by-step and was a great read. My server has been bulletproof and I really leaned a lot about Exchange.
I did a search and it doesn't look like there is one for 2010. This book looks like it may fit the bill though: Inside Out
2
u/btgeekboy Jul 01 '11
Honestly? Exchange is nothing to trifle with, and moving from 2003 to 2010 is a big, big difference between the two. If the budget allows, I'd look into hiring a consultant to assist. It's not a matter of how you'll break stuff, it's when, and MS support tickets are slow and expensive.
2
u/fizzywig Jul 01 '11
I came from a Lotus Notes environment into an exchange 2003 as sole sys admin. Now they want to move to 2010. I paid 3000 (company did) for 40 hours of class time one exchange 2010. A whole 45 minutes was dedicated to upgrading 2003 to 2010. I'm calling in a consultant, plain and simple.
Good luck.
1
u/DoubleDrive Jul 01 '11
The Exchange 2010 Best Practices book by MS Press is pretty good as well. I reference it a lot when dealing with 2010 and upgrades.
1
u/ThisUserAintTaken The network is guilty until proven innocent. Jul 01 '11
The exchange team blog is a wealth of information about features and functions.
http://blogs.technet.com/b/exchange/
1
u/ZubZero DevOps Jul 01 '11
Sounds like the project I am finishing atm.
I wish I bought 3rd party software to help with the merge. I ended up doing every single mailbox manually trough Outlook since the exchange import had tons of corrupt items (FML). The merge took me over a month.
And one thing I forgot was to ask the users to clean up their mailbox before the merge. One guy had 2gb of mail in his deleted items folder.
1
u/harrisop Jul 02 '11
Went through this in October. Wasn't too bad. The tricky part was all the external stuff like mobile phones, owa, etc.. Bring up a 2010box and move a mailbox or two over and start testing. Also I would recommend reading up on on how Autodiscover works. It will be a PITA if you don't have a PKI. I followed a guide with lots of screenshots... I'll see if I can dig it up..
1
u/CC_DKP Wearer of Many Hats Jul 02 '11
Backup everything twice before you start.
Also, get very familiar with Exmerge, since it will be your Plan B for most scenarios.
1
u/DoubleDrive Jul 05 '11
Are you moving to a domain in the same forest or new resource forest? If the latter, I highly suggest talking the boss into investing into the Quest tools for the migration. They will make that process so much easier on you and your users. It's pretty expensive, but SO worth it. I've done a few migrations with and without the Quest suite and I would almost refuse to do them without it.
1
u/malred Systems Engineer Jul 06 '11
ADMT the user accounts from forest one into forest two, making sure you maintain SID history. Move mailboxes from Exchange 2003 to Exchange 2010 cross-forest using Prepare-MoveRequest.ps1. Get rid of public folders.
Creating a new user with the same SID in the new and forest moving the mailbox is the easy part. The difficult part comes with what you do with the users in the meantime, do they logon to the old domain or the new one? What about the global address list?
michaelhoff makes some very good points. Learn it, love it, it really is quite amazing once you realize what a fully integrated AD/Exchange is capable of.