How to Add an extra email address to your O365 mailbox the right way

This blogpost describes how to add an extra email address on your O365 mailbox. Someone told me that when he tries to add an extra email address using the Office 365 admin partner he receives the following error :


The error says that this action (adding an extra email address) should be performed on the object in your on-premises organization. This means that your Active Directory is connected to Azure (O365). So extra email address should be added on the specific user properties and not directly using the Exchange admin interface. Your changes are automatically replicated to Azure.

Go to your domain controller and open dsa.msc (Active Directory Users and Computers) and go to the user you wish to provide an extra email address. Important : don’t search for this specific user, this way you don’t see all the properties later on. Also make sure that you have the advanced view enabled in dsa.msc, otherwise you won’t see the Attribute editor tab.


Open the properties of the specific user and select Attribute Editor and go to ProxyAddresses. Now you have the option to add an extra emailaddress, use the following Value :

Make sure that the domain is registred correctly in O365.

(Thanks to Roelf Z for the comment)


How to export an Exchange Mailbox to PST

Exchange 2010 SP1 and later doesn’t allow by default for any user to export a mailbox. You have to assign those rights to a specific user. Use the following command :


New-ManagementRoleAssignment –Role "Mailbox Import Export" –User domain\user


Now that we have an user with the appropriate rights, make sure you have the location ready where you wish to store the PST files. Make sure that this folder has read/write rights to the Exchange Trusted Subsystem :


Now export the mailbox to a PST with the following command:

New-MailboxExportRequest –Mailbox user –FilePath \\servername\Export\user.pst


Use the following command to show the progress


Get-MailboxExportRequest -Name MailboxExport | fl


When the export has been completed, remove the mailbox from the old Exchange system using the following command:

Get-MailboxExportRequest | where {$_.status -eq "Completed"}

Solved : Cannot display the folder.

I found out that opening very large mailboxes (several GB’s) using Outlook 2013 (32 bit) I ran into a not enough free memory problem :



After some troubleshooting I found out that there are 2 solutions. The first one is completely disable caching of the mailbox. But that was not a working solution for me, because sometimes I want to open my email without a working internet connection. This is the solution that worked for me :



Leave use cached exchange mode on, and clear (disable) the download shared folders and download public favorites.

I’ve never seen the error since!

Advanced administration Office 365 3

More and more companies start using Office 365 (including me:-)). The interface is simple and administration is fairly easily to use. But sometimes you wish you could do that little bit more, those things you could do when running Exchange 2013. I’ve got a surprise for you… you can!

Ok, let’s assume you are running Office 365 with one or more licenses. You probably now how to log on. Let’s go to and use your credentials to logon :


After entering the credentials you see something like this :


Go to Outlook and you see you inbox. Ok, pay attention. You now see that your url has change to something more. Let’s change everything after .com/ to /ecp. So you have the following url


And (when you are an administrator of your Office 365 account) you now see the following screen :


Wow! That looks familiar! You now have (almost) full control over your Office 365 account. (Which uses Exchange 2013 under the hood).

Now it’s possible to :

  • administrator advanced options
  • access to malware and quarantaine filters
  • track and trace emails
  • create and administrator public folders
  • configure archiving etc

More information soon in part 2

Review MigrationWiz

Because I’m doing more and more Office 365 migrations I was looking for a solution to automate this proces. I was looking for a tool that could automatically migrate mailboxen, contacts, public folders etc. Ofcourse using PST-files is one way to do it, but when you are migrating lots of data (Gb and/or users) this could take some time. I’ve heard the name BitTitan several times their product MigrationWiz seems to good to be true. I decided to ask them for a trial license to test the product.

MigrationWiz doesn’t require any special software, this because it’s all webbased. Just go to the website and login. After logging in you see the following :


First you have to create a connector. A connector is the link between your old en your new environment. Setting up a connector is an easy thing to do :


In the above picture you can any source configuration you are using, you can choose the same options in the target. So you can use MigrationWiz for the fallback scenario also.

You can also specify what to migrate :


Ofcourse you can migrate emails, but also calenders, contacts but also the rules(!) I particularly like that option because I created many rules to move incoming mails to their folders and their is no other easy way to export/import those.

After creating your first connector you can find it in the manage connector section :


In this view you can easily edit the connector, view statistics and see the mailboxes you are about to migrate.

After creating the connector you can add the mailboxes you wish to create. Their are several ways to do that. First you can manually add them :


You don’t have to have each user’s password. You can select one migration account which has access to all the exchange accounts.

Another way is to do a bulk import :


As you can see in the above screen, everything is fairly easily and their is little room for mistakes. It would be nice although if you could select the mailboxes from a list that MigrationWiz provides but that option isn’t (yet?) available.

After adding the mailbox(es) you can start the migration with the option buttons :


The first button is to start the migration, the second gives you the details, you can change the settings of delete the mailbox from MigrationWiz (not Exchange!)

After starting the migration you can see the progress in detail :







At this point you just have to wait for the mailboxes to complete. 🙂

Other thing I think are worth mentioning :

Migration Skydrive / Google Drive data :


Migration Public Folders :


It’s also possible to export all your exchange data to PST for back-up or legal reasons :



I’m very enthousiastic about MigrationWiz and I think I will testdrive their other products also. Migration maildata is easy and works as it supposed to. Some minor improvements would be nice like the option to select the mailboxes instead of importing them with one of the bulk options. I also noticed that the impact on the source exchange system is noticeable, but you can tweak the options. So look out for importing all your exchange data during daytime without looking into the tweak options.

Do you have any questions? Leave a comment!

 Functionality  [s3r star=4/5]
 Stability  [s3r star=4.5/5]
 Support  [s3r star=3.5/5]

Do you like this review? Please vote!


Messages stuck in Exchange 2010 queue (resolved)

Today a collegae of mine ran into a problem with Exchange 2010. Messages both internally/externally were not delivered. We noticed that the Exchange server was using 100% CPU resources.  After some investigation we noticed that the submission queue was building up.

We decided to suspend the queue, exporting the messages. Then deleting the queue and recreating it. Finally we imported the exported messages. We used the following steps :

First open the Exchange Management Shell

Show all Exchange queues


Suspend all messages in this queue

get-queue exchangeserver#submission | get-message | suspend-message

Export all suspended messages

$array = @(Get-Message -Queue "ExchangeServer\submission" -ResultSize unlimited) 
$array | ForEach-Object {$i++;Export-Message $_.Identity | AssembleMessage -Path ("c:\Mailqueue\"+ $i +".eml")}



Stop the MsexchangeTransport service

Stop-Service MsExchangeTransport

Now rename the queue directory, the default directory is


Startthe MsexchangeTransport service

Start-Service MsExchangeTransport

Solved : All Exchange 2010 services disabled after update

Today I ran into a problem after updating Exchange 2010. After a reboot (which took ages!) I noticed that all the services were disabled. After some troubleshooting I found out that the problem had something to do with an installed update. My resolution (and was planned) was to install the latest servicepack (SP3). There is one drawback, the services are disabled and Exchange SP3 setup is unable to stop/start them.

I used this powershell command to set the service to manual :

Get-Service MSEx* | Set-Service -Startuptype manual

During the install I had to execute this command 2 times, the SP3 setup worked fine and after that the services were automatically started.