Placement of exchange servers between AD sites

We are planning to upgrade exchange 2013 and expand our exchange Organization. We have 10 AD sites with below details.
HQ Site 5000 Mailboxes
Site1 6000 Mailboxes
Site2 4000 Mailboxes
Site3 800 Mailboxes
Site4 500 Mailboxes
Site5-10  100-400 Mailboxes.
Below are our related concerns:
1.Do we need to place exchange servers in sites?  if yes, what are the requirements and criteria to place exchange server on sites.
if not, what are the bandwidth requirement in order to connect to HQ site.

1.  No.  If your network can support the client traffic between the sites, you can place the servers in a central site.  The network is the only criterion.  It's usually cheaper to build up the network than to build out the servers.
You can calculate the requirements using this tool:
https://gallery.technet.microsoft.com/office/Exchange-Client-Network-8af1bf00
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Similar Messages

  • RPC error when configuring Exchange 2013 servers in 2nd site

    Hello. I'm running into an error when trying to configure any of my Exchange 2013 servers in my 2nd AD site. To get into the loop of what my server structure looks like, please check below:
    Site 1 servers:
    DC1 - Domain Controller
    DC2 - Domain Controller
    CAS1 - CAS server
    CAS2 - CAS server
    MBX1 - Mailbox server
    MBX2 - Mailbox server
    MATHAFTMG - TMG server
    Site 2 servers:
    CCCDC1 - Domain Controller
    CCCDC2 - Domain Controller
    CCCCAS1 - CAS server
    CCCCAS2 - CAS server
    CCCMBX1 - MBX server
    CCCMBX2 - MBX server
    CCCTMG - TMG server
    Currently I have a site-to-site vpn connection between site 1 and site 2 TMG servers via Internet connection; I can access the servers of the other site perfectly (whether I am in Site 1 or Site 2).
    All user mailboxes are currently in Site 1 MBX servers; when users are in Site 2, they connect to the CAS servers in Site 1 to access their mailboxes.
    Many users will stay permanently in Site 2, so it makes sense to have Exchange servers in Site 2 to provide faster access to mailboxes. I created the Site 2 domain controllers, and made sure AD replication is working; and it is. I then added the MBX servers
    and CAS servers in Site 2 in this order: CCCMBX1, then CCCCAS1, then CCCMBX2, then CCCCAS2.
    All Exchange servers in Site 2 installed beautifully. But then I tried to access the servers via ECP to proceed with the configuration. In ECP, I click on the server link, and all Exchange servers in both sites appear. If I try to configure the virtual directories
    of Site 1 CAS servers, no problem. But when I try to configure virtual directories of Site 2 CAS servers, I get this error message:
    The task wasn't able to connect to IIS on the server 'CCCCAS1.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
    The virtual directories issue is just an example. Same thing happens if I try to configure Outlook Anywhere for Site 2 CAS servers.
    Users connect to Site 1 CAS servers via mail.domain.com. I have the A record mail.domain.com pointing to the IP address of CAS1 server, and another A record mail.domain.com pointing to the IP address of CAS2 server. Not the best load balancing going on here,
    but it works great with Exchange 2013.
    From mail.domain.com I can access OWA and ECP internally and externally; no problems there. From ECP I can access and configure any Site 1 Exchange 2013 servers.
    The only problem is when I access ECP to configure the Site 2 Exchange 2013 servers, I get the same error message:
    The task wasn't able to connect to IIS on the server '<server name>.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
    Even if I try to access a Site 2 Exchange 2013 server via https://localhost/ecp to configure it, it get the same error message.
    I updated all Exchange 2013 servers in both sites to CU2 v2 and rebooted the servers in the proper order; problem still there.
    Any clue what might the problem be?
    Thank you!

    Hello. I'm running into an error when trying to configure any of my Exchange 2013 servers in my 2nd AD site. To get into the loop of what my server structure looks like, please check below:
    Site 1 servers:
    DC1 - Domain Controller
    DC2 - Domain Controller
    CAS1 - CAS server
    CAS2 - CAS server
    MBX1 - Mailbox server
    MBX2 - Mailbox server
    MATHAFTMG - TMG server
    Site 2 servers:
    CCCDC1 - Domain Controller
    CCCDC2 - Domain Controller
    CCCCAS1 - CAS server
    CCCCAS2 - CAS server
    CCCMBX1 - MBX server
    CCCMBX2 - MBX server
    CCCTMG - TMG server
    Currently I have a site-to-site vpn connection between site 1 and site 2 TMG servers via Internet connection; I can access the servers of the other site perfectly (whether I am in Site 1 or Site 2).
    All user mailboxes are currently in Site 1 MBX servers; when users are in Site 2, they connect to the CAS servers in Site 1 to access their mailboxes.
    Many users will stay permanently in Site 2, so it makes sense to have Exchange servers in Site 2 to provide faster access to mailboxes. I created the Site 2 domain controllers, and made sure AD replication is working; and it is. I then added the MBX servers
    and CAS servers in Site 2 in this order: CCCMBX1, then CCCCAS1, then CCCMBX2, then CCCCAS2.
    All Exchange servers in Site 2 installed beautifully. But then I tried to access the servers via ECP to proceed with the configuration. In ECP, I click on the server link, and all Exchange servers in both sites appear. If I try to configure the virtual directories
    of Site 1 CAS servers, no problem. But when I try to configure virtual directories of Site 2 CAS servers, I get this error message:
    The task wasn't able to connect to IIS on the server 'CCCCAS1.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
    The virtual directories issue is just an example. Same thing happens if I try to configure Outlook Anywhere for Site 2 CAS servers.
    Users connect to Site 1 CAS servers via mail.domain.com. I have the A record mail.domain.com pointing to the IP address of CAS1 server, and another A record mail.domain.com pointing to the IP address of CAS2 server. Not the best load balancing going on here,
    but it works great with Exchange 2013.
    From mail.domain.com I can access OWA and ECP internally and externally; no problems there. From ECP I can access and configure any Site 1 Exchange 2013 servers.
    The only problem is when I access ECP to configure the Site 2 Exchange 2013 servers, I get the same error message:
    The task wasn't able to connect to IIS on the server '<server name>.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
    Even if I try to access a Site 2 Exchange 2013 server via https://localhost/ecp to configure it, it get the same error message.
    I updated all Exchange 2013 servers in both sites to CU2 v2 and rebooted the servers in the proper order; problem still there.
    Any clue what might the problem be?
    Thank you!

  • Exchange High availability between two sites with two servers

    Hi Team,
    I have a requirement to deploy exchange server 2010 between two sites. but i have limited resources to full fill this. below the summary.
    2 servers in two sites
    different subnets will user for two sites
    Need to deploy DAG.
    please let me know the considerations for this deployment. 
    Thank you

    Hi - In this scenario, you would setup the following: Site 1: Exchange 2010 Multi-Role server File Share location to place File Share Witness for the DAG Site 2: Exchange 2010 Multi-Role server The above will give you 2 nodes in the primary location and
    one node in the secondary location so that resources will stay in Site one. You will also need to enable DAC (Datacenter Activation Coordination) on the DAG so that the Cluster group can be managed by Exchange. Last but not least, you will want to restrict
    automatic failover of resources to Site 2 by blocking that action on the Exchange server in Site 2 using 'Set-MailboxServer <servername> -DatabaseCopyAutoActivationPolicy Blocked' This will make you manually failover to site 2 and not end up with resources
    there after a sudden failure or issue that is not impacting the entire site.Jason Apt Microsoft Certified Master | Exchange 2010

  • Two sites, Two Exchange servers, same domain

    Exchange can seriously baffle me at the best of times. Which is why I'm writing here at the moment.
    I have 2 sites in two geographical locations for the same business connected via IPsec VPN. At each site we have:
    - Domain Controller (domain.local)
    - RDS Server
    - File server
    - Exchange server (domain.org.au) (SiteA - exch1, SiteB - exch2)
    All servers are Windows Server 2008R2, Exchange servers are 2010, Outlook is also 2010.
    Both exchange servers are set up with DAG replicating the primary mailbox database.
    Both RDS servers have outlook set up - users are currently connecting to exch1 for exchange connectivity (at both siteA and siteB)
    I want to configure the outlook clients so that SiteA uses exch1, and SiteB uses exch2.
    When testing, I manually set up an outlook profile and entered the server name as 'exch2', but upon clicking 'check name' it substituted 'exch2' for 'exch1'.
    I have had a look at implementing CAS array, but this will not work as we have DAG set up between exchange servers, and according to a microsoft article this cannot be done:
    ""WNLB can't be used on Exchange servers where mailbox DAGs are also being used because WNLB
    is incompatible with Windows failover clustering.""
    Is there something I need to change in either the Group Policy or Autodiscover instance, or even DNS to allow this to work? Is this even possible? Any help would be greatly appreciated.

    Forgive me - I still dont quite understand what's required..
    Because I have 2 physical sites with AD and Exchange, even though both sites are using the same domain and the same Exchange Mailbox Database, I still require 2 CAS arrays?
    Just to clarify, both DC's arent under separate sites within Active Directory Sites and Services - they are both members of the 'Default-First-Site-Name' site. Would this make any difference to the config I am aiming for?
    I can understand the concept of having 2 CAS arrays, one for physical site A and physical site B, so that their respective RDS servers outlook clients point to their own local exchange server - but if both exchange servers are replicating and using the one
    Mailbox Database, I'm not sure if that will cause any issues - Cant you only apply one CAS array per database?
    Also, if I am unable to use network load balancing because the software balancing service wont work with the cluster service, what IP(s) would I point the CAS array to - my guess is the local IP's of the exchange servers for its relevant site?

  • How to to make Cluster between two server 2012 Datacenter with share storage and Hyper-V role then install Exchange 2013 on each server datacenter then make DAG between Exchange servers

    Dears,
    I have IBM Flex server with built in storage,  
    HOW to to make Cluster between two  server 2012 Datacenter with share storage and Hyper-V role then install Exchange 2013 on each server datacenter then make DAG between Exchange servers?
    If there any prerequisites of the Share storage types ?and any configuration guide to deploy Cluster between two Server 2012 datacenter ?

    Microsoft Failover Clusters require shared storage.  If you wish to create a failover cluster with local storage, you need to use third party software to mirror the disks and present it to the hosts (siog.com, datacore.com, starwind.com).  If you
    use third party software, you will need to follow their instructions for configuring the environment.
    Questions on how to configure Exchange environments are better asked in an Exchange forum.
    .:|:.:|:. tim

  • 2 Exchange 2013 Servers in 2 sites

    Hi. I have 2 Exchange Servers total, one in main site and the other one in a branch ofice. Both of them belongs to the same forest, and also both of them have MBX
    and CAS roles installed. The goals is to have them in a Database Copy configuration so both of them have the same DBs in case of an issue with any of them (if this is the proper design configuration).
    After 2nd server installation I'm not able to connect to it through PowerShell (even though I'm logged on locally in it) as it redirects the connection to the 1st server. Within ECP (of the primary one) I can't see the 2nd server in the Servers tab, nor
    the default DB it hosts.
    I'm very confused about what the design must be in order to have them replicated with the same functionality. Would you please advice?
    Thanks!
    Infrastructure Management Sr. Analyst | MCSA Windows Server 2012

    As for the design, I would probably add another node in the primary site so you have some local HA.  What happened after you forced replication?  Did it show up in the EAC?  What happens if you go into the shell in the main site and run get-exchangeserver?
    Can you also make sure that the Exchange Trusted Subsystem security group is a  local administrator on both Exchange Servers?  Also, make sure you have a global catalog in each site .
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

  • Is it possible to have different service pack between Exchange servers.

    Is it possible to have CAS Exchange 2007 running service Pack 1 and Mailbox server 2007 running SP2? In my env I need to have SP1 running on CAS server for some applications but also need to install SP2 for migration. Application cannot be upgraded so
    I am thinking to keep one CAS running SP1 and upgrade other Exchange 2007 servers to SP2. Please suggest.

    Hi,
    It is recommended to have the same service pack level on all Exchange 2007 servers, different service pack level may have potential effects.
    Here is a related thread for your reference.
    Exchange servers with different Service pack levels
    http://social.technet.microsoft.com/Forums/en-US/88e22daf-7ccb-49c3-97d8-f339336476da/exchange-servers-with-different-service-pack-levels?forum=exchangesvrdeploylegacy
    Hope this helps.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Exchange servers in DMZ zone

    is it's right practice whether all exchange 2010 role servers in Dmz zone??
    or need to place only cas server in DMZ ZOne??

    Hello,
    It is required to place at least one writable Domain Controller with Global Catalog in every Ad site where Exchange servers are going to be deployed.
    Hope it helps,
    Adam
    www.codetwo.com
    If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others
    find the answer faster.

  • Internet Connection loss after losing connection between 2 sites

    Hello,
    I have started working for a company over a year ago and recently we are running into an issue with losing internet after a loss of connection between companies site.  Below is a summary of setup.
    Company has 2 locations, Site A and Site B..both same domain
    Site A has DC and other servers such as ERP, Document Control Software.
    Site B has DC, Printer Server, File Server and other essentials servers.
    Each site has own independed 20 MB connection.
    Site A and B are linked via MPLS and only used for ERP, Document Control software, and DC traffic.
    Recently we started to have frequent connection issues with the MPLS and as a result I started to notice none of the users at Site B can access the internet such as google.com, msn.com...etc. As soon as MPLS connection is restored interent works.
    The DC at Site B was setup before I started working for company.
    I have been trying for the past few days to figure out why Site B is losing connection when MPLS Tunnel is not operational...but so far no luck.
    I am very sure that internet traffic is not routed via MPLS because when internet is working the IP lookup such as "whatismyipaddress.com" points to ISP IP address for site B. Also when doing tracert to external website the route is via ISP for
    Site B.
    I think this issue is related to DNS but cannot tell the cause or how to fix? 
    Thanks for assistance in advance.

    Hi 
    Having said internet is not routing via MPLS, Even i think to be a DNS issues,
    Try to check the below
    Ensure all the client DNS is set to AD DNS server 
    In AD DNS server ensure its not forwarding DNS query to Other site 
    During outage check any client PC manually changing the DNS IP to 4.2.2.2
    - all client DNS are set to AD DNS server
    - I checked the properties for the AD DNS and found there are 3 forwarders listed.
    The first IP is at Site A which is resolved.
    The second IP I am not sure about since it is not even in our subnet (not resolved)
    The 3rd IP seemed to be for an old DC that is no longer operational (not resolved).
    - During outage if I change client machine DNS to 8.8.8.8 or 4.2.2.2 they can access the internet.
    I guess my issue is with the forwarders. Would the right step be remove all 3 forwarded and add 8.8.8.8 and 4.2.2.2?
    Thanks.

  • Reroute some vrf traffic between 2 sites over redundant link

    hey guys,
    We have a single client (in vrf) with 2 sites in different states and running over our mpls core.. Our primary link in our core is experiencing degredation of service and want to route this client over our redundant link while keeping all other clients going over our primary link - is this possible?
    The client in question has its own vrf (L3VPN) at both sites and is running over mpls between both sites. We want to re-route this particular client to take our backup path, while keeping everyone else between both sites going over the primary. We are not using TE, instead LDP to build MPLS.
    I don't believe this is possible to only re-route one client, however I thought I would ask the question.
    We cannot failover to secondary link for everyone between both sites because the link doesn't have the capacity.
    Thanks in advance.

    Hi,
    Using MPLS TE would certainly be an option. You would need to setup an MPLS TE LSP over the backup. You would also need to configure a separate lookback interface on each PE and use this loopback interface address as the next hop for the specific VRF
    ip vrf X
    bgp next-hop loopback 999
    ip route 255.255.255.255 Tu1
    This way you would make sure that only the traffic for this specific VRF would travel over the TE tunnel.
    Regards

  • Error when moving files between Sharepoint sites using 'content and structure' feature

    Hi,
    I am using Sharepoint Online 2013 on a mac computer.
    I am trying to move files between sharepoint sites/libraries but because the "open with explorer" link does not work on mac computers, I need to do so using the 'content and structure' feature.
    When I select a file to move and then select the destination site/doc library, i get the following error:
    An error was encountered performing this operation.
    Operation to Move '120207_Australia Post_Invoice.pdf' to '/Ops/internal/admin/General Admin' failed
    No items were moved. Please remove 120207_Australia Post_Invoice.pdf from the selection and retry operation
    Please help!
    Thanks,
    Kate

    Hi Kate,
    If you mean only one file "120207_Australia Post_Invoice.pdf" could not be moved, please compare this file to the other files moved successfully, check if there are some differences, like the content types, fields.
    Also compare the source library and destination library, make sure they have the the same type of fields.
    And you could have a try of moving this single file separately see if it could help, or as a workaround to download this file from source and upload to the destination library.
    Since it is related to SharePoint Online 2013, we cannot see the ULS log for more information, I would suggest you post this issue in Office365 SharePoint online dedicated forum via the following link for a better assistance.
    http://community.office365.com/en-us/forums/default.aspx
    Thanks
    Daniel Yang
    TechNet Community Support

  • SAP CRM with multiple MS Exchange Servers

    Hi all,
    I would like to use a SAP CRM 7.0 system with multiple MS Exchange servers. It is possible to forward emails from these Exchange servers to the SAP WAS via SMTP, so that SAP ERMS functionalities can be used to process the emails?
    Thank you,
    Till

    The answer is yes.  You need to just setup the exchange servers to route the e-mail to the inbound SMTP port setup on the CRM WAS server.  You will then configure the inbound e-mail address on the WAS to map to the ERMS service.
    CRM does not care how the message got sent to it, it just needs to be dropped off at that location.
    Take care,
    Stephen

  • Simultaneous sync with two exchange servers - will it ever be possible?

    I fully understand that this is not possible at present (one has only to try to get a very clear pop-up message). I also understand that nobody can predict (or is willing to say) what is coming in future releases. My question is whether or not simultaneous syncing with two exchange servers is even theoretically possible. I don't undertstand exchange/ActiveSync well enough to even know if it's in the realm of possibility.
    If not, I'll try to find another way to do what I want (Gmail for calendar and contacts and work for mail, calendar and contacts) - I am open to suggestions. If it is, I'll have to figure out how important one (or the other) is to me for now and wait for the day when I can have my cake and eat it too.
    Thanks.

    I'm not sure if this is an ActiveSync limitation, but it might be since I don't believe accessing more than one Exchange account via ActiveSync with a Windows Mobile device is supported either, and ActiveSync and Windows Mobile are Microsoft products.

  • Differences between Publishing sites and publishing enabled document library

    Hi
    what is the main differences between Publishing sites and publishing enabled document library 
    and how to enable publishing for document library?
    adil

    Publishing Sites is an out-of-the-box site template designed to publish web pages and it comes with a pre-built workflow or without (depends on which template you pick). It comes with libraries such as Pages library, Publishing Images, or Site Images.
    It is configured to fully customized the master pages (or add new ones), and page layouts.
    There is no such thing as publishing enabled document library. A document library is not designed to publish web pages. You can have Site Pages library in a team site, but if you are looking to fully brand a site collection, then this is not your answer.
    You will need to use a Publishing Site to fully brand your Internet or Intranet site.
    You can enable the publishing infrastructure on any site that is NOT a publishing site, but this does not turn your provisioned site to a publishing site. It simply turns on publishing features, such as navigation management, master pages/page layouts management,
    publishing workflows, etc....

  • Receivables question: AR invoices/credit memos between Supplier Sites

    I'm trying to solution a client requirement of having the ability to transfer AR invoices/credit memos between supplier sites of the same supplier. Is this possible or is there a comparable workaround available in Receivables R12?
    Thanks,
    Chris

    Chris,
    are you sure ... AR Invoices/Credit Memos to Suppliers ???  Looks like a typo error some where ... However, we might not be able to transfer transactions from one site to another (be it supplier or customer), what we can do is merge ....in which case all transactions that are appearing against a particular site would be pushed to the new site ......this could be taken as a workaround ...
    Merge functionality comes with very less flexbility, you cannot choose the transactions that you wanted to merge ....
    Regards,
    Ivruksha

Maybe you are looking for