Our website use cookies to improve and personalise your experience and to display advertisements (if any). Our website may also include cookies from third parties like Google Adsense, Google Analytics, Youtube. By using the website, you consent to the use of cookies.

DAG

I’m happy to announce support for use of an Azure virtual machine as an Exchange 2013 Database Availability Group witness server. Automatic datacenter failover in Exchange 2013 requires three physical sites, but many of our customers with stretched DAGs only have two physical sites deployed today. By enabling the use of Azure as a third physical site, this provides many of our customers with a cost-effective method for improving the overall availability and resiliency of their Exchange deployment. You can learn more about the deployment and configuration process, as well as learn about our best practices in the TechNet Library…

I was performing an SP2 upgrade on a clients Exchange 2010 Sp1 environment today and whilst upgrading the first "Mailbox Server Role" in the DAG the upgrade process came up with the following error:- Error: The following error was generated when "$error.Clear(); if ($exsSid -eq $null -or $exsSid -eq "") { $exsSid = get-ExchangeServerGroupSID -DomainController $RoleDomainController } start-setupservice -ServiceName MSExchangeADTopology -ServiceParameters $exsSid,$RoleDomainController " was run: "Service 'MSExchangeADTopology' failed to reach status 'Running' on this server.". Service 'MSExchangeADTopology' failed to reach status 'Running' on this server. Looking at the exchange setup logs it was discovered that the Exchange Trusted Subsystem was not a member of the Builtin Administrators…