Solved

Exchange Server 2013 Implementation

Posted on 2014-01-07
9
356 Views
Last Modified: 2014-01-20
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.
0
Comment
Question by:kurajesh
  • 5
  • 4
9 Comments
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 39762920
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.
http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx

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.
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 39762941
0
 
LVL 1

Author Comment

by:kurajesh
ID: 39779842
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?
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 39780002
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.
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 1

Author Comment

by:kurajesh
ID: 39781445
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.
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 39781449
Hi Kurajesh. I didn't quite understand the last question.
0
 
LVL 1

Author Comment

by:kurajesh
ID: 39785486
i meant any other points to take care apart from the above points discussed for exchange 2013 implementation
0
 
LVL 31

Accepted Solution

by:
Gareth Gudger earned 500 total points
ID: 39786698
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.
https://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-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.
0
 
LVL 1

Author Closing Comment

by:kurajesh
ID: 39794941
Thanks a lot diggissaur. Very useful tips.
0

Featured Post

Are your corporate email signatures appalling?

Is it scary how unprofessional your email signatures look? Do users create their own terrible designs and give themselves stupid job titles? You can make this a lot easier for yourself by choosing an email signature management solution from Exclaimer today.

Join & Write a Comment

Suggested Solutions

Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

757 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now