I have observed the similar situation couple of times in the past one year. Everything is normal from event viewer, server component state, service status, database copy health but the database activation will fail every time when I try to activate it from one of the nodes in 4 node DAG cluster. The databases are easy to do all possible operations in other 3 nodes, but one node. The issue…

Recently I observed this issue during the migration of Exchange 2010 to Exchange 2016. Following are the symptoms noticed not for all but for very few users (less than 1%). 1. Unable to do Deep search on Outlook Address Book (Cached mode), such as with phone number, department etc. 2. Unable to succeed “Test E-mail AutoConfiguration” test from Outlook 3. Availability information were not displaying 4. Outlook returns following error…

Since the introduction of DAG into Exchange Server architecture, the DR situations became more easy and comfortable to deal with. On this article I have tried to pen down a simple and straight forward process on how to deal with DR scenario. My LAB Servers: Exchange Servers (4 nos): EX16-01, EX16-02, EX16-03, EX16-Dr1 AD Servers: 2010adc1 & 2010adc2 (both work as Witness/Alternate Witness servers respectively) DAG Name: DAG02 (Please note…

We often think how to Move Exchange Server 2016 to Different Active Directory Site. This kind of situation arises when you plan to extend the Messaging Infrastructure DR for Site resilience. Replicating small databases are possible by installing Exchange Server in DR site, however it may not be viable option replicate databases over narrow bandwidth if we plan to host bigger databases. From Exchange Server 2010, we can easily shift/move…

You may experience similar problems in version from Exchange 2010, here I have showcased an issue I faced in Exchange Server 2016 infrastructure. You will see one or more of the following events/status on the server, Event IDs 4026, 1009 etc. Log Name:      Application Source:        MSExchangeRepl Event ID:      4026 Level:         Error Computer:      ex16-01.lab.ed.com Description: [Seed Manager] The seed request for database 'LAB-DB01' encountered an error during seeding. Error: An Exception…

You may receive the following error when you tried to re-add a recovered Exchange 2016 Mailbox server back to Database Availability Group (DAG). -A server-side database availability group administrative operation failed. Error The operation failed. CreateClustererrors may result from incorrectly configured static addresses. Error: An error occurred while attempting a clusteroperation. Error: Node EX16-01 is already joined to a cluster..- You may also see that the following error when trying…

This video help you understand the process of introducing or installing new version of Exchange, Exchange Server 2016 to existing environment. The LAB I have is with Exchange 2010 and not with Exchange 2013. But the process are the same to introduce the new exchange server.  Ensure you went through the pre-requisites such as the minimum patch level, AD requirements etc. This video walks you through only the installation procedure…

Updates for all versions of Exchange Servers are now available on the Microsoft Download Center. First ever update for Exchange Server 2016, Cumulative Update 12 Exchange Server 2013 and Exchange Server 2007 and Exchange Server 2010 Update Rollups are available for the customers to download and patch. More Details and Download Links, Cumulative Update 1 for Exchange Server 2016 - Download CU1 ver 2016  Exchange Server 2013 Cumulative Update 12 - Download…