Exchange Server 2013 Implementation

we are currently using exchange 2003 server and going for exchange 2013 soon. Before the new implementation I need to know some prerequisite steps. The number of mail
boxes are 200.

1) Hardware recommendations with appropriate sizing (which must support the business at least for next 5 years)
2) Best Redundancy for exchange 2013 , virtualisation methods
3) Total Software licenses required
4) Domain Controller with ADC.
5) Exchange 2013 Backup and Restore solutions (best third party solution)

we already have sonicwall firewall in place and DMZ config requirements for the new servers need to be defined. which all servers need to be in DMZ.
kurajeshSenior Systems AnalystAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Gareth GudgerSolution ArchitectCommented:
You can't migrate directly from 2003 to 2013. You need to migrate to either 2007 or 2010 first (I recommend 2010).

1/. The sizing all depends on your user base. How many emails they send and receive a day, the average size of those email and the size of their mailboxes. Microsoft has a sizing calculator I would recommend. Otherwise I am just guessing for you.

2/. The best redundancy would be four servers. Two servers acting as a CASARRAY and two servers acting as a DAG for mailbox redundancy.

3/. Software licenses depends on what you are going to accomplish. There are Standard and Enterprise Exchange Server licenses. The only difference here is the number of database you need and for 200 users I would say Exchange Server Standard is the way to go. There are also Standard and Enterprise USER CALs dependent on the features you need. If you need archiving for example, or, unified messaging. Standard CALs most functions. You world need 200 USER CALs and an Exchange Server Licenses depending on how many servers you go with, and any base OS server licenses.

4/. Are you referring to the Active Directory Connector? Shouldn't need this.

5/. I use Symantec Backup Exec 2012. R2 will be releasing soon and that will include granular recovery again.
Gareth GudgerSolution ArchitectCommented:
kurajeshSenior Systems AnalystAuthor Commented:
thanks a lot diggisar, very useful tips. by the way we will go with 4 servers for exchange standard version with standard cals for 200 users.

considering the high availability options shall I opt VMware or hyperv is enough?
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

Gareth GudgerSolution ArchitectCommented:
I've done quite a few on VMware ESXi without any problems. It is recommended you assign a raw LUN for the Exchange DBs, but I have seen people successfully use a datastore VMDK as well for smaller environments.

I have not personally tried Hyper-V, but being another Microsoft product you would hope it would work as well as VMware. I hear Hyper-V 2012 is a huge improvement over 2008 as well.
kurajeshSenior Systems AnalystAuthor Commented:
thanks a lot. iam clear now with the above. I need to invite the partners for quotes for the above.  in case if you think that we need to consider apart from above kindly let me know.
Gareth GudgerSolution ArchitectCommented:
Hi Kurajesh. I didn't quite understand the last question.
kurajeshSenior Systems AnalystAuthor Commented:
i meant any other points to take care apart from the above points discussed for exchange 2013 implementation
Gareth GudgerSolution ArchitectCommented:
I think you have got it all. Obviously just to reinforce a previous point that you can't go directly from 2003 to 2013. You have to go to either 2007 or 2010 first. I would recommend using 2010 as your hop to 2013.

I use this article all the time to go from 2003 to 2010.

You will also need to look into creating/modifying DNS records and purchasing SSL certificates for the new Exchange server. The article above goes into all of that. Otherwise I would say you are ready to proceed.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
kurajeshSenior Systems AnalystAuthor Commented:
Thanks a lot diggissaur. Very useful tips.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.