John Yassa's Blog

Home » 2014 » June

Monthly Archives: June 2014

Couldn’t connect to the source mailbox. while running New-MailboxExportRequest

When trying to export a mailbox to PST , we face the error

Couldn’t connect to the source mailbox.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemotePermanentException
+ FullyQualifiedErrorId : BEE464B8,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest

new-mailboxexportrequest

 

Exchange 2010 relies of MAPI when performing any mailbox export. I had to enable MAPI.

So all what you have to do is to enable the MAPI from the mailbox properties as below

EnableMAPI

 

Now run the command one more time after enabling the MAPI

new-mailboxexportrequest2

 

OneDrive for Business storage limit for each user will be increased from 25GB to 1TB

Starting on July 1 and over the next week, the OneDrive for Business storage limit for each user will be increased from 25GB to 1TB. As a part of this, any extra storage previously assigned to OneDrive for Business sites above 25 GB will be returned to the shared storage pool. Because all users will be moved to 1 TB, you no longer need to manage the OneDrive for Business storage limits. No action is required from you as these changes will be automatically applied.

Source: Office Blog

Error When enable archiving on mailbox hosted on office 365

When you try enable archiving on any mailbox hosted on Office 365 (withing hybrid deployment with exchange 2010) , you face the below error

1

“The following error occurred during validation in agent ‘Windows LiveId Agent’: ‘Unable to perform the save operation. ‘Fayis Khader’ is not within a valid server write scope.”

This problem occurs because recipient management must be performed from the on-premises environment when you’re using Active Directory synchronization.

To resolve this issue, enable archiving for the mailbox from the on-premises Exchange server. To do this, use one of the following methods.

Method 1: Use the Exchange Admin Center or the Exchange Management Console

In Exchange 2013
  1. Open the Exchange Admin Center.
  2. Click recipients, and then click mailboxes,
  3. Click the mailbox that you want to change, click Enable under In-Place Archive, and then click yes.
  4. Wait for two cycles of directory synchronization to run (about six hours). to force directory synchronization follow this article Force directory synchronization
In Exchange 2010
  1. Open the Exchange Management Console.
  2. In the console tree, expand Recipient Configuration, and then click Mail Contact.
  3. Right-click the contact that you want to change, and then click Enable Hosted Archive.
  4. Wait for two cycles of directory synchronization to run (about six hours).to force directory synchronization follow this article Force directory synchronization

Method 2: Use the Exchange Management Shell

  1. Open the Exchange Management Shell, and then run the following cmdlet:
    Enable-RemoteMailbox <UserName> -Archive
  2. Wait for two cycles of directory synchronization to run (about six hours). to force directory synchronization follow this article Force directory synchronization

How to force Directory Synchronization for Office 365

To force synchronization, log into your server that has the Directory Synchronization tool installed.

Open up Power Shell and navigate to C:\Program Files\Microsoft Online Directory Sync. as below

1

Start the Directory Sync Configuration Shell by typing .\DirSyncConfigShell.psc1 

2

This will launch the Directory Synchronization Configuration Shell.  Once this is open you can type the following command to force synchronization: Start-OnlineCoexistenceSync 

3

Now to confirm that the Synchronization has run , you can check from the office 365 portal

4

 

 

 

 

%d bloggers like this: