• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 316
  • Last Modified:

Migrating Exchange 2010 to 2013

Dear All,

  Im in process of migrating from Exchange 2010 server to  Exchange 2013 server. I have Installed two Exchange 2013 CAS/MBX in site 1 and  Exchange 2013 CAS/MBX  in site 2 and I will be configuring the DAG between them. I will be going live before I get my Kemp hardware load balancer.
I need to manage even with one CAS for 1 month until I get my HW load balancer. what is the best way to reduce the downtime while migrating my users from 2010 to 2013. can I have Exchange 2013 CAS and some users still in 2010, will they be able to access?


Thanks
0
ITMaster1979
Asked:
ITMaster1979
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
Have you read the co-existence documentation on TechNet?
This is a common scenario - I wouldn't touch the Exchange 2010 client access roles, other than the changes required for coexistence. Some of the CAS functionality goes through Exchange 2013, others would use Exchange 2010 servers.

Simon.
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now