EXCHANGE Coexistence with two server

Think this situation of disaster recovery, that i am recreating in my lab.
EXCH2013 installed on a server, member of AD, CAS+MB.
That server goes down, and can't work anymore.
I reinstall, on other server in the same AD, CAS+MB. I have copy of db, for example in local pst or other kind, no matter now.
When i access to ECP new  server i will be able to manage users, i will find the users mailboxes activated in other server (and not working) but i will have the chance to "recover" situation creating new users or assigning user's mailboxes
on new server.
Is this right?
Why OWA, ECP, on new server DON'T permit to log (old server DOWN)? I can see the page, put the credential but then error 500...how think that IIS service want to find the MB on server down, it can't find and goes error.
Any suggest?

I would do /RecoverServer first which will recover the server. And if I have the EDB file then I will mount that data. Or if I have Backup, I will restore the Backup.
Note: Make sure all the exchange services are running after /RecoverServer is successful
Does it works with new Mailbox?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Similar Messages

  • How can i split Client Network traffic and My exchange traffic with two differnet ip address?

    Hello Everyone
    sorry for my bad English and also my bad explaine
    here is my network looks like
    all the client on one subnet and network is 192.168.0.0
    i have Dsl router that connect to Tmg server
    i have Tmg with two NIC
    1-192.168.0.4
    2- 2 Public Ip address
    i want to do this
    i want to split user's traffic and my exchange traffic
    i mean i want to route user's traffic with one public ip addresss
    and my exchange server's traffic with another public address
    but when i add additional ip address at Tmg or create new NIC card
    all of my traffic route with one public ip Address what should i do?

    Hi Uhan,
    You need to use ENAT fuction on TMG to achive this
    On the External NIC assing the Second IP as Additionl IP address (VIP)
    Create a network Rule to NAT traffice From Exchange server IP address to the required Public IP which you need the E NAT.
    Ensure you are creating rule only from Exchange server IP and not all INternal.
    Look at the below Doc you step by step config
    http://www.isaserver.org/articles-tutorials/configuration-general/Configuring-One-to-One-NAT-TMG-2010.html

  • Exchange rates with two parallel currencies

    Hi all,
    I need to manage a company with two parallel currencies (USD and PKR). To post a document in USD it's necessary to define in TCURR an exchange rate FROM USD to PKR, and to post a document in PKR it's necessary to have an entry FROM PKR to USD.
    Obviously the second exchange rate has to be the multiplicative inverse of the first one.
    For this reason, to avoid redundant and possibly wrong entries, is it possible to manage only one exchange rate in TCURR (for example FROM USD to PKR) instead of two? How?
    Thanks for your attention

    Go to SAP Netweaver> General Settings> Currencies and manipulate the following and you should be able to maintain only one set of exchange rates.
    i) go to Check Exchange Rate Type - and manipulate the exchange rate type you are using (Check Financial Accounting Basic settings>  Ledgers> Define Currencies for Leading Ledger to check the exchange rate type used for each company code - generally M is used) and assign Reference Currency "Ref.crcy" (for example we use USD) for that exchange rate type.
    ii) go to Define Stnadrd Quotation for Exchange Rates and maintain - Forexample we use "Blank" to "USD", so that we just have to maintain Other currencies to USD (ref.crcy) and in In-direct Quotation.
    These setting would give you the ability to maintain just "Other Currencies" to "USD" in in-direct quotaion. Use this example to decide which currency you want to use as reference currency and then maintain accordingly.
    Hope this helps.

  • Lync 2013 FE pool with two server limitions

    Hi,
    I have some query about Lync 2013 FE pool with two FE servers.
    1. if I deploy two servers in the one FE pool so what happen if one fe server down ?
    2. will windows fabric work?
    Thanks.

    I don't completely agree with this. I have built a few environments with only 2 servers in the Front End pool (despite recommending that three be deployed) 
    1. Anyway in the event that one FE fails, users are temporarily disconnected and then the client will re-sign them in to the second server.
    2. Two servers is supported, but not recommended. See this link (it also contains how to handle two servers - scroll to bottom) http://technet.microsoft.com/en-ca/library/gg412996.aspx.
    The biggest issue with only having two servers is losing quorum. If both servers are shutdown at the same time, you can run into issues starting them back up. (it is recoverable by resetting the fabric/quorum, but it's a pain)
    If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer" | Blog
    www.lynced.com.au | Twitter
    @imlynced

  • Replacing Exchange 2007 with another server with new server name

    I am working with a client to move Exchange from the server it is on now to another server. This will be new hardware and new name. The current server Exchange is on will still exist by I want to move Exchange completely off of that server. 
    Current Network Setup:
    Server 1: 1 SBS 2003 server is Domain Controller, Runs AD, DNS, DHCP, File Sharing, SharePoint 2003 and Remote Desktop
    Server 2: Server 2008 running Exchange 2007, Backup Domain Controller, File Sharing, SharePoint 2007, Terminal Services. 
    Current Plan:
    Introduce Server 3 to run just Exchange 2007. I would like to completely over a short period of time move exchange from Server 2 to Server 3. I have searched over the internet and found several articles but still have a few questions. There are roughly 75
    mailboxes with 50 actual users. Some users are using Outlook 2003 that came with the SBS 2003 and others are using Later versions of office. Server 3 will be a Server 2008 R2 system.
    1. What is the best method to perform this transfer. I found article TechNet
    Article that explains with 2 remote offices how to do this but not sure if the same will apply.
    2. Since I am not immediately decommissioning Server 2 how can I safely remove all the roles and add them to Server 3?
    3. For the end user impact. Will the change make Outlook automatically pickup the new server name or will each user need to reconfigure their outlook profiles?
    4. I will be moving OWA since there are several Remote and Terminal Service users that use OWA for email. I would like to keep the same certificate and domain name setup if possible. 

    Hi,
    According to your description, I recommend you install another exchange 2007 on server 3, the exchange server role as the same as server 2.
    And then, transfer all mailboxes and configurations(OWA,DNS..) from server 2 to server 3.
    Finally, decommission the server 2 .
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Exchange 2003 with Windows Server 2012 DC's only. Migrate to Exchange 2010.

    I have the following situation:
    An Exchange 2003 SP2 server in an 2003 FFL and DFL domain with 2 Windows Server 2012 DC's. There are no Windows Server 2003 DC's anymore. Exchange 2003 is still functioning properly, but the eventlog is showing me some errors about LDAP which is unable to
    find an old 2003 DC.
    I know this is not supported, so we want to migrate to Exchange 2010 as soon as possible.
    What is the best way to do this? Will coexsitence still work? Do I have to add an 2003 DC's again?
    Please advice. Thank's in advance!

    Oh thank GOD I found this thread!
    I am facing a similar situation:
    http://social.technet.microsoft.com/Forums/exchange/en-US/9a8bc14b-1a45-4b8b-ac3a-38d63e66a7da/exchange-predeployment-analyzer-exchange-2010-compatibility-check-does-not-recognize-windows?forum=exchangesvrdeploylegacy
    And this is the first post I have seen marked as an answer by a Microsoft Contingent Staff affiliated person.
    Thanks Steve and Simon, you have saved me a bunch of grey hairs.
    C.
    "Time is an illusion, Lunchtime, doubly so..." - Ford Prefect

  • Help with OSX server mail setup

    Please if anyone can tell me what I am doing wrong, I would be very grateful.  I have a company with an externaly hosted website and an an internally hosted email (OSX server).  I have everything kind of working, but some things don't seem quite right.  I'll explain below:
    I have a purchased domain: mycompany.com hosted by godaddy.
    I am using Godaddy name servers: ns65.domaincontrol.com and ns66.domaincontrol.com
    The external godaddy DNS has an a name entry for my mail server: mail pointing to 123.123.123.123 (which is my companies external static IP address).
    There is also a null (@) a name record for my website hosting service (squarespace) pointing to 456.456.456.456
    There is a cName record www pointing to the squarespace domain "www.squarespace6.com"  (know this is unusual, but it is how squarespace asks this to be set up and does not work otherwise)
    There is an MX record with priority 10 and host name @ pointing to mail.mycompany.com
    I have a airport extreme router with the appropriate ports forwarded to the OSX server.
    The DNS servers on the router are pointed to the internal IP address of the OSX server
    I did not change the domain name on the router (mistake?) it is currently san.rr.com
    On the OSX server I have set up host name to be mycompany.comDNS is set up with primary zone being mycompany.com
    Primary Zone entries include
    nameserver = mycompany.com
    machine record host name is mycompany.com and the IP address is the internal IP address of the OSX server
    another machine record with host name "mail" and IP address is the internal IP address of the OSX server.
    Finally, there is a mail exchanger record with mail server "mail.mycompany.com" and priority 10
    There are 2 entries autocreated in the Reverse zone
    Mail is setup and running on the OSX server providing mail for "mail.mycompany.com"
    Users are setup with email address: [email protected] (note: without the mail subdomain - I think this is OK?)
    I am using self signed certificate.
    In my clients (windows Thunderbird, Mac Mail, iOS mail), the settings are for the incoming mail server host name to be "mail.mycompany.com" and the outgoing also to be "mail.mycompany.com"
    I woud have expected this to be imap.mycompany.com and smtp.mycompany.com respectively, but it doesn't work when I input these values and works with the former.  Have I set this up wrong??  imap seems to require SSL on port 993 and SMTP seems to require TLS on port 587.Outlook on PC gives me an error that after googling appears to be a problem with not recognizing a fuly qualified hostname form the SMTP client.  I see the fix, but wanted to know if that meant that my server didn't have a fully qualified host name and whether I should change that rather than just remove that restriction???
    The final problem is that my outgoing emails seem to be getting caught up in other people's spam filters too frequently.  What is the main reason for this?  Is it because I have set something up wrong and it brings up flags or is it simply because I am not a huge hosting company, or somethign else althogether?
    If you've gotten this far, big thanks!  If you can help me, even more thanks!

    Well, actually they are both getting caught up in spam filters and bounced back.  I actually realized that part of the problem is that I have a dynamic IP address, but it doesn't change.  Regardless, on the bounce back it looks like hotmail and other domains are rejecting email from my IP and recognize it as dynamic.  This was a test server that i would by physically taking to my business where there is a static business IP address (Cox).
    Sorry for the very long original message, but it seems that most people don't post enough information for the problem to be solved in their original posts and I was hoping to provide as much detail as possible.
    The other is the question of "are things set up right?"  It seems strange to me that both my outgoing and incoming servers are "mail.mycompany.com" and not imap.mycompany.com and smtp.mycompany.com and I wonder if this is going to cause me to have problems?
    Is it a problem that my email addresses are [email protected] and not [email protected]?
    Was I supposed to change the domain name on the router?
    Also is it going to be a problem that I am using a self signed certificate?

  • Autodiscovery and coexistence of two different exchange server

    Hi all,
    I'm trying to understand how autodiscovery works during coexistence of two different exchange server.
    We have one AD server and two different Exchange server and two users (A and B). 
    The mailbox of user A is in Exchange server ONE
    The mailbox of user B is in Exchange server TWO
    They are creating for the first time their profile in outlook. How autodiscover works in this scenario?
    Maybe the information are too few but I want to understand if in a scenario like this, Autodiscover can work with appropriate configuration or there is now way to use autodiscovery.
    Thank you
    Best Regards
    Riccardo

    Hi
    Riccardo,
    You dont need to worry about autodiscover if both are in the same forest.
    You just point your autodiscover to one of the server. It will proxy to the right server.
    For example if your autodiscover pointed to ServerONE and when a request comes from UserB, ServerONE will
    proxy  the request to ServerTWO. 
    Normally all point autodiscover to the internet facing server.
    Thanks, MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • 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

  • Exchange 2013 in coexistence with 2010, Outlook keep looking for Exchange 2010 server slow connection

    All,
    not sure if this topic has already answered, but can't find anything around.
    Here's the scenario. Migrating from a single Exchange 2010 to a cluster of 2 + 1 Exchange 2013. Two in a site, One in the other site (DC).
    I have migrated successfully a firsat batch of users. Mail flow works perfectly. The only thing is that often the migrated users are experiencing a long time (about 30 minutes) to get their Outlook syncronized. Both OL 2010 and 2013 doesn't make any difference.
    They're using OL Anywhere, and I've already tried to rebuild the profile.
    From a check on the OL connection status, looks like they're still looking for something on EX2010, but no idea what could be. If I disable the cache mode it works smooth and quick.
    My best guess is that is something in cache they're trying to keep updated... but still this doesn't explain the huge delay.
    Any help would be highly appreciated!
    Thanks!

    Hi Alessandro,
    What happens in OWA? I guess it should be good.
    Did you have public folders with Exchange 2010? Were they moved over to Exch 2013? Technically you should move the PF to the latest version from the legacy version before moving over the users?
    - Moved the PF to OL2013. same behaviour
    May be the outlook clients are looking for th OAB? Did you move the OAB to Exchange 2013?
    - Did this too.
    Try running outlook on safe mode and see what happens? may be one of the outlook add-in's are looking for something on Exchange 2010?
    - Will try that....
    Can you do a Test Email Auto Configuration in outlook (Hold CNTRL key and right click on outlook icon on status bar) and see if the exchange url's are pointed to Exch 2013?
    - Will try that....
    Is this happening to all migrated users or specific? Are they BlackBerry users?
    - All users and there are no BB users
    Do you have any archived emails on those migrated users? May be outlook is looking for some archived stuff on the Exch 2010 side?
    - I instructed Exchange to migrate also the archiving database, however There are no archived mailbox on 2010
    Could this be because of any calendar entries? May be migrated user mailboxes are having issues with working with non-migrated mailbox calendars?
    - This maybe a possibility. I have only 10 users actively using Exchange, while all others have the mailboxes only because they've Lync. I've completed all migrations today, so there shouldn't be anything left on 2010
    Let me know how it went - all the best!
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. Regards, Siva

  • OWA problem Exchange 2013 coexistence with 2010

    Hi all,
    I am in the midst of a migration from a single Exchange 2010 server to a two-server Exchange 2013 environment (both servers are CAS and MBX with DAG). Everything seems to work fine. I can access OWA on 2013 for mailboxes already moved to 2013, I use ActiveSync
    successfully but I cannot for the life of me figure out how to enable OWA 2010 proxying through 2013. I have checked many websites, forums etc. for it, I changed Authentication Methods back and forth and did everything I can think of but still... when trying
    to access OWA with a mailbox that is still on 2010 it fails with the following error:
    something went wrong
    A problem occurred while you were trying to use your mailbox.
    X-OWA-Error: Microsoft.Exchange.Data.Storage.NotSupportedWithServerVersionException
    X-OWA-Version: 15.0.913.21
    X-FEServer: <name of 2013 server>
    X-BEServer: <name of 2013 server>
    Maybe I should add that the new 2013 servers are installed in a completely different AD site which is connected through VPN to the 2010 site. In the new site I also have a loadbalancer in front of the 2013 servers.
    Actually I am still not sure if I need a different address in Exchange 2013 for OA, OWA and so on then in Exchange 2010. If I understood correctly there is no need for a legacy namespace anymore so I used the same URL for OA, OWA ... in both environments.
    This seems to be in conflict with the requirement that the OA URL in Exchange 2010 should point to the 2013 URL?!?
    Any help is greatly appreciated!
    Best regards
    Daniel

    Hi,
    How do you configure your Exchange virtual directories in Exchange 2010 and Exchange 2013? Please run the following command to provide detailed information about it:
    Get-OwaVirtualDirectory | Select Identity,name,Internalurl,ExternalUrl,*auth*
    According to your description, I noticed that it is set the same URL for OWA using. If the ExternalUrl
     for OWA 2010 is configured in your coexistence environment, please remove it. Then when external Users access OWA 2010, they can use OWA 2013 URL and be automatically proxy to Exchange 2010 and access their mailboxes.
    Regards,
    Winnie Liang
    TechNet Community Support

  • SBS2008: Move email from Exchange 2007 to new server with Exchange 2013

    We have an old server (SBS2008) and plan to buy a new server with (Server 2012). I need to move all the exchange emails, contacts & calendars to the new server. We will no longer use the old server. 
    Is there a document or migration tool that will help me understand how to move this data form the old exchange server to the new one? 
    Old Server:
    SBS2008 running Exchange 2007
    New Server:
    Server 2012
    Exchange 2013
    Any help is appreciated!

    Hi Dave,
    It can be done, and as Larry suggested you will consider two Server 2012 installs in order to achieve an environment that looks like your current SBS roles; Exchange 2013 on an Active Directory controller isn't a good long-term solution (SBS did this for
    you in the past).
    For your size operation, a virtual server host, with a Windows Server 2012 license, and two virtual machines would probably be a suitable design model.  In this manner, you have Server 2012 license that permits 1 +2 licenses (one host for virtualization,
    up to 2 Virtual Machines on same host).
    There's no migration tool. That comes with experience and usually trial and error. You earn the skills in this migration path, and for the average SBS support person you should plan on spending 3x (or more) your efforts estimate in hours planning your migration. 
    You can find a recommended migration path at this link to give you an idea of the steps, but its not exactly point by point going to cover you off for an sbs2008 to server 2012 w/exchange 2013 migration.  But the high points are in here. If it looks
    like something you would be comfortable with then you should research more.
    http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx
    Specific around integrating Exchange 2013 into an Exchange 2007 environment, guidance for that can be found here:
    http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
    If that looks like something beyond your comfort level, then you might consider building a new 2012 server with Exchange 2013 environment out as new, manually export your exchange 2007 mailbox contents (to PST) and then import them into the new mail server,
    and migrate your workstations out of old domain into new domain.  Whether this is more or less work at your workstation count is dependent upon a lot of variables.
    If you have more questions about the process, update the thread and we'll try to assist.
    Hopefully this info answered your original question.
    Cheers,
    -Jason
    Jason Miller B.Comm (Hons), MCSA, MCITP, Microsoft MVP

  • I bought a new imac running Loin and Office 2011. The server we use to access emails runs exchange 2003 and my IT person says the imac is not compatible with the server. The server does not want to let me access using any email software.

    I bought a new imac running Loin with Office 2011. I am the only mac in the office and the Server we use to access emails runs exchange 2003 and my IT person says the imac is not compatible with the server. The server does not want to let me access using any email software other than webmail access through our website. It looks as though 2011 is not compatible with 2003 per some searches online, but what are some options I have to gain full access again? I purchased parallels in hopes that this my help and I am able to use remote desktop connection to log on to server but can not drag and drop files I need. There is a shared drive on that Server we all use to exchange files.
    The two main issues are gaining access to my email again and ability to drag and drop files from mac to pc. I hope this is enough info to get some solutions.
    PS - IT person says my iMac's IP is what his server does not understand so that is why I can not login.

    Office 2011 is not compatbile with Exchange 2003.
    I suggest you post further Office related questions on Microsoft's own forums for their Mac software:
    http://answers.microsoft.com/en-us/mac

  • Exchange 2013 / 2010 coexistence with different public domains

    Currently in my organization
    1x Exchange 2010 Standard w/SP3 - Client Access / Hub Transport
    1x Exchange 2010 Standard w/SP3 - Unified Messaging Server (we also have Lync 2013 in the environment)
    1x Exchange 2010 Standard w/SP3 - Mailbox
    In my organization, we have approximately 600 mailboxes - 100 office staff, and 500 field employees using a mixture of Outlook 2007/2010/2013 and various mobile devices. Most of our field employees are in remote locations, several hundred
    miles away. We have no IT staff in any of our field locations.
    We also have two public domains that we use, though we are trying to phase out the old one to unify everything.
    domain-old.com - Used when the company had a different name. All Exchange services are published with this one.
    domain-new.com - Used after the company changed names. The goal is to publish all Exchange services with this one.
    domain.local - Our internal Active Directory domain.
    We use Microsoft Exchange Online Protection for all inbound/outbound email. We publish OWA, ActiveSync, etc. through our Sophos firewall. Also, we have two KEMP LoadMaster appliances that for high availability that we currently use for Lync 2013; they are
    severely underutilized.
    Goals for the Exchange migration
    My primary goal is to introduce high availability into our environment by introducing redundancy on multiple levels. I would like to accomplish this by utilizing Exchange 2013 since we will need to purchase additional licensing anyway. My idea of the
    final topology is:
    2x KEMP LoadMaster appliances providing reverse proxy and load balancing to the CAS servers
    2x Physical servers running Hyper-V, separated physically but in the same AD site. Each one would run:
    1x VM with Exchange 2013 Standard w/SP1 - Client Access
    1x VM with Exchange 2013 Enterprise w/SP1 - Mailbox - Utilizing DAGs for high-availability
    I'd like all the new Exchange services to be published under the domain-new.com domain - such as mail.domain-new.com, mail.domain-new.com/owa, smtp.domain-new.com, etc.
    We have purchased two new physical servers that will be Hyper-V hosts running Server 2012R2. My timeframe to start this project is within the next two weeks, so I'll be running the new Exchange 2013 VMs under Server 2012, not R2 as it won't be supported
    until Exchange 2013 SP3 is released.
    Deployment Plan
    Install Exchange 2013 on new VMs.
    Create CAS Array object.
    Configure Exchange 2013 to publish under the new namespace.
    Perform mailbox moves to 2013 for a small group (1-5 users) at a time. Recreate Outlook profiles and mobile device profiles for that group. Test and move to the next group.
    Once all users are moved to the new namespace, decommission the Exchange 2010 servers.
    Unknowns
    My primary unknown is about the namespaces. All of the guides I have read strictly deal with keeping the existing namespace and having the Exchange 2013 CAS proxy requests to Exchange 2010 for mailboxes still on 2010. This should never be an issue for us
    since we'll be using the new domain for each mailbox we move.
    My question boils down to, is this a supported way to migrate to Exchange 2013? And if so, are there some materials or information to help me perform it this way?

    Hi,
    From the description, you want to install Exchange 2013 in another domain and then migrate from Exchange 2010 to Exchange 2013. 
    About DAG, all servers in a DAG must be running the same operating system. If there is only one mailbox server, there is no need to deploy DAG.
    About CAS array, we should know that the CAS Array no longer exists in Exchange 2013.
    About the namespace, based on my knowledge, we can introduce a new namespace. Just as what you said "This should never be an issue for us since we'll be using the new domain for each mailbox we move".
    Here are some articles about how to upgrade from Exchange 2010 to Exchange 2013 in the same organization.
    Checklist: Upgrade from Exchange 2010
    Install Exchange 2013 in an Existing Exchange 2010 Organization
    Upgrade from Exchange 2010 to Exchange 2013
    Hope this helps.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • 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

Maybe you are looking for