1 / 34

Move From Exchange 2007 to Modern Exchange

BRK2218. Move From Exchange 2007 to Modern Exchange. Steve Conn – Senior Product Marketing Manager, Exchange Greg Taylor – Principal Program Manager, Exchange. Non-zero population of customers on Exchange 2007 “It’s still running…and email is email, right?”

marisol
Download Presentation

Move From Exchange 2007 to Modern Exchange

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BRK2218 Move From Exchange 2007 to Modern Exchange Steve Conn – Senior Product Marketing Manager, Exchange Greg Taylor – Principal Program Manager, Exchange

  2. Non-zero population of customers on Exchange 2007 “It’s still running…and email is email, right?” Exchange 2007 has been in Extended Support since 2012: thus, no new features for 4 ½ years In April 2017, Extended Support ends: thus, no security fixes, no bug fixes, no timezone fixes “Exchange 2007 won’t stop working in April, so why not keep using it?” Why are we here?

  3. Travel back in time to 2007 • Concepts introduced in Exchange 2007 that have proven out well • 64-bit hardware only – reduced I/O throughput; larger DBs • Edge Server role – reduced attack footprint in the DMZ • AutoDiscover – no more cryptic server URLs to set up access from devices • Resource mailboxes – no reconfiguring a user mailbox for room bookings • Message retention policy – manage preservation, auto-aging out • LCR/CCR/SCR – discrete high availability improvements • OOF versions – separate internal and external Out of Facility messages • But we’ve done some work since then – enhancing those features, and introducing others.

  4. Exchange 2010 introduced For the IT Pro: Store schema and ESE changes reduced IOPS by 70% Role Based Access Control (RBAC) – define permissions without modifying ACLs OWA mailbox policies – define user policies without modifying IIS vDirs Control mailbox access by mobile device types – allow/block/quarantine Support for hybrid connectivity to Exchange Online JBOD recommended over RAID – less cost and complexity for storage

  5. Exchange 2010 introduced For the end user: Federated delegation - share free/busy, share/delegate calendar between organizations MailTips – guidance for end users on missing subject lines, etc. (don’t send that email!) Support for conversation view in Outlook Web App Ability to view message reply status on Exchange ActiveSync devices OK, not much more here

  6. Exchange 2013 introduced For the IT Pro: Reduced server roles to 3: less complexity, better hardware utilization Session affinity between CAS and MBX not needed – easier load balancing New Public Folder architecture based on mailbox – support for DAGs, etc MAPI over HTTP instead of MAPI over RPC – improved connectivity to Outlook Reduction from 8 to 2 namespaces – client protocols and Autodiscover All or nothing hold changes to in place hold - query-based or time-based hold Data loss prevention – keep sensitive info from leaking via policy High availability enhancements – Managed Store (improved resiliency); Auto Reseed (DBs from failed disk to spare disk); lagged copies (automatic log playdown in low disk space scenarios)

  7. Exchange 2013 introduced For the end user: OWA optimized for more devices – tablets, smartphones along with PCs, laptops OWA support for add-ins (apps) – similar to add-ins for Outlook for desktop OWA support for contact linking – e.g. link user from GAL and from Contacts OWA support for merged view of multiple calendars Add-ins can work in compose (new message), not just in the body of a received email

  8. Exchange 2016 introduced For the IT Pro and the end user: Nothing…Exchange 2016 is exactly the same as Exchange 2013 JUST KIDDING!

  9. Exchange 2016 introduced For the IT Pro: Reduced server roles to 2: less complexity, better hardware utilization PF Mailboxes go from 100 > 1,000 – more ability to place data in remote offices 2016 MBX support 2013 CAS – seamless interop for upgrades, migration In-Place eDiscovery/Hold for public folders – easier, more complete compliance 10,000 > Unlimited number of mailboxes in a single In-Place eDiscovery search 30 new DLP data types – more pre-configured “fingerprints” to choose from DLP integration w/ SharePoint – emails where “Cloudy doc” contains condition Reduced bandwidth needs between active and passive DB copies DB divergence detection, loose truncation – automatically detect DB corruptions

  10. Exchange 2016 introduced For the end user: Document collaboration – automatically send a link instead of an attachment URL preview/video preview/inline playback – keep content “in” the conversation REST APIs – simple, uniform, programmatic access to email/calendar/contact info Improved integration with Skype for Business calls, meetings, IMs Improved search from Outlook – now server-powered Events from email – add to calendar

  11. Exchange Online introduced For the end user: Focused Inbox for all Outlook apps Zero-day Autopurge (time travel) REST APIs – simple, uniform, programmatic access to email/calendar/contact info Delve/Delve Analytics – fitness tracker for your business Office 365 Groups – Distribution Lists++ @mentions and Likes in email Safety tips for suspicious email

  12. Modern Exchange Demo

  13. So What if I Don’t Care About Those Things? • There are plenty of other reasons for getting up to date • Security and time-zone fixes • Compatibility with newer devices and apps • Outlook 2016 won’t connect to Exchange 2007 • Modern browser incompatibilities – most won’t work with OWA 2007 • (MUCH) Better compliance capabilities • Less prone to failure and easier to recover • The hardware won’t run forever (even if it’s virtual you’d have to keep moving it around)

  14. So Is Moving Off 2007 Hard? • Migration to Exchange has never been what you might call ‘easy’ but it has become ‘easier’ • You really have two choices at this stage • Stay on-premises • Or go to the cloud • Let’s start with cloud

  15. Why Start With the Cloud? • Because if you are on 2007 today you have other things to worry about, more important than email • And if you upgrade on-prem there’s a good chance we’ll see you at the ‘So, you’re still running Exchange 2016?’ session in 10 years from now…. • You can do it in a single jump – from old software to the very latest and then you stay there • So what are your choices for getting to the cloud?

  16. From Exchange 2007 to Infinity… and Beyond! • If you want to stop being On-Prem you can do a Cutover or a Staged Migration • If you want to keep some mailboxes On-Prem you can install Exchange 2010/13 and go Hybrid • Or you could use a 3rd party tool and/or hire a partner • And you can import PST’s • https://support.office.com/en-us/article/Ways-to-migrate-multiple-email-accounts-to-Office-365-0a4913fe-60fb-498f-9155-a86516418842?ui=en-US&rs=en-US&ad=US • And we can even do most of it for you……

  17. Which Do I Choose? Cutover or Staged? • A Cutover Migration is the best bet for organizations with <150 seats and who want to migrate over a couple of days • Source can be Exchange 2003/7/10/13 • Goal is to move user accounts and mailboxes to O365 and remove Exchange On-Prem • Outlook Anywhere is used to suck the accounts and data from your On-Prem org • A Staged Migration is best for organizations with >150 seats and who want to migrate over more than a couple of days • Source can be Exchange 2003 or 2007 only (if you have 2010/3 consider Cutover or Hybrid) • Requires you perform Directory sync from On-Prem AD to O365 (you can sync passwords) • Uses Outlook Anywhere to extract data and then match it to accounts sync’d to the cloud • The admin then converts mailboxes on-prem to Mail-Enabled Users On-Prem

  18. Cutover vs Staged Migrations

  19. A Bit About Hybrid • Hybrid gives you the richest feature set and collaborative experience • Provides secure mail routing • A unified GAL • Cross-Prem Free/Busy • Single OWA URL • And more.. So go see the Hybrid Session - Migrate to Exchange Online via Exchange Hybrid – Wednesday 2:15 – 3:3pm – Thomas Murphy Ballroom 2 & 3 • Requires Exchange 2010 or 2013 be in your 2007 Org • You need to add a 2010 or 2013 server to enable the Hybrid configuration • So if you have only 2007 today, what do you do? • If you can’t do Cutover or Staged, add 2013 and configure Hybrid

  20. 3rd Party Solutions and Partners • If the idea of doing this is scary, or too hard, hire a partner or use a tool! • Walk around the Expo floor and you’ll find them there! Use a third-party email migration tool Migration tools can help speed up and simplify email migration. You'll find a list of tools in the Office 365 Marketplace. Hire a partner to help migrate your email You'll find a list of partners in the Office 365 Marketplace.

  21. O365 Import Service • There are two ways to import PST files and SharePoint data to Office 365 • Network upload • You upload your data files over the network to a temporary storage location in the Microsoft cloud. Then you use the Office 365 Import service to import the data to mailboxes or sites in your Office 365 organization. • Drive shipping • You copy the data files to a BitLocker-encrypted hard drive and then physically ship the drive to Microsoft. When Microsoft receives the hard drive, we upload the data to a temporary storage location in the Microsoft cloud. Then you use the Office 365 Import service to import the data to mailboxes or sites in your Office 365 organization. Drive shipping is a good way to import data to OneDrive for Business sites. • Cost • Network upload – free • Drive Shipping - $2 USD per GB of data

  22. And What About FastTrack? • The Onboarding and Adoption Assistance is available for 50 seats or more while the migrations assistance is for 150 seats or more. • Refer to FastTrack Center Benefit for Office 365 for details on eligible Office 365 plans and available FastTrack Center service details.

  23. What About My Public Folders/Other C**p? • You can move your PF’s to the cloud but that’s largely on you (FT won’t do that but partners might) • But this might also be a great time to ditch those things and start new • Apps you have integrated might have newer versions, or could be re-written for EWS/REST • You might want to keep an Exchange box on-prem for SMTP enabled scanners and to manage identities/mailbox creation

  24. Any Other Words of Advice • Super Important - Keep your clients updated because then AutoDiscover and other things will ‘just work’ • Don’t let an automagic upgrade to Office 2016 break connectivity to Exchange • Security ‘Policy’ – now’s a great time to understand if the policy you have is based on the technology you have today, not the world you live in • Think of your role as administering a service rather than a server – you are still very necessary

  25. What If You Want to Stay On-Prem • Well you can’t 

  26. But What Choices Do You Have If You Must • You can add 2013 to your 2007 Org (Update 2007 to the latest SP/Roll-Up) • You need to consider namespaces, certificates and down level proxy • Once you have that in place all users start by hitting the newest version of Exchange, and are redirected/proxied as necessary • Then you move mailboxes • Try and move users who are connected (manager/delegate for example) together • Mailbox Moves are Online – no interruption of service • Once done you can move Public Folders • Though if you intend to move to the cloud (why didn’t you just do it?) then perhaps leave them on 2007/10 and not move to Modern PF’s as you cannot current migrate modern PF’s to the cloud (though we are working on adding support for that)

  27. So What Would a Move to 2010 look like? • Nothing, it would look like nothing as you would be mad to do it…

  28. So What Happens Once You Get to 2013 • Then, you move to 2016 asap • The delta between 2013 and 2016 is small • You can add 2016 mailbox servers and not even change the CAS/Front End configuration • Then you can move mailboxes to 2016 • You can add 2016 to the load balancer and switch over gradually (or all at once) • And then you’re on 2016.

  29. Any Last Words of Advice • Keep your clients updated because then AutoD and other things will just work • Follow our general guidance • Use the Exchange Deployment Assistant to help you along the way • Review the latest sizing guidance as there are clear recommendations around sizing (and not over-sizing) • Stick to the Preferred Architecture

  30. Summary • Cloud or On-Prem is Your Choice but if the reason you are still on 2007 is because you don’t have time or the inclination, then go to the cloud

  31. Deploy, ramp-up on new services and onboard new users with Microsoft FastTrack:http://fasttrack.microsoft.com/

  32. Join the Microsoft Tech Community to collaborate, share, and learn from the experts:http://techcommunity.microsoft.com

  33. Please evaluate this session Your feedback is important to us! From your PC or Tablet visit MyIgnite at http://myignite.microsoft.com From your phone download and use the Ignite Mobile App by scanning the QR code above or visiting https://aka.ms/ignite.mobileapp

More Related