In the image above I ran into an issue when trying to create an admin pool for on Quest Notes For Exchange migration toolkit.This was for a migration to Exchange Online.

So the first thing i did was set-executionpolicy unrestricted -force on both the x64 and x32 versions of powershell. But that didn’t fix the issue.

Most enterprises have quite a few group policies and sometimes these policies are applied before the machines have been moved to an OU that has inheritance blocked.

So to remove the group policies causing the issue. 

In this post I just wanted to highlight what active directory attributes need to change on a user account when you have an existing Exchange Hybrid and want to migrate Lotus Domino users into exchange online.

Primary Email Address: Sean@contoso.com
Hybrid email Domain: contoso.mail.microsoft.com

The existing users that have exchange mailboxes will already have exchange active directory attributes. So lets take a look at what happens when you migrate an on premise exchange mailbox to exchange online.

When you run dirsync , a proxy hybrid domain is created in the example above it is contoso.mail.microsoft.com. So when you initiate a ‘new remote move request‘ and move an onprem user to the cloud the user becomes a mail contact and their routing email address becomes

1. We set the user’s location , in this example the country is US
   Get-MsolUser -UnlicensedUsersOnly |Set-MsolUser -UsageLocation US
2. Get-MsolUser -UnlicensedUsersOnly | Set-MsolUserLicense -AddLicenses “Contoso.com”:EXCHANGESTANDARD

I previously blogged HERE about the Microsoft Outlook Connectivity Analyzer 2.0 which has now been replaced by the Microsoft Office Configuration Analyzer Tool 1.0 which you can download HERE

This tool can be really useful when troubleshooting connectivity issues like firewalls and proxies blocking access to Office365.

When using DirSync and ADFS it can take a long time to activate thousands of users. So here is a really quick way of doing it.

Firstly HERE is a great article on msexchangeguru.com on dirsync filtering. So there are plenty of organisational units in Active Directory that do not need to be syncronised to Office365.

So I always filter the OU’s that are synchronized to Office365.

Within the organisation section of the Office365 portal make your external domain which has been verified the default domain.

Ensure all user’s have the correct User Principal Names as per one of my previous BLOGS 

So once all the user’s have been synced to Office365 , they need a license assigned to them.

So connect to Office365 via the Windows Active Directory Module for Windows Powershell and do the following.

connect-msolservice # and enter an Office365 Global Administrator’s credentials.

As all of the users are currently unlicensed , we will set a location for the users as per the command below and the location will be us.

The upgrade from DPM2012 to DPM2012 SP1 RU1 is quite simple or so I thought!

1. In order to install SP1  for dpm2012 rollup3 is a pre-requisite which you can download HERE
2. However I could not get Rollup 3 to install as it kept failing on execute sql strings section.
3. Open a command prompt with elevated privileges and make this the current directory “C:\Program Files\Microsoft System Center 2012\DPM\DPM\bin” and then run this command dpmbackup -db. This will place a backup of the dpm database in the following folder C:\Program Files\Microsoft System Center 2012\DPM\DPM\Volumes\ShadowCopy\Database Backups
4. So once we have done a backup , the trick is to set the options on the DPM database to single user mode as per the image below.So once this is done. You can install Rollup 3.

1. I would then still leave it in single user mode when installing DPM 2012 SP1
2. You may get an error with id:820 when DPM2012 begins the upgrade to SP1. HERE is a description on how to fix it. HERE is also a great post about WMI Service errors
3. You may also get an error 812 stating that reporting services cannot be configured. So to fix this there are a few steps.

   Firstly run this command ‘netsh http show urlacl’ and copy all the http urls on port 80.
   So in my case I deleted the following urls with the following cmmands

   netsh http delete urlacl http://+:80/Temporary_Listen_Addresses/
   netsh http delete urlacl http://+:80/ReportServer_MSDPM2012/
   netsh http delete urlacl http://+:80/Reports_MSDPM2012/

   Then open up SQL 2008R2 / Reporting Services Configuration Manager and connect to the dpm2012 instance. Within the web services url section click apply. Then you can re-run setup and no more error 812

4. Then after SP1 has been installed , you need to install ROLLUP1 for DPM 2012 SP1
5. Finally you can then re-enable multi-user mode on the database and login to DPM2012 SP1 RU1 🙂
6. Final version number will display as per the image below. Version 4.1.3322.0

I recently came across the error in the image above when trying to move mailboxes from an on-premise hybrid server to Office365.

Why would this happen? 

Configure your hybrid servers before you configure dirsync. During the hybrid configuration wizard , the wizard creates a sub domain  ‘domain.mail.onmicrosoft.com’ 

Now that the target delivery domain has been created by the Hybrid Wizard, We can run the DirSync configuration wizard. Select enable ‘hybrid configuration’  so once the wizard can see the target delivery domain it will add the smtp:email@domain.mail.onmicrosoft.com to the proxyaddress attribute in Active Directory for each user account.

So now when you try to run a remote move request, it will complete without issue.