I have two exchange 2013 node . Dag working fine, My scenario like that:

1. DC 2012 with (sharewitness)

2. EXCH-A

3. EXCH-B

My question is if one exchange is down , then my DAG will continue work?

Note: I have only single site.

I have two exchange 2013 node . Dag working fine, My scenario like that:

1. DC 2012 with (sharewitness)

2. EXCH-A

3. EXCH-B

My question is if one exchange is down , then my DAG will continue work?

Note: I have only single site.

Yes. If the File Share Witness is accessible, quorum can be maintained with one server up in your scenario.

Note that putting a File Share Witness on a DC is not recommended as you have to give the Exchange Trusted Subsystem group Domain Admin rights.

This is my test environment.

When i shutdown the Exch-A , my Exch-B not able to come up. My failover manager look like that. picture is attached and also exchange management shell not able to connect.

• Edited by libra_ali786 14 hours 7 minutes ago

This is my test environment.

When i shutdown the Exch-A , my Exch-B not able to come up. My failover manager look like that. picture is attached and also exchange management shell not able to connect.

That looks right, EXCH-A shows down, and everything else shows online.  Can you explain what you mean with Exch-B would not come back up?  Also, what's the error you get when you try to launch the ems?  can you connect to the EAC?

unable to browse https://exch-b.cnn.com/ecp    or      https://dag.cnn.com/ecp          . The error is http error 404. the requested resource not found.    and EMS error is

Why is the FSW path an IP address and not a server FQDN?

Nowhere near enough detail to really think about this.  Post

Get-DatabaseAvailabilityGroup -Status

For example, did you enable DAC? No mention of that.  If so then there are additional considerations about FSW reboots.

https://technet.microsoft.com/en-us/library/dd979790%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

Because the witness server's boot time is used to determine whether a DAG member can mount its active databases on startup, you should never restart the witness server and the sole DAG member at the same time. Doing so may leave the DAG member in a state where it can't mount databases on startup. If this happens, you must run the Restore-DatabaseAvailabilityGroup cmdlet on the DAG. This resets the DACP bit and permits the DAG member to mount databases.

DAC is not applied yet. I am new in DAG environment. is it necessary to apply DAC for the single site with two node?.

Please explain little bit for the necessity,

• Edited by libra_ali786 12 hours 52 minutes ago