365 Migration first steps

[petben]

I am just starting to test an Office365 migration from Exchange 2010 sp3. I have got some A2 licenses, an onmicrosoft.com domain and verified our school domain. I have also setup some test users within 365 but this is a bit pointless as it needs to be AD linked. Can someone please advise what I should do next, can I go ahead and set up ADFS and Dirsync on a VM, and then actually migrate a few test mailboxes from the network? Does it work like that? Has anyone any step-by-step links or can guide me on the order things need completing in.

 

I also have a .local internal domain and a .com external. what are the implications? 'the internet' gives many differing opinions regarding certificates and the need for domain\username logon.

 

Thanks

[mikkydoos]

I presume your .com domain is just for your website/mail etc not for remote desktops/Exchange etc.

 

If it is for external access just be careful of getting your DNS right.

 

 

1. Set up DNS with your hosting provider and verify in O365. I'd set up a CNAME record with your hosts so your O365 tennant is pointed to from (something like) mail.mydomain.com.

 

2. You can run DirSync at any time. Users aren't assigned an email account until you assign a license to their user account/mailbox. Beware if you're doing this and you're using Exchange, likewise with changing DNS on your domain name. You're Exchange box will stop routing mail. The thing to do is go into their AD object, properties and make sure in the email field your desired email address is present.. then go the Attribute Editor and add a Proxy Address with their old email address. This will catch mail addressed to their old account as long as you have both domains set up in O365. This applies if the naming convention is changing e.g. R.Smith@xxx to Robert.Smith@xxx. Check the convention for SMTP: and smtp:

 

3. When you're ready to swap, run DirSync again (use powershell, not the Dirsync app - Microsoft advised me of this), set up your distribution lists, shared calendars, sharepoint, then license your users with whatever you want them to access.

 

4. You'll need to sync their old mail account (if you've changed from another domain name) with their new one so they've still got their mail. Either do this with IMAP (an lengthy admin pain) or sync with your Exchange box if you have one.

 

Not a lot else you need to do except maybe train your staff a bit.

 

(A hybrid DirSync deployment between my Exchange and O365 destroyed my domain controllers and a full rebuild had to be done. I'm still miffed!)

Edited October 17, 2014 by mikkydoos

[petben]

Thanks, I thought ADFS synced the accounts and dir sync the passwords. I was thinking I needed a dedicated ADFS Virtual server?

[mikkydoos]

No DirSync does the lot. Turn it on in O365, run DirSync, then it should sync about every 3 hours Edited October 17, 2014 by mikkydoos

[petben]

do you think a dedicated dirsync (virtual) server is necessary? I do like splitting roles but then MS say it could just go on an DC...

[mikkydoos]

No. Not at all. All its doing is uploading bits of your AD database to the cloud. For 200 user accounts, mine takes about 5mins.

 

I do mine off my DC. I think you can do it on a workstation even. Can't rightly remember.

 

Keep it simple, bung it on your DC

[jamesbmarshall]

Keep it simple, bung it on your DC

 

Just keep in mind that it can be a memory hog; if you have lots of users/changes etc. then it's best to keep it on a separate machine.