Hi,
I have used MigrationWiz before but found CodeTwo Office365 Migration to be excellent too, I could tune the migration to use as many threads that were reliable, could pause migration and resume when needed without having to resend everything that had already been moved. Product was worth the money vs the amount of mucking around it takes via other means and has an excellent interface to show you exactly what’s happening an where you are up to. Kind Regards, Jim. From: AusNOG <ausnog-boun...@lists.ausnog.net> On Behalf Of Michael Keating Sent: Tuesday, 19 June 2018 11:58 AM To: Bill <b...@wjw.nz> Cc: ausnog@lists.ausnog.net Subject: Re: [AusNOG] [AUSNOG] o365 experience I'll also praise MigrationWiz, it's a fantastic product with a lot more features than a few years ago (think profile migration client that you can deploy to endpoints). Exchange Online is very stable, not like the days of what felt like endless downtime. Like everything, you learn the ins and outs through experience, and it really depends on your deployment model. Using ADSync? Hybrid? Windows Server Essentials deployment? Standalone? The compliance and security settings are very comprehensive, and management though Exchange Online Powershell is a must. Just while rate-limiting is mentioned, users that access a number of other users mailboxes will have a poor experience when adding mailbox permissions through ECP (automapping) in cached mode. You will want to disable automapping by granting the permission through Exchange Online Powershell and disabling auto-mapping, and adding the account manually in the end-users mailbox. This does change the end user experience, but in practice getting the whole mailbox cached and not have Outlook freeze far outweighs the quirks it brings. Regards, Michael Keating On Tue, Jun 19, 2018 at 11:46 AM, Bill <b...@wjw.nz <mailto:b...@wjw.nz> > wrote: We used a product called MigrationWiz to migrate our 7000 users. The only issue with using a product like that is the rate limit into the tenant. However you can request MS turn it off for a period of time. We’ve been running with Exchange Online since 2013. There have been occasional network issues, but they are usually short in duration and exacerbated by us being a global organisation with our tenant based in North Central US. Sent from my iPhone On 19/06/2018, at 1:04 PM, Paul Wilkins <paulwilkins...@gmail.com <mailto:paulwilkins...@gmail.com> > wrote: I'd be interested to hear general opinions and lessons learned from o365 migrations. So far as I've seen, the architecture (network and services) is complex, and user experience can never equal local Exchange. So much so it leaves me wondering if the effort of migration can be justified? At the end of the day, you need a performant service, not finger pointing between networks and services, and blaming performance on insufficient network/proxy scale out. Kind Regards Paul Wilkins -- This message has been scanned for viruses and dangerous content by <http://www.efa-project.org> E.F.A. Project, and is believed to be clean. Click here to report this message as spam. <http://mail.wjw.co.nz/cgi-bin/learn-msg.cgi?id=97FAAC00C4.A2F98&token=693f7dd93f1784489182abc5f3252e49> _______________________________________________ AusNOG mailing list AusNOG@lists.ausnog.net <mailto:AusNOG@lists.ausnog.net> http://lists.ausnog.net/mailman/listinfo/ausnog _______________________________________________ AusNOG mailing list AusNOG@lists.ausnog.net <mailto:AusNOG@lists.ausnog.net> http://lists.ausnog.net/mailman/listinfo/ausnog
_______________________________________________ AusNOG mailing list AusNOG@lists.ausnog.net http://lists.ausnog.net/mailman/listinfo/ausnog
