<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>High level Exchange 2010 architecture</title><link>http://blogs.technet.com/b/ucedsg/archive/2009/06/29/high-level-exchange-2010-architecture.aspx</link><description>Here are some questions I had from a college in Ohio wanting to plan for Exchange Server 2010: &amp;#160; What does the Exchange 2010 architecture look like? The 5 Exchange 2010 roles are the same but there are some major changes in the way things work: Outlook</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: High level Exchange 2010 architecture</title><link>http://blogs.technet.com/b/ucedsg/archive/2009/06/29/high-level-exchange-2010-architecture.aspx#3280664</link><pubDate>Sat, 12 Sep 2009 02:23:42 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3280664</guid><dc:creator>markga</dc:creator><description>&lt;p&gt;Brian,&lt;/p&gt;
&lt;p&gt;It depends on where your CAS servers are placed. If you have multiple CAS roles in the same AD site then it would not necessarily use the locally hosted CAS. &amp;nbsp;Your CAS array would be load balanced with NLB or HWLB. One note when combining roles, you cannot have NLB and DAG on the same server so you would have to leverage a 3rd party LB.&lt;/p&gt;
&lt;p&gt;ISA 2006 would direct all client traffic via HTTPS to the CAS roles via a NLB or HWLB VIP address.&lt;/p&gt;
&lt;p&gt;Thus far the beta recommendations are 8 core for CAS and 8 core for multi role &amp;nbsp;(16 max) - The final HW and proc core recommendations will be coming after RTM of Exchange 2010.&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://blogs.technet.com/blogfiles/ucedsg/WindowsLiveWriter/Exchange2010RCavailablefordownload_DFDE/image_6.png"&gt;http://blogs.technet.com/blogfiles/ucedsg/WindowsLiveWriter/Exchange2010RCavailablefordownload_DFDE/image_6.png&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Combined &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3280664" width="1" height="1"&gt;</description></item><item><title>re: High level Exchange 2010 architecture</title><link>http://blogs.technet.com/b/ucedsg/archive/2009/06/29/high-level-exchange-2010-architecture.aspx#3280660</link><pubDate>Sat, 12 Sep 2009 01:42:27 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3280660</guid><dc:creator>Brian</dc:creator><description>&lt;p&gt;In Exchange 2007 the HUB roll on a mailbox server would see only that HUB being used by clients on the MB server. With all rolls being supported on a each box (even if it's in a DAG) would the clients of one MB server only use that CAS (ala redirect to your CAS) or would they still all be split. How does this impact ISA publishing OWA if all your CAS are on each MB server. With IO requirements being lower and CAS doing all the client connections a single 16 core server with 32GB of RAM looks more attractive than 1 with 4 cores and 4G (HUB) 2 with 8 cores and 16GB (CAS).&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3280660" width="1" height="1"&gt;</description></item></channel></rss>