#EXCHANGE ENTERPRISE USER CAL WINDOWS#
Network Load Balancing is a feature of Windows Server 2008 Standard and Enterprise. Remember when planning for NLB implementation it is best to create a separate VLAN for NLB cluster traffic. However if you have a third-party hardware-based network load-balancing for stateless applications such as a CAS server, you can get away from using Network Load Balancing. To cluster a Client Access Server Array you need to implement NLB (Network Load Balancing). The Microsoft Exchange Mail Submission service on Mailbox servers automatically load balances between all available Hub Transport servers in the same Active Directory site.Ĭlient Access does not require Enterprise Edition of Windows Server 2008 for high availability. This clustering functionality if built into both Exchange 2010 standard and enterprise edition. Hub Transport does not require Enterprise Edition of Windows Server 2008 for high availability. Which exchange roles need Windows 2008 Enterprise Edition for High Availability? However you may need Windows Server Enterprise Edition or higher depending on what roles you want to cluster as exchange 2010 leverages some high availability functionality from the operating system. No - you can setup Exchange 2010 clustering with nothing but Exchange Standard Edition for all 5 roles. Is exchange 2010 enterprise needed for clustering? For example you could have a Exchange 2010 Enterprise Edition mailbox server DAG talking to Exchange 2010 client access servers and hub transport servers in the same active directory site. In this post I'm going to address many questions that comes around licensing with Exchange 2010 as this can be a very confusing area - it took me a while to understand it properly!Ĭan I have exchange 2010 standard edition mixed with exchange 2010 enterprise in the same exchange organisation?
0 kommentar(er)
