AskTechGurus Get help now →

Email & Exchange Server

After an Exchange migration, the address book stops updating and mailbox moves fail

After moving to new Exchange servers and shutting down the old ones, the offline address book stops updating, cloud mailbox moves fail, and eDiscovery or calendar sharing breaks. Some of Exchange's hidden system mailboxes were left on the old servers.

What you’re seeing

  • New employees are missing from the Outlook address book, and departed ones still appear.
  • Mailbox moves to Microsoft 365 fail with errors that mention the migration mailbox or arbitration mailbox.
  • eDiscovery or compliance searches fail or never complete.
  • Calendar sharing with other organizations has stopped working since the old servers were shut down.

Common causes

Every environment is different, but these are the causes our engineers find most often:

  • Exchange's hidden arbitration mailboxes, including the one that coordinates migrations, still live on databases hosted by the retired servers.
  • Generation of the offline address book is assigned to a system mailbox that is no longer reachable.
  • The discovery search mailbox and other system mailboxes were never moved to the new servers.
  • The old servers were powered off rather than properly uninstalled, so Active Directory still lists them as hosting active components.

Why it matters

This problem tends to surface weeks after a migration that everyone thought was finished. Staff cannot find new colleagues in the address book and email the wrong people, cloud migration projects stall halfway, and compliance or legal teams lose the ability to run searches they may be obliged to perform. Because the old servers are gone, fixing it properly is harder than it would have been during the migration, and every week it continues adds to the stale data users rely on.

How AskTechGurus fixes it

Skip the trial and error. A certified engineer works on your actual system, finds the root cause, and fixes it properly.

Tell us what’s happening

Submit a ticket in about two minutes. Paste the error, describe what changed, and pick your tier. No charge to submit.

A certified engineer diagnoses it

A vetted, US-based systems engineer claims your ticket, usually within minutes during business hours, and investigates over a secure remote session you can watch and end at any time.

Fixed and verified with you

The engineer resolves the root cause and confirms with you that it’s working. You don’t just get a workaround, and you get a plain-English summary of what was wrong.

Pay only when it’s resolved

Fixed price from $99, invoiced only after you approve the fix. If it isn’t resolved, you don’t pay.

Frequently asked questions

Can we turn the old servers back on to fix it?

It depends on their condition. If they can still start cleanly they may help with recovery; if not, there are other routes. Our engineer confirms which applies before changing anything.

Is any mailbox data missing?

User mailboxes are not affected by this. The hidden system mailboxes hold configuration and service data rather than staff email, but they need to be in the right place for those features to work.

Still stuck? Let a pro take it from here.

AskTechGurus connects you with vetted, US-based systems engineers who fix this every day. No call centers, no scripts, no surprise bills.

Start now →