220 likes | 316 Views
Explore the enhancements in Exchange Server 2010, such as the database availability feature, improved scalability, and new management roles. Learn about database changes and high availability options for better performance. Discover strategies for coexisting with previous Exchange Server versions. While promising, it is recommended to carefully consider before implementing in a production environment.
E N D
Exchange Server 2010what’s new? Jaap Wesselius May 27, 2009
Agenda • Disclaimer • Exchange Server 2007 • Exchange Server 2010 • Server Roles • Management • Coexistence
Exchange Server 2010 Beta1 • Disclaimer: this presentation is based on the first beta of Exchange Server 2010. This one is not feature complete! • Features might be added • Features might be changed • Features might be removed
Exchange Server 2007 • X64 bit enhancements • Scalability (memory) • Reduction in disk I/O • Active Directory sites routing • ‘Traditional’ clustering with shared storage • Database replication – LCR, CCR and SCR
Exchange Server 2010 • New replication technology called ‘database availability’ • Public Folders are still here! • New move-mailbox • Remote Management • MAPI on the CAS Server (MoMT) • Windows Server 2008 and R2 only • Real cool Outlook Live!
Exchange Server Roles • Exchange has 5 separate server roles: • Mailbox Server Role • Hub Transport Server Role • Client Access Server Role • Unified Messaging Server Role • Edge Transport Server Role • Roles can be on dedicated hardware or combined, except for Edge Transport
Mailbox Server Role • Contains Mailboxes and Public Folders • MAPI Clients do not connect to MBX • MAPI Clients do connect to PF • Extensible Storage Engine (ESE) • High Availability via replication
Database changes • Drastic changes in the database schema • Less tables, less indexes better performance • Database page size from 8KB to 32KB • Host large mailboxes (>1 GB) • Database and log files on one SATA disk • SIS is gone…
Database changes cont’d • Storage Groups are gone • Database, log files and checkpoint • Database no longer on server level but on organization level
High Availability • Database Availability • Basically CCR and SCR combined • LCR, CCR, SCR and SCC are gone • No need to install fail-over clustering • Database Availability Group • Multiple Database Copies • “self healing” database functionality • Add servers on demand
Move Mailbox • New Move-Mailbox functionality • Old and New mailbox are synchronized and switched when needed • Small downtime (don’t know about Outlook 2010 though) • Exchange 2007 and Exchange 2010 only
Hub Transport Server Role • Routes all messages in Exchange org • Internal Messages • External messages • Compliancy • Enhanced Disclaimers • Shadow redundancy • Integration with RMS
Client Access Server Role • All clients connect to CAS Server • Including MAPI (=Outlook) clients • New Outlook Web Access (now called Outlook Live) • Cross Browser experience is cool!
MAPI on the Middle Tier • Outlook (MAPI) clients connect to the Client Access Server for mailboxes • No direct connections to the Mailbox Database • Public Folder access still to Mailbox Server
Edge Transport Server Role • Additional layer of security • Message hygiene • Routes all messages to/from Internet
Exchange Management • Management Console & Management Shell • Powershell v2 • Windows Remote Management (WinRM) • ‘known issues’ in Beta1! • Use local shell as work-around
Coexistence • Exchange 2010 can coexist with: • Exchange Server 2003 SP2 • Exchange Server 2007 SP2 • No support for Exchange Server 2000 • Intra-org: transition • Inter-org: migration
Conclusion • It’s too early to make any conclusion • Exchange 2010 looks promising • Database Availability is key feature • Less complexity (esp. on clusters) • Database changes, less disk I/O • Start looking, start playing, but please don’t bring it into production yet!
Questions and Answers • www.simple-talk.com/exchange • www.microsoft.com/exchange • J.wesselius@dm-consultants.nl