University Of Oregon Campus Exchange 2010 Briefing

1. University Of OregonCampus Exchange 2010 Briefing Fall 2011

2. Meeting Agenda • Outcomes • Exchange 2010 Timeline Update • Design Overview • Demonstrate functionality • Discuss administrative responsibilities • Migration • pre-requisites • steps • Next steps for IT Units

3. Timeline Update You Are Here July 2009-Present August 2010- December 2010 January 2011 – June 2011 July 2011-September 2011 October 2011-December 2011

4. Design Overview • Design Objectives • Multi-site high availability • Consolidated management • IDM Integration • Distributed Administration • Distributed Support

5. Hardware

8. Mailbox Database Layout

9. Storage Performance Testing Load testing was at full production estimates. Subsequent tests at higher load levels showed no increase in storage latency. Future plan to upgrade to 10G networking

10. Client Performance Testing Client testing shows results for 50% of total production environment (site redundancy)

11. Service Level Agreement • Service Level Agreement will be posted shortly on IT website • http://it.uoregon.edu/systems/services/exchange/sla • Design target of 99.999% availability – 5-6 minutes of user-impacting unscheduled downtime per year

12. Exchange 2010 Access URLs

13. Live Environment Demo • Show live production environment • Show Outlook Web Access https://outlook.uoregon.edu • IE • Firefox • Safari

14. Upcoming Changes • Global Address List • Autodiscover • IDM synchronization • Mail flow/Routing into Production

15. Global Address List Changes • Administrative Approval Received • Development work necessary to ensure we are protecting FERPA protected data • Announce changes one week in advance • GAL updates will propagate over a normal weekend • Send out announcement after all GAL changes are complete • September 9th- 11th – GAL changes for all Staff and Faculty goes live • Student GAL may be implemented during quarter 4 of 2011

16. Autodiscover Changes • The Autodiscover service does the following: • Provides access to Exchange features for Outlook 2007 or Outlook 2010 clients that are connected to your Exchange messaging environment. • Uses a user's e-mail address and password to provide profile settings to Outlook 2007 or Outlook 2010 clients and supported mobile phones. • Autodiscover service is inconsistently functioning • Microsoft does not support autodiscover with 2003 mailboxes • On an announced date we will cutover autodiscover URL to point to the production environment (go-live date)

17. Exchange Mail Routing - Today

18. Exchange Mail Routing – Go-Live Controlled by Identity Manager

19. Microsoft Exchange Support

20. Supported Exchange Account Types • Phase I – Fall 2011 • Phase II – Winter 2011

21. Exchange Administrator Approval Form

22. Role Base Access Control

23. IDM Integration • From the Exchange Scope and Vision • “Centralized Identity Management – consistent and automated provisioning of client access through integration with the central Identity Management infrastructure.” • “Identity Management: Access to Exchange must be managed based on the rules and practices in use for the current central email offering.”

24. Access by Affiliation

25. Provisioning • Departmental Exchange Administrator will Exchange enable managed accounts in their OU through the IDM interface • Mailbox is automatically created with a 2GB quota – increases available upon request • .forward file is automatically updated to point to the correct Hub Transport Server • At the end of the provisioning event, an email notification will be sent to the Exchange Admin and the OU Admin.

26. De-provisioning • Exchange access can be manually removed prior to automatic de-provisioning. • De-provisioning of Exchange will happen automatically when a users affiliation changes such that they no longer are eligible for access. • De-provisioned accounts will have their mailboxes detached and retained for 75 days • Exchange will automatically remove detached mailboxes after 75 days. • Email notifications will be sent to the end user as Exchange starts to de-provision from the end user. These will follow the same configuration as the notifications associated with our current Email role.

27. IDM Interface Click here

28. IDM Interface Click here

29. Migration • Pre-Requisites • Migration Types • 2003 to 2010 Migration • IMAP to 2010 Migration • Ongoing Migrations

30. Migration Pre-Requisites • Active Directory OU • IT Unit will assume Tier I and Tier II responsibilities • Designate a qualified and approved full-time IT professional as delegated Exchange Administrator • Must have all email to be migrated stored in an online 2003 mailbox or centrally managed IMAP account

31. Migration Spreadsheet

32. 2003 – 2010 Migration Exchange 2010

33. IMAP to 2010 Migration Exchange 2010

34. Ongoing Migrations • Users that have their mailboxes migrated from Exchange to IMAP will also be subject to additional migrations when affiliation status changes • Users will be given a self-remediation web-accessible tool to self migrate their email between environments on affiliation changes

35. IMAP to Exchange Migration Tool

36. IMAP to Exchange Migration Tool 2

37. IMAP to Exchange Migration Tool 3

38. Migration Checklist

39. Caveats/Considerations • Only Exchange mailboxes with existing DuckID’s will be supported for migration at go-live • Public Folders, Mail Enabled Groups (Distribution Lists), and Resource accounts are Phase II • Some of these processes are subject change

40. More Information • http://it.uoregon.edu/systems/services/exchange • Questions?

41. Acknowledgements