I had not seen those - thanks for posting them. I'm not thrilled with #3 - they gloss over the CAS/HT planning and don’t really discuss the impact that your choice of HW LB has on CAS planning (all of F5, Cisco, and Kemp Technologies have solutions that deal with SNAT sources so that IP affinity can be dealt with properly). It also assumes SAN. I know that's a requirement in some environments, but in general - even for the BIG deployments - I've been deploying 2010 on DAS.
Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Gary Babb [mailto:gsb...@hotmail.com] Sent: Tuesday, January 04, 2011 10:17 AM To: MS-Exchange Admin Issues Subject: re: Designing & Implementing Exchange 2010 in the new year. Microsoft has written white papers on deploying Exchange 2010 for 500, 9,000 and 16,000 mailboxes. They are a great read, see white paper description below from Microsoft: This white paper provides an example of how to design, test, and validate an Exchange 2010 solution for customer environments with 9,000 mailboxes deployed on Dell server and storage solutions. The step-by-step methodology in this document walks through the important design decision points that help address key challenges while ensuring that core business requirements are met. Here are the links to each white paper: 1. 500 Mailboxes - http://www.microsoft.com/downloads/en/details.aspx?FamilyID=e0e93251-fc04-4a18-8aa0-23817b6d0c97 2. 9,000 Mailboxes - http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c89c9e7b-9b70-4370-8db9-593cbe518791 3. 16,000 Mailboxes - http://www.microsoft.com/downloads/en/details.aspx?FamilyID=987882fb-5286-48a6-800f-64665a278613 --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
