Error moving mailboxes?

So you’re cleaning out a storage group, and there are a bunch of mailboxes that you don’t seem to be able to move?

If you check the Eventlog, do you find these events?

The MAPI call ‘OpenMsgStore’ failed with the following error:
The information store could not be opened.
The MAPI provider failed.
MAPI 1.0
ID no: 8004011d-0289-00000000

For more information, click

Failed to open mailbox ‘/o=CONTOSO/ou=First Administrative Group/cn=Recipients/cn=JohnDoe’ in mailbox store ‘/o=CONTOSO/ou=First Administrative Group/cn=Configuration/cn=Servers/cn=ContosoMailServer/cn=Microsoft Private MDB81234567’ on server ‘ContosoMailServer’.
Error: The information store could not be opened.
The MAPI provider failed.
MAPI 1.0
ID no: 8004011d-0289-00000000

For more information, click

Quickly check if these users are not disabled.  Mailboxes with disabled users as associated account cannot be moved.  The workarounds are to enable the user accounts – which is not that desireable for your company’s Security staff – or assign SELF as the associated account.

More info at Microsoft.


Lost your disconnected mailboxes on Exchange 2007?

So you’re happily clicking and typing away, and you need to relink a mailbox to another AD user.  So you do the obvious:

  • Go into the Exchange 2007 Management Console (or Shell)
  • Find the mailbox in the Recipient Configuration
  • Write down the server the mailbox is stored
  • Disconnect the mailbox from the original AD user
  • Get a list of disconnected mailboxes on the server you wrote down

Only to find that the mailbox is not listed. Panic!

Did you forget to check the Deletion Settings on the mailbox store? No, on second glance they are the default 30 days, so the disconnected mailbox should still be available.

But, wait… On Exchange 2003, didn’t you run the Cleanup Agent to find disconnected mailboxes?

No such a thing in Exchange 2007, or is there?

Yes there is.  Clean-Mailboxdatabase is your cmdlet and friend.  Run Clean-Mailboxdatabase <databasename> in an Exchange Management Shell and reload your list of disconnected mailboxes.

You saved the day!  Or at least Exchange saved your job ;).

So next time:

  1. Get-Mailbox | Format-Table Name, Database
  2. Disable-Mailbox
  3. Clean-MailboxDatabase “Mailbox ServerMailbox Database Storagegroup Name”
  4. Connect-Mailbox -Database “Mailbox Database” -Identity “John Peoples”   -User

I Know

Microsoft held their Unified Communications launch event on Thursday in Louvain-La-Neuve, and I attended to see what all the fuzz is about.

Microsoft renamed it’s Live Communications Server to Office Communications Server with the 2007 release, and features new and improved features.

Communications Server is Microsoft’s answer to the possible information overload you could get when using e-mail, instant messaging, one or more cellphones and your desk phone, and the integration of all the personal internet experiences into an business environment.

The information worker of 5 years ago could live without IM, possibly even without his cellphone and was happy to communicate face to face, by his desk phone or by email.  The information worker has evolved, however, and is now using Instant Messaging at home to keep in touch with colleagues and friends, his cellphone has grown into a personal notepad and he keeps a blog, while at work he still communicates with his old one-trick deskphone and archaic e-mail.

The information worker of the future is the teenager of today: work is done in a team effort through IM, webcam conferencing, sharing desktops and being digitally omnipresent while physical presence loses importance.  These people will not fit in a business environment where the main communications platform are e-mail and a deskphone, and where physical presence is required to manage these communication methods.

The business that will succeed in offering a digital presence, will attract the information worker.  The business that will only offer physical presence, will appall these talented workers.

The issue with all these information streams is that currently, these are separate information streams: you need to ask your colleage something, so you look up his number to call him.  You dial the number into your deskphone, but he’s not available and you leave a message in his voicemail.  Following that, you send him an email to be sure he reacts.  The more urgent your question is, the more quickly you are going to repeat the above procedure until he reacts.  This all while in the mean time people are trying to reach you, and you are trying to do your work.

OK, so how does Office Communications Server fit in this vision of the future?  Communications Server delivers a central platform to interconnect your Exchange Server, Instant Messaging, mobile access and telephony.  All communications are connected, so before you call, you can see if someone’s available on IM or in any Office application (and application which uses the Communicator API).  If your contact does not respond to your IM message, he’ll get it when he is ready.  If you call your colleague and he does not pick up, your voicemail message generates an item in your colleague’s inbox.  And if you need to have a meeting but your colleague is not around, you can easily drop him into a conference call or conference webcam.

I’ll be testing this in the near future, to work together with Exchange Server (and it’s newly released Service Pack!).  In the mean time, be sure to check the I Know UC website.  So you’ll know… 🙂

edit: The speaker presentations are up on


Cannot install an update? Try this workaround.

One of many Microsoft patches used the Microsoft Update.exe Package Installer and that got me almost into trouble tonight…

The Update.exe Package Installer relies on Update.inf to check wheither the update, patch or hotfix is suited for the operating system and patch levels of your application.  Normally, this poses no problem, but at times you might have something running which was supported, and then not. …