Now that Exchange Server 2013 is gradually being used in some enterprises, I also want to share a question about the DAG's inability to add members when Exchange Server 2013 was just released, and then the following error occurred:
650) this.width=650; "height=" 139 "title=" image "style=" Border:0px;padding-top:0px;padding-right:0px;padding-left : 0px;background-image:none; "alt=" image "src=" http://s3.51cto.com/wyfs02/M02/6C/58/ Wkiom1vg5kqyxrioaahbvnwrc3w598.jpg "border=" 0 "/>
From here, in fact, Exchange Server 2013 and Exchange Server 2010 DAG Add, configuration and no difference, then after the completion of the addition of the above error, check the existence of DAG01, as you can see is there.
650) this.width=650; "height=" 367 "title=" image "style=" Border:0px;padding-top:0px;padding-right:0px;padding-left : 0px;background-image:none; "alt=" image "src=" http://s3.51cto.com/wyfs02/M00/6C/58/ Wkiom1vg5krdfy2naafvcu7euvk544.jpg "border=" 0 "/>
So why are you not going to find it? The final check was found to be due to synchronization problems, after the re-update domain synchronization, another current error in the Mailbox server log on the connection of the domain controller before the DAG01 information, once again execute the Add command, then you can add the normal.
This article is from the "Clumsy birds have" blog, make sure to keep this source http://tingdongwang.blog.51cto.com/1056852/1641659
A DAG cannot add member issues in Exchange Server 2013 error troubleshooting