1 / 10

Exchange Implementation Update

Exchange Implementation Update. Pat Burns, CSU Westnet Presentation June 14, 2006. Agenda. Exchange features Project timeline Architecture description Affiliation addresses Rapid deployment program Decisions. Exchange Features – Why Change?. Centralizes electronic calendaring

aconway
Download Presentation

Exchange Implementation Update

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. Exchange Implementation Update Pat Burns, CSU Westnet Presentation June 14, 2006

  2. Agenda • Exchange features • Project timeline • Architecture description • Affiliation addresses • Rapid deployment program • Decisions VPOF Presentation - Exchange

  3. Exchange Features – Why Change? • Centralizes electronic calendaring • Provides ubiquitous single point of access to: • E-mail, Calendar, and Address book (Contacts) • Mobility(!) • Integrates with current Exchange environments • Allows non-Exchange environments to continue ‘as is’ or migrate to new service • 500MB quotas (currently 75MB) • Greater robustness VPOF Presentation - Exchange

  4. Project Timeline • June, July: Order and install hardware and software, work with Microsoft consultants • Fall, 2006: Mail migrations, Outlook training • Calendar transition • For all meetings through December 31, 2006: use Oracle calendar • For all meetings after January 1, 2007: use Exchange calendar • May 1, 2007: sunset date for Oracle calendar VPOF Presentation - Exchange

  5. Exchange Architecture - Summary • Eight servers: increased performance and redundancy/robustness • 2 supporting web access • 6 supporting application in fail-over model • Large, scalable storage – 9 TB iSCSI • Cost: $200K • Arriving: late June and July, 2006 VPOF Presentation - Exchange

  6. Exchange Back-end Exchange Back-end N e t Outlook Web Access Load Balancer Exchange Back-end Exchange Back-end Disk Storage Internet Exchange Back-end Exchange Back-end Load Balancer Disk Storage N e t Outlook Web Access Disk Storage New Exchange Architecture- Scalable and Robust Users Front end Back end Storage Active/ Active/ Passive VPOF Presentation - Exchange

  7. Issue #1: Affiliation Addresses • Affiliation address • User.Name@Org.ColoState.EDU • “Org” may be a dept., unit, or club, etc., e.g. ASCSU, CAHS, etc. • Vs. the CSU University standard • User.Name@ColoState.EDU • Can be “pointed to” any email server for delivery • Recommended by the World Electronic Messaging Association VPOF Presentation - Exchange

  8. Affiliation Addresses - Options for Deployment • Three potential solutions: • Support neither ‘To’ nor ‘From’ • Disrupts delivery of historical email addresses, stationary, business cards, etc. • Support only delivery (‘To’) • No changes in business cards or stationery required now, but may “sunset” this in the future • Support delivery & outbound stamp (‘To’ and ‘From’) • Involves significant engineering VPOF Presentation - Exchange

  9. Issue #2: Rapid Deployment Program – Exchange 2007 • Early release code • Heavily vendor supported • Premium Support Engineers • Product Team • $50K+ worth of consulting services provided for free • Timeline matches ours • Promotion incentive from Microsoft • Benefits to CSU • Performance increases over Exchange 2003 • Better mail/calendar tools and interface • Avoids significant upgrade effort in 18-24 months VPOF Presentation - Exchange

  10. Decisions • Affiliation Address Option #2 • We do not have the resources to implement Option #3, and it would significantly complicate our operational environment • Uses the University standard for ‘From’ • Allows retention of “identity” on all business cards, stationary, etc. for ‘To’ • This is just one of the numerous Identity Management issues we will continue to struggle with over time • Proceeding with the RDP for Exchange 2007 • Detailed analysis and checking with other sites lends confidence to a successful deployment VPOF Presentation - Exchange

More Related