I have not done a staged migration, only cutover migrations with SBS 2008 and 2011. I don't see a reason for you to do a cutover with SBS 2008. How many users are you talking about?
And as was mentioned, what version of Office/Outlook are the users using? I have not seen any duplicate messages from doing the cutover migration multiple times. I think it runs once every 24 hours to keep messages in sync after initial run. You can see the current status by looking at the migration. The initial migration time depends on the amount of email and you Internet connection upload speed. I usually start the migration Wednesday evening, check it for any errors and fix them if any, then on Friday evening I switch the MX records. Monday I check that everyone is getting email from Office 365 and if nothing has come into the on premise Exchange server it gets shut down Monday evening and then the server is rebooted to allocate resources. Actually it's been pretty easy and painless. But then again, it's all in the planning. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Neil Standley Sent: Friday, April 8, 2016 3:18 PM To: [email protected] Subject: SPAM RE: [NTSysADM] RE: Azure Active Directory Connect Ha! That's the article right there. Does this only apply to auto-complete or suggested contacts that are in AD? If so it's not a big deal, we're only talking about a few users here and we could recreate those entries without any hassle. Do you happen to know if runing the migration batch from O365 will generate duplicate messages in the user's mailbox? I'm asking because the instructions indicate you should allow the batch migration to complete before changing the MX record for the domain. Which means you may have new messages arrive at the on-premise Exchange server, and if you can't run the batch migration again the you'd end up losing new mail. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Susan Bradley Sent: Friday, April 8, 2016 1:29 PM To: [email protected] Subject: Re: [NTSysADM] RE: Azure Active Directory Connect Essentials has a sync up with Office 365 that syncs the passwords with the 365. It's not ad connect but if you are going to Essentials, it would be the road I'd go. http://blog.powerbiz.net.au/sbs-2008/migrating-email-from-sbs-exchange-to-office-365/ One main drawback from using any method that does not synchronize the Office 365 platform to your existing Active Directory is dealing with the issue of Auto-Complete or Suggested Contacts. After the migration, it is quite likely that replies on old emails or emails sent using the stored contact information in Auto-Complete or Suggested Contacts will result in a Undeliverable error as follows: IMCEAEX-_O=MyDomain_OU=First+20Administrative+20Group_cn=Recipients_cn=boldlastn...@domain.com #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ## Read the rest of the post and I think that there are ways around your issue On 4/8/2016 1:09 PM, Neil Standley wrote: > Replacing the server was one option I pitched but funds are an issue so we'd > just planned to migrate to O365 and move them to Essentials 201x next year. > > So your suggestion is to put up a temp server, complete the migration and > remove Exchange, then install WMF4 on to the old SBS machine? > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Susan Bradley > Sent: Friday, April 8, 2016 12:43 PM > To: [email protected] > Subject: Re: [NTSysADM] RE: Azure Active Directory Connect > > Stand up a temp server. Use an eval of something. I'm assuming you'll be > getting rid of the SBS 2008? > > > > On 4/8/2016 12:26 PM, Neil Standley wrote: >> 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 >> > > > > >
