The recommended way of installing the Exchange 2013 Edge Transport server is on a workgroup member (stand-alone server) in the DMZ. However, it is not uncommon that customers are implementing an Active Directory domain in their DMZ for management purposes.
Continue reading Edge Transport server fails in Active Directory domain
After moving several users successful from Exchange 2013 on-premises to Office 365 at one point the migrated stopped (for some users) with the following error message: “You can’t use the domain because it’s not an accepted domain for your organization”:
Continue reading You can’t use the domain because it’s not an accepted domain
On August 26 Microsoft released Exchange 2013 CU6, the sixth Cumulative Update since the new servicing model of Exchange 2013, exactly after 90 days which fits in the quarterly cadence.
In my previous blog post on Implementing and Configuring AutoReseed I’ve explained how to implement and configure AutoReseed in a Database Availability Group. In this blogpost I will explain what happens when a disk fails and AutoReseed kicks in.
Continue reading AutoReseed magically repairs a FailedAndSuspended Mailbox database copy.
Recently I had to implement and configure AutoReseed in Exchange 2013 and it wasn’t as easy as I figured in Advance. To be honest, I had to rebuild the DAG after fiddling too much with the Mailbox servers so it might well be a good idea to write down my experiences.
Jaap Wesselius 
You must be logged in to post a comment.