Decommission a DAG member

I have a three member DAG group with Exchange 2010.  It's a single site with just three databases so I don't need three members.  I want to cleanly decommission the third member.  Most of the docs I've seen cover removing a failed member. 
This one is running and I need to find a doc that will guide me through removing it. 

Make sure you don't have any database copy on the third server or remove the copies. 
Remove a Mailbox Database Copy - https://technet.microsoft.com/en-us/library/dd298164(v=exchg.141).aspx
Then remove the server from DAG...
Remove-DatabaseAvailabilityGroupServer -
https://technet.microsoft.com/en-us/library/dd297956(v=exchg.141).aspx
Then you would be good to go for Uninstall (make sure it is not holding any other roles or if it does then remove from necessary things...)
Amit Tank | Exchange - MVP | Blog:
exchangeshare.wordpress.com 

Similar Messages

  • DAG member, PF database host, and hub maintenance (6hr power-off)

    Hello, 
    We have an EPO test coming up in one of our data centers that requires me to power off 2 of our 4 DAG members. In preparation for this I’ve been reading up on DAG member maintenance best practice as well as deconstructing the Start[Stop]DagServerMaintenance.ps1
    script. After testing in my lab I noticed that the iteration of Suspend-MailboxDatabaseCopy is followed by the parameter -ActivationOnly and sets ActivationSuspended to True. Why only suspend copy activation and not database copy processes? Does the script
    assume that DAG member maintenance does not include server shutdown or is suspending database copy processes not actually necessary? 
    Also, one of the DAG members I have to power off serves 1 of 3 of our PF databases. I’ve noticed that the Start[Stop]DagServerMaintenance.ps1 scripts do nothing for PF databases. Should I just unmount it and rely on standard PF replication to update it when
    I mount it back? Do I need to change my databases over to use a different PF database?
    The power-off duration is 6 hours so I'm not too worried about log build up. Our CAS servers are VMs and will be “motioned” to our other data center. We have two Hub Transport servers, I plan to simply power one of them off. Am I missing anything?
    Thanks!

    Belinda, 
    Your understanding and the article you provided on Managing Database Availability Groups seems to be inline with what I've described. However,
    just our of curiosity can you or anyone else explain why the script StartDagServerMaintenance.ps1
    only runs Suspend-MailboxDatabaseCopy -ActivationOnly? In other words, why does the script only suspend copy activation and not the copy process? 
    "Did the two Hub Transport servers locate in the same AD site?", yes they are in the same
    AD site but different physical locations. The article on HSS helped explain HT HA. 
    Thanks again! 

  • DAG Member Reboot & Outlook Connectivity

    Hello. I Have two Exchange 2013 CU3 Standard servers in a DAG. 
    The servers are running Server 2012 Standard.
    We’ve had a few users report that they sometimes encounter an error when trying to attach an Outlook item (e-mail message) to an existing item in a public folder calendar.
     The users can attach the item, but when they click on Save, a message stating that “Changes made to the item were lost due to a reconnect with the server.” appears.
      The clients are all running Outlook 2010 SP2.
    I have determined that in at least one case, and probably a few more, this happened during or shortly after, I was rebooting our passive DAG member as part of the process of installing Microsoft updates on it. 
    I use round robin DNS to achieve the load balancing needed to provide high availability. 
    A check on the connectivity status of an Outlook client shows the name of the DNS record associated with this as the proxy server. 
     The name is essentially “serverLB”.  Since I have DNS records for serverLB that point to the IP address of each DAG members, is it possible that some clients are connecting to the passive node, and, therefore, affected
    by it being rebooted?    I’d like to understand how rebooting the passive server causes the problem encountered by the Outlook users. 
    If you have any insights into that, please share them with me. 
    Thanks.

    Hi. Thank you for the response.
    I have two nodes in the DAG.
     The passive server is completely passive - it has no mounted databases.
    Please clarify your comment about checking "server health” on the active node when the passive node is rebooting. 
    What exactly do I look for, and what is the best method of doing this? 
    As far as checking replication health when the passive node is rebooting, I would expect Test-ReplicationHealth to indicate that replication is failing because one of the servers is rebooting and, therefore, unavailable. 
    With regards to database copy status, I would also expect that get-mailboxdatabasecopystatus * would report failures since the passive node is unavailable due to the reboot.
    Accessing the user mailbox through OWA rather than Outlook is a good idea. I'll try that during our next scheduled reboot. That, however, may not happen for about a week.
    I don’t have the money for a hardware load balancing solution, and network load balancing is incompatible with a DAG. 
    Consequently, round robin DNS is the only option for me.
    Please clarify your comment about adding HOST file entries. 
    Do you mean that if I add two entries for serverLB and the IP address of each server to the HOST file on each client, I could avoid the issue I have asked about?

  • Exchange 2010 SP3 - Can DAG member be on OS 2012 R2 STD?

    Hi guys.
    We have Exchange 2010 SP3 on 2008 r2 enterprise.
    now we are thinking about having DAG. I know that recommendations is to have the same OS on 2nd Exchange server but still is it possible to make DAG between: Exchange 2010 SP3 on 2008 r2 enterprise and on other side Exchange 2010 SP3 on 2012 R2 STD?
    with best regards,
    bostjanc

    Hi guys.
    We have Exchange 2010 SP3 on 2008 r2 enterprise.
    now we are thinking about having DAG. I know that recommendations is to have the same OS on 2nd Exchange server but still is it possible to make DAG between: Exchange 2010 SP3 on 2008 r2 enterprise and on other side Exchange 2010 SP3 on 2012 R2 STD?
    with best regards,
    bostjanc
    No. It wont let you do that. 
    http://technet.microsoft.com/en-us/library/dd638104(v=exchg.141).aspx
    DAGs are available in both Exchange 2010 Standard Edition and Exchange 2010 Enterprise Edition. In addition, a DAG can contain a mix of servers running Exchange 2010 Standard Edition and Exchange 2010 Enterprise Edition.
    Each member of the DAG must also be running the same operating system. Exchange 2010 is supported on both the Windows Server 2008 and Windows Server 2008 R2 operating systems. All members of a DAG must run either Windows Server 2008 or Windows Server 2008
    R2. They can't contain a combination of both Windows Server 2008 and Windows Server 2008 R2.
    In addition to meeting the prerequisites for installing Exchange 2010, there are operating system requirements that must be met. DAGs use Windows Failover Clustering technology, and as a result, they require the Enterprise version of Windows.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2010 Decommisioning a DAG member from a 3 node Dag

    Hi Guys,
    What the safest way to remove one server from a 3 Node Dag.
    Currently I am planning the following steps:-
    Remove Exchange server MAIL03 from DAG
    1.Start up Exchange Management Console
    2.Go to Organization Configuration > Mailbox > Database Management;
    3.if mail boxes are mounted on MAIL03, Select the database where ” Mounted on Server” reads the MAIL03;
    3.1.Select Move Active Mailbox Database;
    3.2.Select the Mailbox server i.e. MAIL01\MAIL02 to host the mailbox database copy and select Move;
    5.When the move has finished, select the database copy hosted on the MAIL03 in the lower pane. There, select Remove.
    6.Remove the MAIL03 server from the DAG. Select tab Database Availability Groups;
    7.Select the DAG the MAL03 server is a member of and select Manage Database Availability Group Membership;
    8.Select the server and click the red cross to remove it from the list. Click Manage to proceed with the actual removal;
    9.When finished the mailbox server is no longer member of the DAG.
    10.Rebalance Mailbox Databases in DAG.
    What do you guys recommend?
    Also after the removal of the DAG node, what the best way to reduce the Passive Database/Transaction logs? our current setup is as follows:-
    I want to remove the drives L,M,N,O
    Thanks
    Jitinder

    Hello,
    Based on your description.
    If you want to remove drives only from that server and leave databases working on the rest of nodes:
    1. Remove database copy on that server.
    2. Remove drives.
    It is not required to move mailboxes from these databases. In this scenario you will not be able to re-add copy of these databases because all nodes need to have the same drive
    letters.
    If you want to remove L, M, N, O from all servers:
    1. Move mailboxes from these databases.
    2. Remove them (copies and empty dabatabes).
    3. Remove drives.
    There is no need to remove server from DAG if you just want to remove database copy from one node. 
    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.

  • Taking down DAG member for maintenance

    Hello I need some advice on what to do.
    I have a two-member Exchange 2010 DAG.  One is an active server where everything is mounted.  The other is simply the passive server.  I will need to power down the passive server in a few days for some extended maintenance.  Roughly
    several hours.  I know for a fact (because I've been through this before) replication will be cut off during this time and as a result I cannot run a full Exchange backup to flush all the transactions logs and secondly, the copy queues will be very backed
    up.  Last time they were so backed up all efforts to reseed the passive copy of the mailbox databases failed.  In the end I think I had to delete and copy the active server's databases over.  That took a really really long time.
    So to avoid all that headache what should I do for this upcoming maintenance to make life easier?  
    - Is there a way I can literally STOP replication or even delete the passive copies of the mailbox databases just so I can run full backups and truncate transaction logs?  
    - Otherwise, assuming I have backed up copy queues, should I simply try reseeding or resuming synchronization?  Or should I not even waste time and delete all the passive copies and their files and start fresh with NEW copies?

    I've seen the "Failed and Suspended" status and recovered using the Update-MailboxDatabaseCopy
    command below. For example:
    PS] C:\>Get-MailboxDatabaseCopyStatus DB1\EX13-2 | fl Name,Status,CopyQueueLength,ReplayQueueLength,ContentIndexState
    Name                 : DB1\EX13-2
    Status               : FailedAndSuspended
    CopyQueueLength      : 3
    ReplayQueueLength   : 0
    ContentIndexState    : Failed
    We then update (or reseed) the failed database copy with the data from a good copy:
    [PS] C:\>Update-MailboxDatabaseCopy DB1\EX13-2 -DeleteExistingFiles
    I understand the reseed process can be lengthy but I'm not sure there are better (supported) methods.
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Rebooting a DAG member in DAC mode

    Hi Guys;
    I'm about to create a two members DAG with a FSW located in Site A. Both exchange servers are 2010 with SP3. As i 'm just starting my first ever DAG and the lack of knowledge/experience brought me here to avoid any misconfigurations.
    I'm planning on a two member DAG, the primary exchange and the FSW servers in site A, in site B a secondary exchange server. I will activate the DAC mode to avoid split brain situation and also will block the automatic activation of databases on the server
    in Site B, so i can have a full control over it, as power problems are a bit concern (it happens from time to time)
    Now what confuses me, is the windows update or exchange related patch installations.
    I would like to know if i can do regular windows updates in this scenario without moving the databases to the secondary server, and so for the exchange related updates.
    What is the best approach in this case?
    Thanks in advance.

    Well, I wouldn't set auto activation to block in this case so that whenever something happens to databases (for example putting server in Site A in maintenance for Windows or Exchange patching), all of them will be mounted on server in site B as next preference
    and users won't see any impact.
    If power goes for both servers in Site A (Exchange and witness) then database will be in service down situation since you have DAC mode setup and you need to execute the DAC mode activation anyways to mount all the database on Site B manually taking decision....
    http://eightwone.com/2010/08/30/datacenter-activation-coordination-mode/

  • Rpcclientaccess value blank on Active DAG member - normal?

    Hi,
    I decomissioned a Ex2010 server after moving all the mailboxes over to a new server in the same site a few weeks previously. Exchange was un-installed with no issues and no refernces were left in AD.
    Now, even though the mailboxes are accessible in Outlook on the existing profiles, I'm unable to set up a new profile as it defaults to the old server name, which no longer exists. Also, the users (thankfully only 3 on this DB) Blackberrys have stopped working.
    Done some troubleshooting and found that the BES is still seeing the old FQDN for these users. Upon checking the mailstore on the server, I found that its LegacyDN shows the old FQDN and that RcpClientAccessServer is blank. This mailstore is the active member
    of a DAG set up after the move so, it is normal for this to be blank?
    If not, would setting this to the correct FQDN help rectify the profile and BB resolver issue or would I need to change the LegacyDN as well?
    The Server is running Ex2010 SP1 with all roles (Its a small remote office so this is suffices).
    Any help would be appreciated.

    Hi,
    As far as I know, the RPCClientAccessServer value is established when the database is created.
    For more information about the basic rules used for determining the value, you can refer to the partition named configure your mailbox database in the following article:
    http://technet.microsoft.com/en-us/library/ee332317(v=exchg.141).aspx
    Thus, it’s not normal for the value to be blank.
    We can try Lrok’s suggestion to set the value.
    Please note that we should recreate the profile after we change the value to ensure client connectivity.
    Best regards,
    Angela Shi
    TechNet Community Support

  • Outlook not switched over to active DAG member after failover

    I have a 2 server DAG stretched across sites for DR.  Both of these servers are multi-role and have the HT, CAS, and MBOX roles.  Everything with the DAG seems to be working fine, as does what turned out to be an accidental failover to the remote
    site.  A fail back also went fairly smoothly.
    However, I've now discovered that some Outlook clients switched over to the DR server automatically and now they will not switch back.  I will come out right away and say that I do not have a CAS array.  I just learned about the CAS array while
    researching the problem.  After refreshing my own mailbox profile, everything swapped back, but obviously I don't want to go around everywhere making that change.  I don't even know how many people are still connecting to the DR server.  In
    fact, the only problem with the people that are connecting to the DR server is a little extra latency.
    Obviously, I would like this to work better, and would like a good way to get the outlook users swapped back to where they should be right now.

    There is a public folder and it is on the same server as the mailboxes.
    2014-05-05T19:58:17.555Z,239,0,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,10.1.1.32,fe80::45df:6c5e:aec6:fad1%14,ncacn_ip_tcp,,Connect,0,00:00:00.0312510,"SID=S-1-5-21-2073836326-1490033320-1384523041-3159, Flags=None",
    2014-05-05T19:58:17.571Z,239,1,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,OwnerLogon,1144 (rop::WrongServer),00:00:00,"Logon: Owner, /O=Company/OU=domain/cn=Recipients/cn=user in database Mailbox Database 2063624589 last mounted on Server1.Company.com at 5/2/2014 4:36:10 AM, currently Mounted; Redirected: this server is not in a preferred site for the database, suggested new server: /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Server1",RopHandler: Logon:
    2014-05-05T19:58:17.602Z,239,2,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,Disconnect,0,00:00:00.0781275,,
    2014-05-05T20:22:59.321Z,217,222,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,DelegateLogoff,0,00:00:00,LogonId: 0,
    2014-05-05T20:22:59.337Z,217,222,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,DelegateLogoff,0,00:00:00.0156255,LogonId: 1,
    2014-05-05T20:22:59.368Z,217,222,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,DelegateLogoff,0,00:00:00.0468765,LogonId: 2,
    2014-05-05T20:22:59.400Z,217,222,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,Disconnect,0,07:43:06.1863315,,
    2014-05-05T20:28:35.067Z,240,0,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,10.1.1.32,fe80::45df:6c5e:aec6:fad1%14,ncacn_ip_tcp,,Connect,0,00:00:00.0156255,"SID=S-1-5-21-2073836326-1490033320-1384523041-3159, Flags=None",
    2014-05-05T20:28:35.098Z,240,1,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,OwnerLogon,1144 (rop::WrongServer),00:00:00,"Logon: Owner, /O=Company/OU=domain/cn=Recipients/cn=user in database Mailbox Database 2063624589 last mounted on Server1.Company.com at 5/2/2014 4:36:10 AM, currently Mounted; Redirected: this server is not in a preferred site for the database, suggested new server: /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Server1",RopHandler: Logon:
    2014-05-05T20:28:35.113Z,240,2,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,Disconnect,0,00:00:00.0625020,,
    2014-05-05T20:28:35.348Z,241,0,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,10.1.1.32,fe80::45df:6c5e:aec6:fad1%14,ncacn_ip_tcp,,Connect,0,00:00:00,"SID=S-1-5-21-2073836326-1490033320-1384523041-3159, Flags=None",
    2014-05-05T20:28:35.379Z,241,1,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,OwnerLogon,1144 (rop::WrongServer),00:00:00.0156255,"Logon: Owner, /O=Company/OU=domain/cn=Recipients/cn=user in database Mailbox Database 2063624589 last mounted on Server1.Company.com at 5/2/2014 4:36:10 AM, currently Mounted; Redirected: this server is not in a preferred site for the database, suggested new server: /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Server1",RopHandler: Logon:
    2014-05-05T20:28:35.395Z,241,2,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,Disconnect,0,00:00:00.0468765,,
    2014-05-05T20:28:42.411Z,242,0,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,10.1.1.32,fe80::45df:6c5e:aec6:fad1%14,ncacn_ip_tcp,,Connect,0,00:00:00,"SID=S-1-5-21-2073836326-1490033320-1384523041-3159, Flags=None",
    2014-05-05T20:28:42.442Z,242,1,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,OwnerLogon,1144 (rop::WrongServer),00:00:00.0156255,"Logon: Owner, /O=Company/OU=domain/cn=Recipients/cn=user in database Mailbox Database 2063624589 last mounted on Server1.Company.com at 5/2/2014 4:36:10 AM, currently Mounted; Redirected: this server is not in a preferred site for the database, suggested new server: /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Server1",RopHandler: Logon:
    2014-05-05T20:28:42.457Z,242,2,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,Disconnect,0,00:00:00.0468765,,
    2014-05-05T20:28:57.708Z,243,0,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,10.1.1.32,fe80::45df:6c5e:aec6:fad1%14,ncacn_ip_tcp,,Connect,0,00:00:00,"SID=S-1-5-21-2073836326-1490033320-1384523041-3159, Flags=None",
    2014-05-05T20:28:58.005Z,244,0,/O=Company/OU=domain/cn=Recipients/cn=user,,SearchProtocolHost.exe,12.0.6672.5000,Cached,10.1.1.32,fe80::45df:6c5e:aec6:fad1%14,ncacn_ip_tcp,,Connect,0,00:00:00,"SID=S-1-5-21-2073836326-1490033320-1384523041-3159, Flags=None",
    2014-05-05T20:28:58.020Z,244,1,/O=Company/OU=domain/cn=Recipients/cn=user,,SearchProtocolHost.exe,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,OwnerLogon,1144 (rop::WrongServer),00:00:00,"Logon: Owner, /O=Company/OU=domain/cn=Recipients/cn=user in database Mailbox Database 2063624589 last mounted on Server1.Company.com at 5/2/2014 4:36:10 AM, currently Mounted; Redirected: this server is not in a preferred site for the database, suggested new server: /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Server1",RopHandler: Logon:
    2014-05-05T20:28:58.052Z,244,2,/O=Company/OU=domain/cn=Recipients/cn=user,,SearchProtocolHost.exe,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,Disconnect,0,00:00:00.0468765,,
    2014-05-05T20:28:58.677Z,243,1,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,DelegateLogon,0,00:00:00.9531555,"Logon: Delegate, /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=other user in database Mailbox Database 2063624589 last mounted on Server1.Company.com at 5/2/2014 4:36:10 AM, currently Mounted; LogonId: 0",
    2014-05-05T20:29:05.286Z,243,7,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,DelegateLogon,0,00:00:01.0469085,"Logon: Delegate, /O=Company/OU=domain/cn=Recipients/cn=cjoynt in database Mailbox Database 2063624589 last mounted on Server1.Company.com at 5/2/2014 4:36:10 AM, currently Mounted; LogonId: 1",
    2014-05-05T20:29:06.552Z,243,27,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,DelegateLogon,0,00:00:00.6718965,"Logon: Delegate, /O=Company/OU=domain/cn=Recipients/cn=cjoynt in database Mailbox Database 2063624589 last mounted on Server1.Company.com at 5/2/2014 4:36:10 AM, currently Mounted; LogonId: 2",
    2014-05-05T20:33:09.013Z,243,36,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,DelegateLogoff,0,00:00:00,LogonId: 0,
    2014-05-05T20:33:09.028Z,243,36,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,DelegateLogoff,0,00:00:00.0156255,LogonId: 1,
    2014-05-05T20:33:09.060Z,243,36,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,DelegateLogoff,0,00:00:00.0468765,LogonId: 2,
    2014-05-05T20:33:09.091Z,243,36,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,Disconnect,0,00:04:11.3830440,,
    2014-05-05T20:33:15.435Z,245,0,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,10.1.1.32,fe80::45df:6c5e:aec6:fad1%14,ncacn_ip_tcp,,Connect,0,00:00:00,"SID=S-1-5-21-2073836326-1490033320-1384523041-3159, Flags=None",
    2014-05-05T20:33:15.482Z,245,1,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,OwnerLogon,1144 (rop::WrongServer),00:00:00,"Logon: Owner, /O=Company/OU=domain/cn=Recipients/cn=user in database Mailbox Database 2063624589 last mounted on Server1.Company.com at 5/2/2014 4:36:10 AM, currently Mounted; Redirected: this server is not in a preferred site for the database, suggested new server: /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Server1",RopHandler: Logon:
    2014-05-05T20:33:15.497Z,245,2,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,Disconnect,0,00:00:00.0625020,,
    2014-05-05T20:33:15.763Z,246,0,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,10.1.1.32,fe80::45df:6c5e:aec6:fad1%14,ncacn_ip_tcp,,Connect,0,00:00:00,"SID=S-1-5-21-2073836326-1490033320-1384523041-3159, Flags=None",
    2014-05-05T20:33:15.779Z,246,1,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,OwnerLogon,1144 (rop::WrongServer),00:00:00,"Logon: Owner, /O=Company/OU=domain/cn=Recipients/cn=user in database Mailbox Database 2063624589 last mounted on Server1.Company.com at 5/2/2014 4:36:10 AM, currently Mounted; Redirected: this server is not in a preferred site for the database, suggested new server: /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Server1",RopHandler: Logon:
    2014-05-05T20:33:15.810Z,246,2,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,Disconnect,0,00:00:00.0468765,,
    2014-05-05T20:33:15.810Z,247,0,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,10.1.1.32,fe80::45df:6c5e:aec6:fad1%14,ncacn_ip_tcp,,Connect,0,00:00:00,"SID=S-1-5-21-2073836326-1490033320-1384523041-3159, Flags=None",
    2014-05-05T20:33:15.841Z,247,1,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,OwnerLogon,1144 (rop::WrongServer),00:00:00,"Logon: Owner, /O=Company/OU=domain/cn=Recipients/cn=user in database Mailbox Database 2063624589 last mounted on Server1.Company.com at 5/2/2014 4:36:10 AM, currently Mounted; Redirected: this server is not in a preferred site for the database, suggested new server: /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Server1",RopHandler: Logon:
    2014-05-05T20:33:15.857Z,247,2,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,Disconnect,0,00:00:00.0468765,,
    2014-05-05T20:34:26.375Z,248,0,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,10.1.1.32,fe80::45df:6c5e:aec6:fad1%14,ncacn_ip_tcp,,Connect,0,00:00:00.0156255,"SID=S-1-5-21-2073836326-1490033320-1384523041-3159, Flags=None",
    2014-05-05T20:34:26.390Z,248,1,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,OwnerLogon,1144 (rop::WrongServer),00:00:00,"Logon: Owner, /O=Company/OU=domain/cn=Recipients/cn=user in database Mailbox Database 2063624589 last mounted on Server1.Company.com at 5/2/2014 4:36:10 AM, currently Mounted; Redirected: this server is not in a preferred site for the database, suggested new server: /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Server1",RopHandler: Logon:
    2014-05-05T20:34:26.422Z,248,2,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,Disconnect,0,00:00:00.0625020,,
    2014-05-05T20:34:26.937Z,249,0,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,10.1.1.32,fe80::45df:6c5e:aec6:fad1%14,ncacn_ip_tcp,,Connect,0,00:00:00,"SID=S-1-5-21-2073836326-1490033320-1384523041-3159, Flags=None",
    2014-05-05T20:34:26.953Z,249,1,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,OwnerLogon,1144 (rop::WrongServer),00:00:00,"Logon: Owner, /O=Company/OU=domain/cn=Recipients/cn=user in database Mailbox Database 2063624589 last mounted on Server1.Company.com at 5/2/2014 4:36:10 AM, currently Mounted; Redirected: this server is not in a preferred site for the database, suggested new server: /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Server1",RopHandler: Logon:
    2014-05-05T20:34:26.984Z,249,2,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,Disconnect,0,00:00:00.0468765,,
    2014-05-05T20:34:27.234Z,250,0,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,10.1.1.32,fe80::45df:6c5e:aec6:fad1%14,ncacn_ip_tcp,,Connect,0,00:00:00,"SID=S-1-5-21-2073836326-1490033320-1384523041-3159, Flags=None",
    2014-05-05T20:34:27.250Z,250,1,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,OwnerLogon,1144 (rop::WrongServer),00:00:00,"Logon: Owner, /O=Company/OU=domain/cn=Recipients/cn=user in database Mailbox Database 2063624589 last mounted on Server1.Company.com at 5/2/2014 4:36:10 AM, currently Mounted; Redirected: this server is not in a preferred site for the database, suggested new server: /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Server1",RopHandler: Logon:
    2014-05-05T20:34:27.281Z,250,2,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,Disconnect,0,00:00:00.0468765,,
    2014-05-05T20:34:28.234Z,251,0,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,10.1.1.32,fe80::45df:6c5e:aec6:fad1%14,ncacn_ip_tcp,,Connect,0,00:00:00.0156255,"SID=S-1-5-21-2073836326-1490033320-1384523041-3159, Flags=None",
    2014-05-05T20:34:29.219Z,251,1,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,DelegateLogon,0,00:00:00.9687810,"Logon: Delegate, /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=other user in database Mailbox Database 2063624589 last mounted on Server1.Company.com at 5/2/2014 4:36:10 AM, currently Mounted; LogonId: 0",
    2014-05-05T20:34:30.250Z,251,2,/O=Company/OU=domain/cn=Recipients/cn=user,,OUTLOOK.EXE,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,DelegateLogon,0,00:00:01.0312830,"Logon: Delegate, /O=Company/OU=domain/cn=Recipients/cn=cjoynt in database Mailbox Database 2063624589 last mounted on Server1.Company.com at 5/2/2014 4:36:10 AM, currently Mounted; LogonId: 1",
    2014-05-05T20:36:00.971Z,252,0,/O=Company/OU=domain/cn=Recipients/cn=user,,SearchProtocolHost.exe,12.0.6672.5000,Cached,10.1.1.32,fe80::45df:6c5e:aec6:fad1%14,ncacn_ip_tcp,,Connect,0,00:00:00,"SID=S-1-5-21-2073836326-1490033320-1384523041-3159, Flags=None",
    2014-05-05T20:36:00.987Z,252,1,/O=Company/OU=domain/cn=Recipients/cn=user,,SearchProtocolHost.exe,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,OwnerLogon,1144 (rop::WrongServer),00:00:00,"Logon: Owner, /O=Company/OU=domain/cn=Recipients/cn=user in database Mailbox Database 2063624589 last mounted on Server1.Company.com at 5/2/2014 4:36:10 AM, currently Mounted; Redirected: this server is not in a preferred site for the database, suggested new server: /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Server1",RopHandler: Logon:
    2014-05-05T20:36:01.003Z,252,2,/O=Company/OU=domain/cn=Recipients/cn=user,,SearchProtocolHost.exe,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,Disconnect,0,00:00:00.0312510,,
    2014-05-05T20:36:07.909Z,253,0,/O=Company/OU=domain/cn=Recipients/cn=user,,SearchProtocolHost.exe,12.0.6672.5000,Cached,10.1.1.32,fe80::45df:6c5e:aec6:fad1%14,ncacn_ip_tcp,,Connect,0,00:00:00.0156255,"SID=S-1-5-21-2073836326-1490033320-1384523041-3159, Flags=None",
    2014-05-05T20:36:07.925Z,253,1,/O=Company/OU=domain/cn=Recipients/cn=user,,SearchProtocolHost.exe,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,OwnerLogon,1144 (rop::WrongServer),00:00:00,"Logon: Owner, /O=Company/OU=domain/cn=Recipients/cn=user in database Mailbox Database 2063624589 last mounted on Server1.Company.com at 5/2/2014 4:36:10 AM, currently Mounted; Redirected: this server is not in a preferred site for the database, suggested new server: /o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Server1",RopHandler: Logon:
    2014-05-05T20:36:07.940Z,253,2,/O=Company/OU=domain/cn=Recipients/cn=user,,SearchProtocolHost.exe,12.0.6672.5000,Cached,,,ncacn_ip_tcp,,Disconnect,0,00:00:00.0312510,,

  • Veeam backing up a passive DAG member with an active Public Folder DB on it.?

    Hi, Anyone here using VEEAM 7 to backup exchange 2010 sp2 (yes.. I know)?
    We have a DAG with two nodes. They are VMware machines. We are having issues with the backups. Specifically getting many many vss writer timeouts when snapshoting the machine and because the VSS is in a failed state it does not appear to be truncating the
    transaction logs. I have talk to veeeam extensively and they feel it is an MS issue..
    What i have noticed is that the VSS fails when freezing the pub folder store. It freezes, generates the shadow copy.. releases the shadowcopy and then say copy aborted
    Thoughts?
    Thanks.
    Drew

    Hi,
    Per my known, the default freeze timeout for the Exchange writer is 20 seconds, and this timeout can result in a failover from the active node to the passive node during snapshot creation.
    I recommend you increase the DAG heartbeat to check the result. For more details about this, you can refer to the following article.
    Configure Heartbeat and DNS Settings in a Multi-Site Failover Cluster
    http://technet.microsoft.com/en-us/library/dd197562(WS.10).aspx
    Besides, here is a related thread which may help you for your reference.
    VSS timeout with Exchange 2010
    http://forums.veeam.com/vmware-vsphere-f24/vss-timeout-with-exchange-2010-t5760-225.html
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
    sure that you completely understand the risk before retrieving any suggestions from the above link.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • UM Stops working if database is moved to other DAG member

    I have Lync 2013 and Exchange 2013 installed.  Exchange is 3 node DAG, Lync is 2 server pool.  Exchange servers are Exchangesvr01, Exchangesvr02, and ExchangesvrDR in another DataCenter.  Svr02 was the first one built.  Svr01 was added
    several weeks later.  If a UM enabled user's mailbox database is mounted on svr02, they can call the SA number, enter their extension, and get to UM OVA.  However, if I move the database to either svr01 or svrDR, when they call the SA number
    they will get a message saying "Sorry, this mailbox is on a server that does not support Unified Messaging".  Moving the mailbox back to svr02 solves the issue immediately.  Both servers are on the dialplan, UM service is running, they
    share the same UM certificate with both servers listed as SAN names.
    Anyone have any ideas?  I have re-run ExchUCUtil.ps1 and OcsUMUtil.exe.
    RJ

    Do you have any firewalls (windows firewall?) that would prevent connections to exchange on ports other than 5060/5061?
    UM calling works as follows..
    Call comes to the UM System attendant from Lync on 5060 or 5061 (secure)
    The SA will look up the location of the users mailbox and issue a redirect 302 move temporary on port 5062/5063 (secure) to route the call to the server where the users mailbox DB is active.
    If the redirect fails UM will play the error ""Sorry, this mailbox is on a server that does not support Unified Messaging"
    If the redirect is successful the DB server receiving the redirect will issue a 2nd move temporary to itself on one of the following ports. 5065 and 5067 for TCP (unsecured). 5066 and 5068 for mutual TLS (secured)
    At this point the audio data starts..
    The fact that you get audio shows you are at least reaching the SA on 5060-5061.
    You need to figure out what is causing the redirect to fail.

  • Emails are stuck in Drafts when shutting down one DAG Member

    Hi,
    We encountered a problem yesterday with our Exchange 2013 servers. We have 4 Exchanges 2013 servers (2 CAS + 2 MBX).
    We also have a DAG with the 2 MBX servers. When we shutted down our secondary MBX server (where the DB were active), the DB switched correctly on the first MBX server, but users could not send emails anymore, they were stuck into the drafts folder of Outlook.
    When we started the secondary MBX, emails were being sent as usual.
    In event viewer we had several "transport rules agent" warning, but the agent was running.
    We tried to shut down the primary MBX server this morning, and everything worked fine.
    So it seems we have a DAG with 2 servers, but only one of the servers can be shutted down...
    Any help for this issue ?
    Thanks

    Hi,
    Based on the description, emails could be sent successfully only when the secondary MBX was running, no matter where the active mailbox database was. If I misunderstood your concern, please let me know.
    Please check the database copy status when you shut down the secondary MBX.
    Please use the following cmdlet to check the receive connector settings on Mailbox Servers and compare the output on the primary MBX and secondary MBX.
    Get-ReceiveConnector -Server MBX | fl name, auth*, perm*, bind*, remote*, iden*, transport*, *port*
    If there is any customized connectors on Mailbox servers, please delete it and restart the transport service to check the result.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Two dag member no cas array

    I have two exchange servers (exchange 2010) in a dag with two databases. The production exchange server and a dr exchange server. Both of the exchange servers have a cas and I have not setup a cas array. I have set the  -RpcClientAccessServer to the
    production exchange server.
    Is this a valid configuration?
    Is it possible to prevent connections to the second exchange server? I find on email headers and on outlook 2010 connection status that there is connections to the second exchange server constantly, even though all mailboxes are on the production server
    and  -RpcClientAccessServer is production server.

    I will look at creating a CAS array then. I thought i would be able to get away with out it. I think what happened was that after adding the second exchange server i did not update the rpclientaccesserver property to point back to the production server,
    for some reason this automatically changed itself to the new exchange server. This means for a few weeks the users were connecting to the DR exchange server over a slow 100mbit link. As soon as i realized that i changed the rpcclientaccesserver property back
    to the production CAS on both databases.
    I found this http://www.mikepfeiffer.net/2011/04/determine-the-number-of-active-users-on-exchange-2010-client-access-servers-with-powershell/
    Very handy powershell script that tells you client connection status to the CAS. currently we have 85 users on production CAS and 20 still on the DR cas even though i set it back to correct CAS over a week ago. Now i need to look at moving these users over
    to the correct cas. But thinking might as well wait till we set up CAS array and then change all users that way.
    the reason i dont have active active is because its over a 100mbit link and is not as fast as the gigabit we have to the production exchange and is not on as fast storage or hardware. The DR exchange just sits on local storage on one esxi box with one other
    server. The rest of our vms are snap mirror across with netapp snap mirror to third party datacenter. In the event of a dr they will supply some new servers for use with the snap mirrored vms.
    In the event of a DR situation there is the understanding that it may take a day before we have everything up and running and this is accepted by the client. We are looking at improving this though and would be interested to hear any suggestions regarding
    improving exchange dr.
    I had some problems with the DAG last month. I had problem seeding one database and finally managed to get that workign and recently had to move the witness to another server as that stopped working with strange error. But now the DAG is 100% healthy with
    no issues, i think the 20 random email problem was caused by stuck emails in the users outlook 2010 on xenapp that he never reported, which is another known issue when migrating from outlook 2003-10. Still very concerning however.
    It would be very handy if there was some automated way to force outlook to the correct CAS only, say by changing a registry key with group policy. If anyone knows of any way to do that, would be helpful thanks.

  • SearchCatalogAvailabilityMonitor showing unhealthy for all database on DAG member mailbox server

    Hi All
    Help me to resolve server (all database) search catalogue availability monitor.
    I am facing a search catalogue "Unknown" issue for newly created copy database and also on same mailbox server
    "SearchCatalogAvailabilityMonitor" showing unhealthy for all database.
    For the newly created copy database I tried to reseed / update search index catalogue by using below PowerShell command but it stopped with below mentioned error.
    [PS] C:\Windows\system32>Update-MailboxDatabaseCopy -Identity DBTest\MBX1 -CatalogOnly
     Confirm
    Are you sure you want to perform this action?
    Seeding database copy "DBTest\MBX1".
    [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): y
    Confirm
    The mailbox database copy 'DBTest\MBX1' has failed to update from server . Do you want to clean up that update
    request now? Seeding cannot be requested for the same database copy until the failed request has been cleaned up by the
    server, which should automatically happen within 15 minutes.
    [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): y
    WARNING: Seeding of content index catalog for database 'DBTest' failed. Please verify that the Microsoft Search
    (Exchange) and the Host Controller service for Exchange services are running and try the operation again. Error: There
    was no endpoint listening at
    net.tcp://localhost:3863/Management/SeedingAgent-64310690-DEA4-47E1-9860-E8B2AC4E292A12/Single that could accept the
    message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more
    details..
    [PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus -Identity DBTest
    Name                                         
    Status          CopyQueue ReplayQueue LastInspectedLogTime   ContentIndex
                  Length    Length                            
    State
    DBTest\MBX2                              Mounted        
    0         0                                  Healthy
    DBTest\MBX1                              Healthy        
    0         0           2/8/2015 3:09:49 PM    Unknown
    DBTest\DRMBX1                            Healthy        
    0         0           2/8/2015 3:09:49 PM    Healthy
    Same time
    Result of get-serverhealth -server MBX1, also please note all database (Copy) search is in unhealthy condition and newly created copydatabase have no entry for "SearchCatalogAvailabilityMonitor".
    Name
    TargetResource
    HealthSetName
    AlertValue
    SearchCatalogAvailabilityMonitor
    DB01
    Search
    Unhealthy
    SearchCatalogAvailabilityMonitor
    DB06
    Search
    Unhealthy
    Reg
    Aditya

    Hi Deepak
    My both exchange servers on hyper V and there should not be resource problems.
    However I have already rebooted server. but it wont help.
    Mean while I get success to make search component healthy on my problematic server by below command but still content index folder is not coming automatically.
    [PS] C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\Installer>.\installconfig.ps1 -action I –dataFolder  "C:\program files\Microsoft\Exchange Server\V15\bin\search\ceres\hostcontroller\data"
    Configuring Search Foundation for Exchange....
    Successfully configured Search Foundation for Exchange
    By running this command these are in health state now.
    Name
    TargetResource
    HealthSetName
    AlertValue
    SearchCatalogAvailabilityMonitor
    DB01
    Search
    healthy
    SearchCatalogAvailabilityMonitor
    DB06
    Search
    healthy
    Reg
    Aditya

  • [SOLVED] Can't add a node to the cluster with error (Exchange 2010 SP3 DAG Windows Server 2012)

    Hi there!
    I have a problem which makes me very angry already :)
    I have two servers Exchange 2010 SP3 with MB role started on Windows Server 2012. I decided to create a DAG.
    I have created the prestaged AD object for the cluster called msc-co-exc-01c, assigned necessary permissions and disabled it. Allowed through the Windows Firewall traffic between nodes and prepared the File Share Witness server.
    Then I have tried to add nodes. The first node has been added successfully, but the second node doesn't want to be added :). Now I can add only one node to the DAG. I tried to add different servers first, but only the first one was added.
    LOGS on the second nodes: 
    Application Log
    "Failed to initialize cluster with error 0x80004005." (MSExchangeIS)
    Failover Clustering Diagnostic Log
    "[VER] Could not read version data from database for node msc-co-exc-04v (id 1)."
    CMDLET Error:
    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:06:21
    MSC-CO-EXC-02V
    Failed
    Error:
    A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode()
    (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. [Server: msc-co-exc-04v.int.krls.ru]
    An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed..
    This operation returned because the timeout period expired
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.ExC9C315
    Warning:
    Network name 'msc-co-exc-01c' is not online. Please check that the IP address configuration for the database availability group is correct.
    Warning:
    The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-11-17_13-54-56.543_add-databaseavailabiltygroupserver.log".
    Exchange Management Shell command attempted:
    Add-DatabaseAvailabilityGroupServer -MailboxServer 'MSC-CO-EXC-02V' -Identity 'msc-co-exc-01c'
    Elapsed Time: 00:06:21
    UPD:
    when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
    I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
    on both nodes.
    It's confused me, because there is normal connectivity between these DAG members through the main interface.
    Please, help me if you can.

    Hi, Jared! Thank you for the reply.
    Of course I did it already :) I have new info:
    when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
    I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
    on both nodes.
    It's confused me, because there is normal connectivity between these DAG members through the main interface.

Maybe you are looking for