Exchange 2003/2007 Upgrade Path Recommendations to 2010 Additional reference information can be found in the back of the presentation on Noted References page. Presented October 12, 2010 at NYExUG Meeting Last Updated on October 12, 2010 Ben Serebin Ehlo & Network Consultant REEF Solutions ( If you can’t get enough Exchange & technology read my blog

About Ben Serebin Working in the IT sector since 1996 Specialty is Exchange Server, Spam Filtering, DNS, & Wireless. Recently Completed Projects Q4 2010: Hyper-V clustering & HP SAN implementation, and 36TB+ DR replication implementation in an Exchange 2010 environment [24 servers protected via 2 backup servers & 2 DR servers via QNAP iSCSI targets]. Upcoming Projects: Implementing a Vmware based High Availability VM cluster on commodity hardware (16GB, no DAS, & iSCSI based). Current Environment: Running Exchange 2007 Server on Windows 2008 on ESXi 4, server computing environment is entirely virtual, DC1 on ESXi 4 and DC2 on Hyper-V R2 (Windows role), Blackberry Enterprise Server Express 5, running on VMware ESXi 4. Current handheld device is a BlackBerry Bold 9650.

Agenda for Presentation Which Exchange Server versions work together (aka coexistence) Install Requirements/Recommendations for Exchange 2010 Active Directory Requirements for Exchange Clients That Work & Don’t with Exchange 2010 Requirements for 2010 for AD (2000/2003/2008/2008R2)? Upgrading Steps from Exchange 2003 to 2010 Migrating Guideline from Exchange 2007 to 2010 Requirements for 2010 for backups, anti-spam, & archiving.

One Big Exchange Server Happy Family? 5.5 No No SP2+ (native mode) 2007 RTM RTM+ Exchange Server Versions – Microsoft Supported Coexistence Tip: older version of Exchange must exist before installing 2010

Exchange Server 2010 Install Requirements (no AD nor clients) Needed to start the party…Partying right… x64 operating system (2008 SP2 & 2008 R2) Deploy 2008 R2 due to longer EOL (End of Life support) & you gain x64 wisdom.. Hard Drive Space: 1.2GB for Exchange installation, 200MB on system volume, and 500MB for transaction logs. 2 partitions (OS/apps and Exchange data [database and transaction logs] with 2x of your 2-4 yr plan. RAM for single role 4GB+ (& CAS/HUB)Edge, Hub, CAS, & CAS+Hub can be 2- 4GB. Mailbox & multi-role 8GB + # of users (10MB for active users [160 msgs/day] / 5MB for less centric staff [85 msgs/day]) Mailbox should be 8GB + (10MB x # of users). So, 100 users is 8GB + (10*100) = 9GB. Normally recommend 8GB+ depending on overall database size. Larger environments support up to 48GB. Management Tools on x64 OS that is Vista and later including server OSes. Stick with server based management. Run it in a VM if necessary.

Active Directory is the foundation for Exchange Nope! 2003 SP1+ Possible 2008 RTM R2 RTM+ Domain Controller Version Answers to icons (2008) 1)AD Domains and Trusts 2)AD Sites and Services 3)AD Users and Computers

Communicating Nicely with Exchange 2010 PC Outlook 2003* (cached mode) Outlook 2007 Outlook 2010 Mac Entourage 2008 Web Service Edition Outlook:Mac 2011 At our March 2010 meeting, we demo the Outlook 2003 & Exchange 2010 problems. See KB article. Only Fix is cached mode. From Technology Reviews…

Upgrading Exchange Server 2003 to 2010 Upgrade 2003 to SP2 Deploy Exchange 2010 in this order (CAS, HUB, MBX) Configure 2003 Front- End & 2010 CAS support. Configure 2010 HUB to take over flow. Move Mailboxes to 2010 This can be a fairly straight forward upgrade. If you are aware of the following (search for TechNet ee332348): Non-2010 mailbox users continue to use older version of OWA. After migration, no more redirect to legacy.

Migrating from Exchange Server 2007 to 2010 Upgrade 2007 to SP2 (HUB Deploy Exchange 2010 in this order (CAS, HUB, MBX) Configure 2010 CAS for legacy hostname Configure 2010 HUB to take over flow, but 2007 HUB present until decom. Move Mailboxes to 2010 This can be a fairly straight forward upgrade. If you are aware of the following (search for TechNet dd638158): Installing an additional 2007 is only possible if one pre- dates the 2010 install. Message flow for 2007 & 2010 Coexistence

Requirements for Pillars of Exchange 2010 Backups DAG friendly? Make sure ability to backup passive database Personal Archive (server-side) aware. RTM & SP1 changed functionality. Anti-Spam Support for hub transport spam tagging. Disclaimer support Archiving Support for archiving based on HUB CRITICAL: do not upgrade to SP1 until you have configured and installed SP1 compliant applications.

Run, don’t walk to deploy/test Exchange Server 2010 Download Exchange 2010 SP1 (it’s the full version). Don’t want to install. Download the pre- configured Exchange 2010 VHD and power it on! Use a test domain name for testing DNS, mail flow, firewall, and SSL configurations. Improving your Deployment Success

Noted References – Microsoft’s Exchange Server 2010 System Requirements - Microsoft TechNet – Prepare Active Directory and Domains - us/library/bb aspx - Microsoft TechNet – Exchange 2003 Planning Roadmap for Upgrade and Coexistence with Exchange – Microsoft Exchange 2010 Planning Storage Considerations - Microsoft Support Policies and Recommendations for Exchange Servers in Hardware Virtualization Environments us/library/cc794548%28EXCHG.80%29.aspx - Exchange 2010 System Requirements - us/library/aa aspx -Outlook 2003 not liking Exchange 2010 when run in non-cached mode

Thank you for attending the October 2010 NY Exchange User Group Meeting. Now for Question of the Month…… Raffles – do not forget, if you bring in new members, you 2x, 3x, or more your chances to win raffle prizes. TechHit.com (Outlook add-ons) – raffling off any one of their products (SimplyFile [intelligent filing], EZ-Detach [easily detach multi- s of attachments], MessageSave [backup, archive, save msgs], AutoRead [mark as read/remove new mail icon], & QuickJump [quickly open/move between Windows folders].