Adding Rights to Public Folders (Recursively)
Sep26

Adding Rights to Public Folders (Recursively)

KB ID 0001598 Problem After a recent Exchange migration (2007 > 2013 > 2016), I had problems with users not being able to see public folders, one user could see them all, (so I know they were present and correct, content wise,) but other users could not even see them. Normally in this situation I’d test them in Outlook Web App first, if they work there then look at Outlook, but Public folders just didn’t work in...

Read More
Exchange ContentIndexState ‘Failed’
Sep04

Exchange ContentIndexState ‘Failed’

KB ID 0001591 Problem A client from a recent Exchange migration I had done, emailed me to say that his clients were having trouble searching their mailboxes, I jumped on remotely and saw that the mailbox Database content index status was showing ‘Failed’. ContentIndexState: Failed Solution I’ve had problems before with indexing here, I replicated the fix to remove the index and generate a new one. The process for...

Read More
Mailbox Move ‘StalledDueToMailboxLock’
Aug17

Mailbox Move ‘StalledDueToMailboxLock’

KB ID 0001581 Problem I was doing a migration from Exchange 2007 (on prem) to Exchange 2013 (on prem), this week. I had a number of mailboxes that were ‘StalledDueToMailboxLock’. Solution Nice easy fix, on the Source and Destination Exchange severs, restart the ‘Microsoft Exchange Mailbox Replication Service’. Wont this break my Mailboxes! No, it will interrupt the migration process, (which is already stalled)....

Read More
Exchange: Hide All Contacts From Global Address List
May30

Exchange: Hide All Contacts From Global Address List

KB ID 0001564 Problem I saw this on EE this evening, so I thought I’d work it out, what if your Global Address List is full of external ‘contacts’, and you want to remove/hide them? Solution First take a look at them, to see you’re not about to cause any damage! Get-MailContact | Where-Object {$_.HiddenFromAddressListsEnabled -eq $false} If you are happy, to remove/hide them from the GAL, simply do the...

Read More
Exchange and the LegacyExchangeDN Problem
Sep07

Exchange and the LegacyExchangeDN Problem

KB ID 0001468 Problem Why do we have the Exchange LegacyDN? It’s a throwback, from a time when we had our users, and our mail users in different databases. Below you can see the ExchangeLegacyDN for this Exchange on-premise user; /O=First Organisation/OU=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn={something-user-specific} Who cares? Well they are still important, if you send an internal email (to someone in...

Read More
Forward Mail From Exchange (On-Prem) To Office 365
Sep06

Forward Mail From Exchange (On-Prem) To Office 365

KB ID 0001467 Problem WARNING: Do not do this, if you are carrying out a Hybrid migration to Office 365! I’ve been doing an On-Prem to Office 365 migration recently. It was a little unusual because the ‘on-prem’ Exchange was not in the clients domain. So rather than migrate all the mail to their domain, and them migrate it to Office 365  we chose to use a third party migration solution ODME (Quest On Demand Migration...

Read More