Hello, Currently my organization is using Exchange 2010 Server with the following design in one site. 1- One Edge server 2- Two server with roles CAS/HUB/MBX => For HA purpose. 3- AD: There are 5 AD sites. Current all exchange servers are in one site. Now I need to implement one Edge server and One server with roles CAS/HUB/MBX on another site. => For DR and HA purpose. My situation and questions as the following: People can advise me. I appreciate your advises. . Q1: Current subnet of Replicate Network is conflict with my WAN network (MPLS). Thus I need to change subnet of Replicate Network. Is there any impact to current system? I need to restart any services and impact to any Exchange Servers? Q2: There are any impacts to current Exchange servers during I am deploying Exchange Servers at remote site. If users can access Mail Server normal? Q3: Current client access array as the following. --------------------------------------------------------------------------------------------------------------- [PS] C:\Windows\system32>Get-ClientAccessArray Name Site Fqdn Members ---- ---- ---- ------- mail Saigon mail.companyname.com.vn {Ex-server1, Ex-server2} --------------------------------------------------------------------------------------------------------------- When I deploy Exchange servers at remote sites I need to run command as below. New-ClientAccessArray Name mail.companyname.com.vn Fqdn mail.companyname.com.vn Site Default-First-Site-Name So after I'd deployed Exchange Servers at another site, the result of Get-ClientAccessArray command will be look like the following, is it correct? --------------------------------------------------------------------------------------------------------------- [PS] C:\Windows\system32>Get-ClientAccessArray Name Site Fqdn Members ---- ---- ---- ------- mail Saigon mail.companyname.com.vn {Ex-server1, Ex-server2} mail Default-First-Site-Name mail.companyname.com.vn {Ex-server3} --------------------------------------------------------------------------------------------------------------- Q4: If possible please share me documents about deploying Exchange Servers at DR site (remote site). Thanks in advance. Peace.

Q1: Not sure if I fully understand the question, but if you need to change the IP subnet scheme of the DR site, this should not affect the current Exchange servers. If no Exchange servers are in the DR site, Exchange doesnt care too much about what happens there. This does not mean you wont have routing or other general network issues with users accessing their mailboxes from the DR site, but this is outside of the Exchange configuraitons. . Q2: Deploying Exchange servers in your DR site is deploying them within the same Exchange organization, so doing so will make changes visible within AD. This should not impact your primary site as far as mail flow or client access. As long as there is a logical separation (separate sites within AD), Exchange will not try to use any of the servers in the DR site unless you have active mailbox databases located there. . Q3: You are correct in that you would need a second CAS array configured for the DR site. You may run into issues with with having them use the same FQDN as you do not want DNS pointing to both arrays using the same name. The CAS array in each site should only service mailboxes located in databases actively held within that site, so clients will need a unique name to use for each CAS array depending on which site their mailbox is located. . Q4: Unfortunately I dont have any documentation specific to this. This may or may not be useful for you: Deploying Exchange 2010  

Hi Q4: Maybe this blog is useful. Terence Yu TechNet Community Support

Hi PS CL, Thank you very much for your reply. About Q2: Because there are about 200 clients in this remote site (DR site). Therefore I also plan for active Mailbox Database at there (Clients at DR site can access direct new Exchange Server). It is not only for DR purpose but also for Load balancing purpose. As I mention in previous thread, the configuration is it Ok? Any recommend for this? Thanks, Peace.

As far as having both sites with active users, there is no problem with this. You may want to configure your secondary site to be non-internet facing (do not configure external URLs on the CAS virtual directories) as this will allow all client access to initially terminate to your primary site. Your primary site will then proxy the connections to the "non-internet facing" CAS servers in your secondary site.