<div dir="ltr">"<span style="text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">user experience can never equal local Exchange.</span>"<div><br></div><div>The cached mode Outlook client comes VERY close.</div><div><br></div><div>Stop treating email as an instant messaging service or calendar as if it updates immediately, and it works perfectly fine.</div><div><br></div><div>I reckon I can count on one hand the number of situations where running your own Exchange server on-premises is worth doing over cloud-hosted collaboration.</div><div><br></div><div>Not that any of this belongs on AusNOG I suspect...</div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, 19 Jun 2018 at 11:04, Paul Wilkins <<a href="mailto:paulwilkins369@gmail.com">paulwilkins369@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>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. </div><div><br></div><div>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.<br></div><div><br></div><div>Kind Regards</div><div><br></div><div>Paul Wilkins<br></div></div>
_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net" target="_blank">AusNOG@lists.ausnog.net</a><br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" rel="noreferrer" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</blockquote></div>