Exchange Online Archive–Counting Archives

Posted on Leave a commentPosted in archive, exchange, exchange online, Exchange Server, EXO, IAmMEC, Office 365

If you are using Exchange Online Archive and what to get a count of the number of users with an archive, or a list of the users with an archive, then the following PowerShell scripts will give you this info:

List all users with an Exchange Online Archive:

Get-MailUser -ResultSize Unlimited | where {$_.ArchiveName -ilike “In-Place Archive*”}

Count all users with an Exchange Online Archive:

(Get-MailUser -ResultSize Unlimited | where {$_.ArchiveName -ilike “In-Place Archive*”}).Count

Both of these PowerShell cmdlets need to be run in Exchange Online via Remote PowerShell.

Errors in Moving Exchange Archive Mailboxes to Office 365

Posted on 2 CommentsPosted in 2010, 2013, archive, cloud, exchange, exchange online, Office 365, Outlook

I was trying to move an Archive mailbox to the Office 365 service from my demo environment the other day when I came across an error I thought I would note down here for completion. I could not find the error elsewhere on the internet

An archive mailbox must be enabled before it can be moved

Now this sounds a stupid sort of error, because if I am moving an archive mailbox then it must already be enabled or the move mailbox wizard will not let me move it. But the mailbox does have an archive on the Exchange organization on-premises, but when the move has completed it has errors reported.

The reason for the error is all down, in my case, to two things.

  1. Its a demo environment and I am doing things too quickly
  2. DirSync is not working at the moment.

In my scenario the DirSync services on my server had stopped a few weeks ago and I had not started them – ensure that DirSync is running. And secondly, as it was a demo I was doing I was creating an archive mailbox and then moving it to the cloud shortly afterwards. Even if DirSync was running, the chances are that it would not have had a chance to sync the existence of the archive mailbox associated with the user account to Office 365’s directory. Archive mailboxes can only be moved from on-premises to the cloud if the cloud service knows about the mailbox archive to move.

To fix my issue I restarted DirSync services and forced a full sync with the cmdlet Start-OnlineCoexistenceSync –FullSync. See http://technet.microsoft.com/en-us/library/jj151771.aspx#BKMK_SynchronizeDirectories on the steps to force a directory sync for running this cmdlet.

Once the sync was completed and Office 365 directory is aware that my user has an on-premises archive I was able to move the archive to Office 365 and keep the mailbox on-premises.

Of course, if I want to create an archive in the cloud with a mailbox on premises for real (not a demo) then I would just create the archive straight in the cloud. My scenario and the three hour DirSync delay (or forcing DirSync) was only needed as I had created an archive and then moved it.

Outlook Archive Appears to be Duplicated

Posted on 3 CommentsPosted in archive, exchange, exchange online, Office 365

A client sent me the following screenshot today, and though redacted you can see that their Outlook mailbox has more than one Online Archive showing:

image

This users mailbox was not the only one in the company, but you can see how the mailbox is showing three Online Archives and seemingly all for the same mailbox. Look closely though, and they contain different content by way of subfolders.

This is because these archives belong to other users that this user has permission to open their mailbox. In Exchange 2010 and later, if users are granted full access to mailbox then Outlook automatically shows the mailbox. An update to Exchange 2010 allowed this automapping to be controlled if permissions are given via the command line.

So to fix this issue in Outlook, remove the permission and add it again with -Automapping:$false

Remove-MailboxPermission -Identity user b -User user a -AccessRights FullAccess

Add-MailboxPermission -Identity user b -User user a -AccessRights FullAccess –AutoMapping:$false

Then wait several hours and repair the users profile. After profile repair you now need to add the mailbox that you have full access to into Outlook.