Ah yes, thanks for the refresher. I do remember this, now that you mention it. 
Something I read yesterday made me believe I had to get AD sync working with 
O365 for this to work. But of course now I can’t locate the article. It also 
goes to show that you shouldn’t believe everything you read on the internet ☺

The other option I really wanted to allow them was password sync, this more 
than anything was most important. But I guess that’ll just have to wait until 
next year when we replace the server.

So I guess at this point I’m going to switch gears and just do a cutover 
migration instead of staged. I see no reason not to.

Thank you.


From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On 
Behalf Of Bertrand ELLEN-PREVOT
Sent: Friday, April 8, 2016 1: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

Reply via email to