The checks described in this article are the result of what we normally check during troubleshooting. Some of these already have specific error events, but the objective here is to try to avoid that these events occur. We plan to keep the post updated and add more checks that we identify as useful. Also, we […]
On a recent project I was asked if I could block certain users from seeing the Default Global Address List, these users worked for the client externally sourcing business, they needed to mail on behalf of the client but the client did not want them to be able to see other users on the GAL. […]
Exchange 2010 introduced the concept of Datacentre Activation Coordination (DAC). DAC is a property found on a Database Availability Group (DAG). It still remains slightly mysterious to some folks out in the field, so its certainly worth bringing it back up for discussion. Tim McMichael’s famous paper plate demo with lots of willing participants was one of […]
I had a customer where Exchange 2013 FAST Search Technology failed and rebuilding the search indexes for the databases did not resolve the problem on a single Exchange 2013 SP1 server. In this blog post I’m going to share with you the symptoms of my issue along with the resolution. Symptoms of Issues Users on […]
Microsoft introduced a new protocol in Exchange Server 2013 SP1 called MapiHttp (codename Alchemy). This is an Office 365 development to replace the traditional RPC/HTTPS protocol used in Outlook Anywhere. Outlook Anywhere was developed in the Exchange 2003 timeframe to use Outlook 2003 over the Internet. Outlook is using RPC to communicate with the Exchange […]
During Exchange migration (2007 –> 2013) in one of my customers I was faced into frustrating issue. Although this basic issue isn’t new, the resolution of this issue required multiple resolution steps. In addition, during my research I couldn’t find a full guide that cover all the required resolution steps, although the Outlook Password Prompt […]
When moving mailboxes between Exchange databases the move complete with a warning. This is because Exchange server sometimes does not fully delete the mailboxes from the source database immediately upon completion of the move the source mailbox database is switched to a “soft-deleted” state. To resolve this you need to remove the disconnected or soft deleted […]
If you move a lot of users from one Server to another (or from one DB to another) you might wish to complete all such requests without typing the full name from the user. The following PowerShell command could be used to clean (e.g. Remove) all completed Exchange mailbox move requests Get-MoveRequest -movestatus completed | […]