1

I currently have an on-premise SBS 2011 (Exchange 2010) server and I’m moving to 365… Only 16 mailboxes and database is around 50gb…

Don’t want to do federation but I do want to push / sync AD passwords (via DirSync)…

Over the past weekend I added and verified the domain in 365 and installed DirSync (following this guide ) on a member server… I successfully synced the AD and assigned licenses to the 365 users…

I made the MX record changes and verified those as well…

I went to test with a user and when I logged into the portal site it logged in correctly with the AD password but when I clicked on Outlook it got an error…

After a call to Microsoft they told me the reason why was because it was pointing to my on premise Exchange server? I don’t understand that but all my AD users did not get mailboxes created…

They then had me change my MX records back and told me to follow the steps for a cusover migration… Problem with that is, it doesn’t mention when to install / use the DirSync piece…

So bottom line is… I want to get my mailboxes to 365 and use DirSync to have same passwords for both AD and 365… I can simply export the PSTs and manually upload them but if that isn’t recommended I need to know what I should do here…

Thanks

3 Spice ups
2

Have you actually done the migration?

Have you used https://testconnectivity.microsoft.com/ to check if your RPC over http is configured properly on your Exchange server?

All i have seen is the following

  1. verified your domain

  2. Installed Directory sync

  3. Changed MX record

Lots of things that needs doing before changing the MX record to Office365.

3

Sorry… Should have been more specific… I’m sort of asking a question and providing a test case that doens’t match up to the question, apologies…

So I guess I have two questions…

  1. Disregard the above scenario… If I follow the Cutover migration (excellent video here: http://www.youtube.com/watch?v=tNYbE5oS4gE ) at what point does DirSync come into play?

  2. In regards to the above scenario… It was only 16 users so my plan was actually to just export all mailboxes to PSTs (Outlook anywhere wasn’t configured, no cert, etc), create the mailboxes on 365, and then upload the PSTs… Then I came across the latest version of DirSync which talked about syncing passwords without ADFS and I wanted to try that but had issues…

4

  1. Dirsync will only copy the AD accounts and password to office365. It wont migrate the mailboxes at all.

  2. what error message is displayed in outlook? while assigning the license the license,did you get a warning that the user;s account mailbox has not been migrated yet?

1 Spice up
5

  1. So if I follow the cutover migration guide and at the end I’m supposed to install DirSync and it will match the passwords to the accounts that were created during the cutover migration?

  2. The issue was the mailboxes were NOT created… My steps for this were just to install DirSync, it brought over my AD, I assigned the users licenses and thought I was good to go… Turns out the mailboxes didn’t get created on the 365 side… Microsoft said it was because there was an on premise mailbox that already existed… I didn’t understand this since it’s completely separate, not ADFS, etc…

6

i think you are on the correct path.The only issue i see here is the mailboxes are still onsite.I have had this sort of issue before but i will suggest you create a test account to try this first before using real accounts

I will advise you to do the following

  1. create another exchange account on premises as a test. send some test message to the mailbox

  2. all dirsync to synchronise it to office 365 and assign a license to it

  3. Go into the newly created account and export the e-mails.

  4. Delete just the exchange features from the test users on your active directory

  5. Give it a few minutes and then try logging into the account on office365

That should work. Also have you configured outlook autodiscover?