Building NLB Exchange 2010 RTM CAS / HT Servers (Hyper-V) – Part 3
NOTE: Before configuring anything after the deployment of the CAS server roles, remember that if any send or receive connectors are configured, these would supersede the configured Exchange 2003 connectors or they would take precedence over the default SMTP virtual server in Exchange 2003 if no connectors are configured at all. My recommendation would be to install the mailbox server roles and create mail databases before performing any CAS configuration tasks.
The following steps should be performed to specify the CAS Array. All this does is specify the connection point to the client. The virtual IP address of the NLB servers will be used as a connection point for MAPI clients.
The CAS Array can be set by opening the Exchange Management Shell and typing the following command:
New-ClientAccessArray –Name “MAPI Client Connection Point” –Fqdn “Outlook.Morecoffeeany1.com” –Site “Default-First-Site-Name”
This configuration task should be performed prior to deploying any Exchange 2010 servers. If any Exchange 2010 servers have been deployed in the environment already, their databases will have to be updated with this information with the following command to be run against each database:
Set-MailboxDatabase <DatabaseName> -RpcClientAccessServer “Outlook.Morecoffeeany1.com”
Now create a DNS A record Outlook.Morecoffeeany1.com with the IP address of the NLB VIP.
When the HT server roles are ready to be configured, it is a good idea to create a connector that uses the NLB IP address to listen on port 25 for incoming SMTP mail to be relayed by the HT role.
See http://www.msexchange.org/articles_tutorials/exchange-server-2007/planning-architecture/load-balancing-exchange-2007-sp1-hub-transport-servers-windows-network-load-balancing-technology-part2.html for a full explanation of this process. This article was written for Exchange 2007 but is still relevant to Exchange 2010.
Building NLB Exchange 2010 RTM CAS / HT Servers (Hyper-V) – Part 1
Building NLB Exchange 2010 RTM CAS / HT Servers (Hyper-V) – Part 2
1 Comment »
Leave a Reply
-
Recent
- Exchange 2010 Cross Forest Migration: The case of the missing User Account Attributes
- Exchange 2010 Cross-Forest (Cross-org) Client Migration Planning
- Vonage – Firewall
- Exchange 2010 SP1 (Beta)
- Exchange 2010 RTM: ActiveSync and the Personal Archive
- Exchange 2010 DAG Implementation
- Upgrade Exchange 2003 Default Address Policy & Address Lists to Exchange 2010
- External HA failover in multiple Internet facing Exchange 2010 sites
- Configuring IE Enhanced Security Configuration on Windows 2008 R2
- Building NLB Exchange 2010 RTM CAS / HT Servers (Hyper-V) – Part 3
- Building NLB Exchange 2010 RTM CAS / HT Servers (Hyper-V) – Part 2
- Building NLB Exchange 2010 RTM CAS / HT Servers (Hyper-V) – Part 1
-
Links
- Belgium Exchange Pro's
- D Golman's Blog – Exchange Escalation Engineer
- Joe Richard's AD Site
- Eric Walter's Exchange Blog
- Harold Wong's Blog
- Exchange Server Team (You Had Me At EHLO)
- Steve Thompson – ConfigManager MVP
- My LinkedIn Profile
- Chris and Robin's Technology Blog
- Jeff Guilet's Expta Blog
- Hugh Marlor's AllUnified Blog
- Elan Shudnow's Blog


Nice post. The Hyper-V Specific section helped me out. Was getting the same error after creating the NLB cluster.