activateahsd
asked on
Dirsync setup
Hi,
We have a Server 2003 domain running Exchange 2003, I also have a server 2008 r2 member server. We have purchased an Office 365 subscription to replace the in-house Exchange.
I have been reading up on dirsync and want to use it to keep the domain and O365 login details in sync. My questions are:
1. can i install dirsync and use it to populate the O365 environment with all the users in advance of the cut over to O365 for email delivery, i.e with internal Exchange still running?
2. i know i have to create an OU in AD to put all the existing AD users in that will have O365 accounts, do I also need to add a UPN name in AD, is this the 'user logon name (pre windows 2000)' if so does this name need to be the same as the email address in O365?
Thanks
Andrew
We have a Server 2003 domain running Exchange 2003, I also have a server 2008 r2 member server. We have purchased an Office 365 subscription to replace the in-house Exchange.
I have been reading up on dirsync and want to use it to keep the domain and O365 login details in sync. My questions are:
1. can i install dirsync and use it to populate the O365 environment with all the users in advance of the cut over to O365 for email delivery, i.e with internal Exchange still running?
2. i know i have to create an OU in AD to put all the existing AD users in that will have O365 accounts, do I also need to add a UPN name in AD, is this the 'user logon name (pre windows 2000)' if so does this name need to be the same as the email address in O365?
Thanks
Andrew
ASKER
Hi, Thanks for the info, really useful.
I think I have got my terminology wrong, as per the microsoft definition I am not doing a 'cut-over' migration. There are only 22 users and they want blank new mailboxes with historical email only available as a locally storted pst file.
So I think what I need to do is manually create the 22 users in O365, then alter the MX records so email starts flowing via O365 rather than internal Exchange. At that point I guess I need to amend the users AD logins to be the new UPN which matches their O365 login (and their primary email address). Once that it done I can install dirsync to keep AD password changes in sync with O365 credentials.
Have I understood it right?
Thanks
Andrew
I think I have got my terminology wrong, as per the microsoft definition I am not doing a 'cut-over' migration. There are only 22 users and they want blank new mailboxes with historical email only available as a locally storted pst file.
So I think what I need to do is manually create the 22 users in O365, then alter the MX records so email starts flowing via O365 rather than internal Exchange. At that point I guess I need to amend the users AD logins to be the new UPN which matches their O365 login (and their primary email address). Once that it done I can install dirsync to keep AD password changes in sync with O365 credentials.
Have I understood it right?
Thanks
Andrew
Go with staged migration instead, you can have dirsync running from the start with it:
http://help.outlook.com/en-us/140/ff959224.aspx
You will need a valid CA certificate for Outlook Anywhere, if you don't have such you can get one for free from comodo or startssl.com.
Doing things manually will also work, but will probably get you into more issues. Just update the UPNs first, set up dirsync and proceed with the migration. Once you read the articles it's not that complicated :)
http://help.outlook.com/en-us/140/ff959224.aspx
You will need a valid CA certificate for Outlook Anywhere, if you don't have such you can get one for free from comodo or startssl.com.
Doing things manually will also work, but will probably get you into more issues. Just update the UPNs first, set up dirsync and proceed with the migration. Once you read the articles it's not that complicated :)
ASKER
Hi - they dont want to import anything to the new mailboxes. Can I install dirsync after everything is up and running just to keep password changes synced?
OK, the idea behind all those methods is to migrate not only the account (and their corresponding attributes), but also the mailbox data associated with them. If you are NOT going to migrate any mail, all you need is dirsync.
Sorry if I have misunderstood you :)
Just to make sure you have displayName set for any groups you want to migrate, otherwise the dirsync process will just skip them.
Sorry if I have misunderstood you :)
Just to make sure you have displayName set for any groups you want to migrate, otherwise the dirsync process will just skip them.
ASKER
Hi, your being very helpful thank you.
Sorry if I am asking dumb questions, I have moved all my required users into a new OU in AD in preparation, when you mention displayname are you talking about the users 'simple display name' in Exchange?
Sorry if I am asking dumb questions, I have moved all my required users into a new OU in AD in preparation, when you mention displayname are you talking about the users 'simple display name' in Exchange?
No, the actual displayName attribute.
ASKER
sorry but where do i find that?
thanks.
thanks.
Oh, 2003 domain? Use adsiedit.msc :)
Couldn't find a nice guide with screenshots and all, so here's a link to a similar question on EE: https://www.experts-exchange.com/questions/27462346/Change-'displayName'-attribute-with-ADSI-Edit.html
Couldn't find a nice guide with screenshots and all, so here's a link to a similar question on EE: https://www.experts-exchange.com/questions/27462346/Change-'displayName'-attribute-with-ADSI-Edit.html
ASKER
of course, thanks!
So its the OU group I have to set the displayName attribute on? Does it have to be anything in particular?
Thanks.
So its the OU group I have to set the displayName attribute on? Does it have to be anything in particular?
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK thanks for all your help, really useful knowledge for my first O365 setup!
cheers
Andrew
cheers
Andrew
ASKER
Really good expert!
2) If you are going to use a custom domain with Office 365, make sure you add this domain as UPN suffix in your AD. Then, change the UPNs of every user you are going to migrate to the cloud to match the new UPN suffix. The UPN and primary email address do not need to match.
Here is the article on cutover migration just in case:
http://help.outlook.com/en-us/140/Ff628719.aspx
Compare different types of migration:
http://help.outlook.com/en-us/140/538c48ad-4a3d-4777-be1b-7fc533ca45eb#migrationmatrix