Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.
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.
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.
Who is Participating?
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.
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.
Cool article on CALs for 2013 as well.
http://office.microsoft.com/en-us/exchange/microsoft-exchange-server-licensing-licensing-overview-FX103746915.aspx
http://office.microsoft.com/en-us/exchange/microsoft-exchange-server-licensing-licensing-overview-FX103746915.aspx
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?
considering the high availability options shall I opt VMware or hyperv is enough?
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.
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.
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.
i meant any other points to take care apart from the above points discussed for exchange 2013 implementation
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
-
Course of the Month11 days, 11 hours left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
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.