It brings the legacy Exchange DNs over as X500 proxies which is what the auto complete entries use for internal users/groups/etc. You could just export these (and any other X500 proxies from the GAL) and import them manually in to Exchange Online if that’s the only thing that AAD Connect was going to bring.
Thanks, Brian Desmond w – 312.625.1438 | c – 312.731.3132 From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On Behalf Of Bertrand ELLEN-PREVOT Sent: Friday, April 8, 2016 3:36 PM To: ntsys...@lists.myitforum.com Subject: Re: [NTSysADM] RE: Azure Active Directory Connect >>suggested contacts and auto complete [...] you need to have directory sync >>working not sure why dir sync should be involved if you're talking about migrating the emails only (and calendars and contacts). Dirsync (talking to Active Directory) should not be involved unless I'm missing something... When connected to an exchange account, finding and migrating suggested contacts and autocomplete depend on the version of Outlook you're using. Outlook 2007 : these are located in a .NK2 file. find previous nk2 file then import it on your new Outlook profile Outlook 2010 & up : they are in a hidden message on the server. Do a "standard" exchange 2007 to O365 migration, the process will connect to the on-premise exchange server and migrate everuthing in the inblox + calendar + contacts (including autocomplete/suggested). http://blog.powerbiz.net.au/sbs-2008/migrating-email-from-sbs-exchange-to-office-365/ Hope that helps, Best Bertrand ELLEN-PREVOT bertr...@izitech.ca<mailto:bertr...@izitech.ca> 2016-04-08 15:26 GMT-04:00 Neil Standley <standl...@cascadiainfotek.com<mailto:standl...@cascadiainfotek.com>>: Hi all, I’m working on a staged SBS 2008/Exchange 07 SP3 to O365 migration for a customer. I’ve read that in order for suggested contacts and auto complete to work after the migration you need to have directory sync working. So we’d like to be able to sync their onsite AD with the cloud but am running in to problems getting Azure Active Directory Connect installed. It wants Windows Management framework 4 installed, with powershell 3, but I’m reading that WMF is not recommended on SBS or Exchange previous to Exchange 2013, where it’s a requirement. So my question, what do I do now? SBS is the only server in the environment and I don’t think it would be wise to run the sync tool from a workstation, not that they have a spare anyways. After the migration I am planning to remove Exchange, but not immediately, I’d like to wait about 30 days to make sure everything is working properly. So should I install the WMF4 and ignore the warnings, or are there other options I don’t know about? Thanks, Neil
