Implementing Exchange 2013 DR Site

Hi All ,
We have current Exchange 2013 with 2 Mailboxes & 2 CAS servers , we would like to implement Exchange 2013 DR Site , to make only passive copy on DR Site once we have a problem with primary site the mailbox users connecting
to DR Site .
How can achieve this requirements ?
Thank you . 

Hi,
If your organization has a third location with a network infrastructure that is isolated from network failures that affect the two datacenters in which your DAG is deployed, then you can deploy the DAG’s witness server in that third location, thereby configuring
your DAG with the ability automatically failover databases to the other datacenter in response to a datacenter-level failure event.
If there isn't a third location for FSW server, you can failover to DR site manually. For more details, you can refer to the following article.
http://technet.microsoft.com/en-gb/library/dd351049(v=exchg.150).aspx
Hope this is helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Similar Messages

  • Exchange 2013 Multi Site Not SR/HA

    This is the first time we have deployed a multi site Exchange organization.  Here is the scenario and I am wondering if it is the correct one or if I should have done it a different way.
    We have a VPN setup between our corporate location and a satellite campus.  The satellite campus has it's own namespace and is a tree in our forest.  We have Exchange 2013 SP1 setup at the corp location.  We installed two Exchange 2013 SP1 servers
    at the satellite location in that domain in the same Exchange organization.  I was able to create a few linked users mailboxes (newly acquired and in process of user migration into our forest) and mail delivers between the two without issue.  But
    lately every new user will not receive email and they will be in the queue.  Does not matter if the email is from a corp user or a local user on the same mailbox server.
    We decided to do this because we want them to have all of their Exchange resources, email, CAS services and UM local to them, but they are still part of our system.  I am having a hard time finding why this is happening.  I also noticed that the emails
    sent from one satellite user to another is actually going through the corp hub transport server and not their local.  Sites and Services is setup with the correct subnets for each site.  I have verified the send and receive connectors.
    Is this scenario the best way to configure our organization or should we simply have created a second organization of their own and tried to share calendars, etc between the two?  All of our other services are centrally located so it only made sense that
    this should also work but before going live I wanted to see if this was the optimal way.  This is not a high availability or site resiliency plan.  No DAGs are used.  We are just one company with two separate very remote disjoint locations and
    even though we have a small VPN for services we would like to keep as much as possible local to that site.
    I have not been able to find information on this scenario.  Everything seems to point to SR/HA scenarios.  Any advice would be greatly appreciated.

    You can't create a second organization when the domain is in the same forest, so you shouldn't have done that.
    You're saying that SMTP messages are stuck in the queue?  That can be caused by any number of problems, but my experience is that it is most likely one of the following.  Look at the SMTP queue and see if any error code is listed, and post that
    here.
    1. In the main site, the site to which the messages are being sent, someone has modified the Default receive connector(s) in a way that the Exchange server can't connect.  The most likely issues would be modifying the PermissionGroups or RemoteIPRanges
    properties.  Best practice is to not modify the Default receive connector (except maybe to add AnonymousUsers to the PermissionGroups to allow inbound mail), and instead create a new connector for the special purpose with the connection limitations supplied.
    2. You have a firewall or relay device between the servers that's "helping" your SMTP connections (Cisco PIX firewalls are notorious for this, disable "SMTP Fixup") or breaking authentication.  The servers must be able to connect on port 25 without
    any molestation of the transactions.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2013 cros site blank page OWA/ECP

    Hello,
    I have an issue with a fresh installation of Exchange 2013 SP1.
    The are two AD site in different cities, connected by WAN link (site-to site VPN organized by Cisco ASA).
    I installed two Exchange servers in Site A (MBX1 and MBX2, both with MBX+CAS roles), and one Exchange server MBX3 in Site B (also both with MBX+CAS roles).
    Each Exchange hosts its own mailbox database (DB1, DB2, DB3 respectively), there are no DAG.
    Users spread over all databases. For example, user1 has mailbox in DB1, user2 - in DB2, user3 in DB3.
    When user1 opens OWA/ECP on CAS server MBX1 or MBX2, he successfully get into his mailbox.
    But, if user1 opens OWA/ECP on CAS server MBX3, he get blank page (no error at all).
    And vise versa:
    When user3 opens OWA/ECP on CAS server MBX3, he successfully get into his mailbox.
    But, if user3 opens OWA/ECP on CAS server MBX1 or MBX2, he get blank page (no error at all).
    I know, that Exchange 2013 is able to proxy request cross site.
    Where are no custom redirects set on IIS.
    Also I check IIS (Back End Site) for right certificate.
    There are no error in Windows Event log and IIS event Log.
    All ports are allowed between sites.
    Everything looks good.
    What I did wrong? May be I need to enable cross-site OWA proxy in Exchange somewhere?
    Or it is a CISCO ASA misconfiguration?
    Any help would be appreciated!
    Thank You!
    Pavel

    Hi,
    Firstly, I’d like to confirm if all your Exchange server are internet facing servers.
    We can try to clear the Forms based authentication on the non-internet facing server.
    And here is a similar thread you can refer to:
    http://social.technet.microsoft.com/Forums/exchange/en-US/85983a21-3922-46f4-b64a-d53c0a2271a7/issues-with-crosssite-cas-redirect-of-owa-users?forum=exchange2010
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Angela Shi
    TechNet Community Support

  • Exchange 2013 Multi site

    Hi
    I have Active directory 2012 R2  with sites ( A ,B)
    Site A
    I have 2 cas servers
    I have 2 MBX servers with DAG
    ALL users in site B has issue from slow outlook profiles , we suggest to create a CAS server there in B site and memeber of DAG 
    SO in site B we will have cas server + MBX member DAG
    Regarding users in B site how can i enforce the to connect the exchange throw the cas server located in B site ?
    How can i confirm that all smtp trafic will go from B site throw cas server located there then to the cas server located in A site then to the firewall ?
    is this scenario provide performance wise?
    all users for site B will have a DB and will be mounted on MX in B site .
    Please need suggestions .
    I need to have high performance for outlook profiles located in B site
    we have wan link between site A and site B but it is slow .
    Do I need to create another DAG ?
    when shall we have multiple DAG in our exchange organization ?
    Thanks
    MCP MCSA MCSE MCT MCTS CCNA

    Hi,
    Based on your description, CAS servers in site A are Internet-facing, CAS server in Site B are non-internet facing.
    In this case, all outbound mail for site B users will go from CAS in site B to CAS in site A and then to firewall and Internet.
    All inbound mails will go from CAS in site A to CAS in site B and then go to Mailbox server.
    Here is an article which may help you for your reference.
    http://technet.microsoft.com/en-gb/library/aa996349(v=exchg.150).aspx
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support
    Thanks for you reply Belinda ,
    Is it need any configuration from my side ?
    MCP MCSA MCSE MCT MCTS CCNA

  • Second Exchange 2013 server in remote site

    Just finished migrating from 2007 to 2013 and decommissioned 2007.  Exchange 2013 is running in site A with 350 mailboxes on it.  However, almost half of those users reside in site B so the plan is to introduce a second Exchange 2013 server to
    this site and migrating mailboxes to it.  There already exists a DC & GC in both sites.
    My question is, immediately after I introduce Exchange 2013 into site B with CAS & MBX role, client computers from that site will start to receive certificate errors.  Will updating the SCP on the new exchange server to point to the SCP on the exchange
    server in site A be enough to mitigate that problem?  What other precautions will I need to take?  Has anybody been down this road?

    Hi
    You can introduce the second exchange server in the remote site and also setup a DAG. If you are using the same name on your certificate like mail.domain.com then you can use the cert for your second server as well. You need to make sure you have autodiscover
    records setup correctly.
    Hope this helps. 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.

  • Exchange 2013/2007 coexistence: The Name on the Security Certificate is Invalid or Does Not Match the Name of the Site.

    In the midst of Exchange 2013/2007 coexistence configuration. 
    Currently:
    Exchange 2007:
    2 CAS\HUB
    1 Mailbox server
    Exchange 2013 (2 sites):
    LA:
    1 CAS
    2 MBX servers
    MKE:
    1 CAS 
    2 MBX servers.
    We purchased a certificate from Digicert and added every SAN name we could think of including "legacy.companyname.com", just to be sure. Added certificate to Exchange 2013 CAS servers and 2007 CAS\HUB boxes. Configured virtual directories on Exchange
    2013 MKE-CAS01 but not on Exchange 2013 LA-CAS01. Configured virtual directories to on Exchange 2007 CAS\HUB to point to "legacy.companyname.com". 
    Mailboxes have not been moved yet. I just wanted to get the coexistence between Exchange 2013/2007 up first but some users (not all) receiving
    "The name of the security certificate is invalid or does not match the name of the site" for
    "LEGACY.COMPANYNAME.COM". I remember configuring the AUTODISCOVER virtual directory for Exchange 2007. Any ideas? Thank you.

    Hi,
    Please make sure that the certificate with "legacy.companyname.com" name is enabled for IIS service. We can check it by running the following command in Exchange server 2007:
    Get-ExchangeCertificate | FL
    Thanks,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 migration between AD sites

    Hello,
    I am preparing a migration from one Exchange 2013 Cu6 server to another 2013 CU6 server in the same domain in a different  AD site. Each server is HT and MB server, hosting its own DB. There is no DAG between the 2 servers.
    I am planning to use coexistence between the servers during the migration when I move mailboxes from one server to the other. The move should be transparent to the users. Outlook should detect the move and find it automatically.
    I configured one namespace for all URLs, identical on both servers like "mail.organization.nl" for AS, OA, OWA, ECP and autodiscover.
    Would this work? I read here it will: The article is referrning to a DAG spanned over 2 sites, which I do not have.
    http://blog.netwrix.com/2014/03/21/configuring-exchange-2013-for-site-resilience-2/
    Any advice on performing this migration without issues?
    Thanks

    Hello,
    I am preparing a migration from one Exchange 2013 Cu6 server to another 2013 CU6 server in the same domain in a different  AD site. Each server is HT and MB server, hosting its own DB. There is no DAG between the 2 servers.
    I am planning to use coexistence between the servers during the migration when I move mailboxes from one server to the other. The move should be transparent to the users. Outlook should detect the move and find it automatically.
    I configured one namespace for all URLs, identical on both servers like "mail.organization.nl" for AS, OA, OWA, ECP and autodiscover.
    Would this work? I read here it will: The article is referrning to a DAG spanned over 2 sites, which I do not have.
    http://blog.netwrix.com/2014/03/21/configuring-exchange-2013-for-site-resilience-2/
    Any advice on performing this migration without issues?
    Thanks
    Mailbox Moves are pretty seamless, so not a concern.
    As far as the CAS namespaces. How are you handling that ? Load balancing between the CAS? Round Robin DNS? Or are you going to cut everything over at once and change DNS to point to the new server? Are both CAS accessible from the internet?
    Twitter!:
    Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Can I change system e-mail of exchange 2013 server

    Dear All
       I finished implement exchange 2013 in out office, but my boss is don't like when he receive e-mail form system when his mail can not send out or etc, can I change e-mail address from
    Microsoft Outlook <[email protected] 
    to system admin or etc, please guide me to complete it
    Thank you for your support

    Sorry  not clear a question, my problem,  like me send mail to  [email protected]   but user1 is never create on our exchange system, so when I send e-mail I must get return e-mail from system about these user is not in our system, and
    e-mail address that notify to me is "Microsoft Outlook <[email protected]>"
     I need to change it,  now I try with your guide, I create one user name [email protected], and userd command 
    Set-OrganizationConfig -MicrosoftExchangeReciepientReplyRecipient change to [email protected] but I test send tto wrong address again about return message is still come from "Microsoft Outlook <[email protected]>"please help me to complete it 

  • Hardware Type for Exchange 2013

    kindly need your assistant to electing the recommended DAS HDD 3.5 inch 15K or 2.5 inch 15K to implement Exchange 2013 and Share Point 2013. keep in mind the electing between Dell R620 and R720 ?
    Ahmed Zidan Network Administrator

    Hi,
    There is a calculator tool can help you, this calculator includes recommendations on sizing Client Access servers and Mailbox servers:
    Exchange 2013 Server Role Requirements Calculator v6.3
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Exchange 2013 user cann't access exchange 2013 public folder

    Hi, during the coexistence exchange 2007 and exchange 2013, outlook is unable to access public folder of exchange 2007 from exchange 2013, I've install CU2 for exchange 2013 and also set authentication to Ntlm, but also failed. please help to look into this
    problem, thanks.
    belows are information about outlook anywhere in our exchange.
    exchange 2007：(primary site)shmail04,shmail05,shmail06; (DR site)drpmail05,drpmail06
    exchange 2013：(primary site)shcas01,shcas02; (DR site)wxcas01
    Identity                           : SHCAS01\Rpc (Default Web Site)
    InternalHostname                   : infor.tdw.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : True
    ExternalHostname                   : infor.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHCAS02\Rpc (Default Web Site)
    InternalHostname                   : infor.tdw.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : True
    ExternalHostname                   : infor.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : WXCAS01\Rpc (Default Web Site)
    InternalHostname                   : infor.tdw.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : True
    ExternalHostname                   : infor.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHMAIL04\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHMAIL05\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHMAIL06\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : DRPMAIL05\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : DRPMAIL06\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}

    Hi,
    I have found an article said that we need to set the external host name the same. See more details in the following link:
    http://blogs.technet.com/b/mspfe/archive/2013/10/21/upgrading-to-on-premises-exchange-server-2013.aspx
    To allow your Exchange 2013 Client Access server to redirect connections to your Exchange 2007 servers, you must enable and configure
    Outlook Anywhere on all of the Exchange 2007 servers in your organization. If some Exchange 2007 servers in your organization are already configured to use Outlook Anywhere, their configuration must also be updated to support Exchange 2013.
    The following configuration is set on each Exchange 2007 server:
    The Outlook Anywhere external URL is set to the external hostname of the Exchange 2013 server.
    Sent By
    Silver

  • OWA still redirects to Exchange 2007 (legacy) after mailbox-move to Exchange 2013

    Hi,
    I am in the process of implementing Exchange 2013 in coex with 2007. I am testing now in a copy of the production environment and have installed the Exchange 2007 SP3 RU11 prior to installing Exchange 2013 using the SP1 media.
    We use a wildcard certificate and I prepared the Exchange 2007 internal/external URLs for OWA/OAB/etc to use the legacy.domain.com names and in Exchange 2013 I set them all to email.domain.com. Exchange 2013 has Outlook Anywhere configured.
    All tests like autodiscover (internally via SCP) run fine and for a new Exchange 2013 mailbox the Outlook and OWA functionality is as expected. A mailbox still on 2007 also connects fine via Outlook and while connecting to OWA (using the htps://email.domain.com/owa
    url) also redirects me to https://legacy.domain.com/owa just fine.
    HOWEVER: after a successfull mailbox-move from 2007 to 2013 my OWA logon-request STILL get's redirected to the 2007 legacy URL. When I then logon again on the 2007 OWA I get the message that I should connect to the 2013 URL and end-up in a loop.
    Anyone any tips where to search?
    Many thanks in advance.
    Best regards and many thanks in advance, Eric Vegter

    This seems to be an outstanding issue.
    We just performed a fresh install of Exchange 2013 on a Windows Server 2012 R2 operating system. We're migrating from our existing Exchange 2007 server. At the moment we have everything properly setup in a co-existence state. All we lack is to complete the
    migration of our mailboxes from the 2007 DB to the 2013 DB.
    In performing the first mailbox move, to test the migration process and make certain mail flows as expected, we noticed this same problem. Before reading through this thread, I was able to assign Full Access to a delegate user and then perform the "Open
    Mailbox" feature from a 2013 user's account. This was successful in opening the mailbox within OWA 2013. However, I still could not access the account by simply logging into the Outlook Web App. It would login, then proxy back to OWA 2007 with the message,
    "Use the following link to open this mailbox with optimal performance:
    http://mail.domainname.com/"
    After reading about cycling the OWA app pool, I immediately tried it as a workaround and it worked. It is a little frustrating going about it in this way. Hoping to see more activity on this thread.
    -Lorne

  • Exchange 2010 to Exchange 2013 Public Folder Problem

    Dear Experts,
    I am in a face of migrating Exchange 2010 to Exchange 2013. Below are my infrastructure details,
    1) Parent Domain in Site A (abc.com)
    2) One Child domain in Site A named child1.abc.com and Exchange 2007 is running in Site A child domain
    3) One Child domain in Site B named me.abc.com and currently Exchange 2010 is running in Site B.
    I have installed Exchange 2013 in Site B in coexistence scenario now Exchange 2013 users in Site B trying to attempt connection with a public folder store in the Site A Exchange 2007 servers instead of Site B Exchange 2010 servers.
    Anyone help will be highly appreciated.
    Thanks & Regards,
    ZB

    so you want users to access the PF in site B.
    Check the setting of Databases in Exchange 2013 and find out what is default Public Folder setup for those Database. You will basically need to change the default Public Folder in Exchange 2013 from Site A PF to Site B,, the way you have explained the scenario.
    run this for Exchanger 2013 DA
    Get-mailboxDatabase -Identity Exchange2013DBNAME | fl
    Get-MailboxDatabase -Identity e15-db1 | fl *PublicFolder*
    Where Technology Meets Talent

  • Exchange 2013 Servers booting from SAN

    Hi,
    One of my client has decided to go with NetApp Flexpods for implementing Exchange 2013 in their environment.
    It has also been decided that these servers will boot from SAN and
    Exchange 2013 will also be installed on SAN. 
    We are planning to Install Win 2012 R2 for OS and E2k13 CU8. Few questions:
    1) Is it supported to boot Windows Server 2012 R2 from SAN, Specially if that server is going to used for E2k13
    2) Is it supported to Install Exchange 2013 CU8 on SAN
    I researched about this and understood that this is supported from Windows OS perspective. I am more concerned about the whole configuration falling within support boundary of Exchange 2013. I found an article which talks about the complexity involved in
    troubleshooting and indicates that its mainly SAN vendor who would be troubleshooting if running into any issues.
    https://support.microsoft.com/en-us/kb/305547- This article is not yet applicable to 2012 R2. Its applicable only till 2008 R2.
    http://www.enterprisenetworkingplanet.com/datacenter/the-pros-cons-of-booting-from-san.html - Pro & Cons of booting from SAN
    The booting from SAN for Exchange servers concerns me a lot as i have never seen any implementation in Exchange 2003, 2007 & 2010 doing this in my 10 years of experience. I have supported about 10 different enterprise exchange deployments and never saw
    this. So this is an unknown territory for me, hence looking for some best practices, articles and guidance around this if its supported by Microsoft Exchange team to run Windows and Exchange from SAN.
    Thanks
    Siva

    Hello,
    Please see the “Supported storage architectures” in the following article:
    https://technet.microsoft.com/en-us/library/ee832792%28v=exchg.150%29.aspx
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Exchange 2013 w/Outlook 2013 "The name of the security certificate is invalid or does not match the name of the site"

    I've completed an upgrade from Exchange 2003 to Exchange 2013 and I have one last SSL message that I can't get rid of.  I've installed a 3rd party cert that is working great for webmail and cell phone access but for some reason the Outlook 2010/2013
    clients get prompted for a security warning.  I just implemented the SSL cert yesterday and I've noticed that new installs of Outlook seem to work just fine.  My Outlook 2013 client doesn't prompt me with the message but I have other users who are
    still getting the "The name of the security certificate is invalid or does not match the name of the site" error.  The domain on the cert error show up as server.mydomain.local.  I've gone through all the virtual directories and pointed
    all of my internal and external URL's to https://mail.mydomain.com.   This made one of the two warnings go away but not the second.  I've dug around on google and gone through everything I could find here and as far as I can tell my internal
    and external url's are configured properly and I can't figure out where this error is originating from.  Any ideas on where I should look outside of the virtual directories? 
    I'm including a good link I found that contains all of the virtual directories I updated.  I've checked them through both CLI and GUI and everything looks good.
    http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
    http://jaworskiblog.com/2013/04/13/setting-internal-and-external-urls-in-exchange-2013/

    Hi,
    When the Outlook connect to Exchange 2013/Exchange 2010, the client would connect to Autodiscover service to retrieve Exchange service automatically from server side. This feature is not available in Exchange 2003 Outlook profile.
    Generally, when mailbox is moved to Exchange 2013, the Outlook would connect to server to automatically update these information. It needs time to detect and update the changes in server side. I suggest we can do the following setting For autodiscover service:
    Get-ClientAccessServer | Set-ClientAccessServer –AutodiscoverServiceInternalUri https://mail.mydomain.com/autodiscover/autodiscover.xml
    Please restart IIS service by running IISReset in a Command Prompt window after all configuraions.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Creation of a second Exchange 2013 server on a different site (with the roles of MBX and CAS) fails on prepare active directory and prepare schema.

    Hello everyone
    I have a network infrastructure  consisting of 3 sites, site A, site B, and site C. i have 2 domain controllers on every site, and the AD roles are on the primary domain controller on site A. On site A I have an Exchange 2013sp1 CU6.
    I want to create a second Exchange on Site B, with the roles of mailbox (the exchange on Site A will be first DAG member and the Exchange on Site B will be the second member of the DAG) and CAS.
    First question: Is my  thought correct about installaing on the same server mailbox and CAS server?
    Second question: how many DAG witnesses I need for the DAG? One per site, or one in general (for example located on site A)
    Third question: When I am trying to perform “Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms”  I receive the error
    “ Setup encountered a problem while validating the state of Active Directory:
     The Active Directory schema version (15303) is higher than Setup's version (15292). Therefore, PrepareSchema can't be executed.  See the Exchange setup log for more information on this error. For more information, visit:
    http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx “
    I tried  to run the PrepareSchema from  the ISO of Exchange 2013 SP1 and form the extracted content of Exchange 2013SP1 CU6 archive, but still receive the same error. Any ideas?
    Thanks in advance.

    Thank you for your answer,
    I have tried to run "Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms”  from
    Exchange 2013 CU6 media, but I still receive  the error:
    The Active Directory schema version (15303) is higher than Setup's version (15292). Therefore, PrepareSchema
    can't be executed.  See the Exchange setup log for more information on this error. For more information, visit:http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx “
    any ideas?

Maybe you are looking for