Building NLB Exchange 2010 RTM CAS / HT Servers (Hyper-V) – Part 2
Before using the NLB cluster for Exchange, the NICs should be able to forward requests between each other. This is achieved by running the following command on the cluster NICs on each node of the cluster:
netsh interface ipv4 set int “Cluster Only LAN” forwarding=enabled
The reason for this configuration is as clear as mud at this stage. However, I assume that it has to do with the fact that the cluster only interface does not have a gateway configured for the connection. This connection functions on a broadcast anyway. According to the Microsoft Enterprise Networking Team, the packet will be dropped since IP forwarding is not enabled by default in Windows 2008 and the inbound packet comes in without a subnet mask.
Now we’re ready to install Exchange 2010. First I’ll run the ExPDA to check the environment for the Exchange 2010 prerequisites. If you’re not sure how download and use the ExPDA, check my earlier blog post on how to do this.
Building NLB Exchange 2010 RTM CAS / HT Servers (Hyper-V) – Part 1
UPDATE: 07/12/2011
Since this has been a topic of debate, I’ve added an additional network diagram (not one generated in my lab) so that it may become a little clearer as to how NLB works. The understanding for this network configuration comes directly from Michael Platts’ blog post: Balancing Act: Dual-NIC Configuration with Windows Server 2008 NLB Clusters.
I know I’ve been pretty offline regarding this blog but I fully intend to jump start it soon.
This post was created using Joe Hoegler’s post as a guide. All Exchange 2010 client access to mailboxes and other resources go through the CAS server. Clients no longer connect to the Exchange server directly for anything. With this said, it makes sense to build CAS servers in an HA configuration. This article was created to detail the steps required to create a load balanced CAS / HT server using Windows Network Load Balancing.
Before deploying the NLB configuration, the following should be carefully considered:
“You achieve load balancing for Hub Transport servers when you install more than one Hub Transport server in the same Active Directory site. By default, connections to Hub Transport servers are automatically load balanced if more than one Hub Transport server is deployed in an Active Directory site. If one Hub Transport server is unavailable, the operational Hub Transport servers continue to accept connections. If all Hub Transport servers in an Active Directory site are unavailable, messages are queued until a Hub Transport server becomes available or the messages expire.
Load balancing of outbound connections to remote domains is achieved by specifying more than one Hub Transport server in the same Active Directory site as a source server for the corresponding Send connector. Load balancing doesn’t occur when the source servers for a Send connector are located in different Active Directory sites.
Note:
If the Hub Transport server is installed on the same hardware as the Mailbox server role, load balancing may not occur. When the Hub Transport server role is on the same hardware as the Mailbox server role, the local server is preferred for all messages that are sent by users who have mailboxes on that server. Therefore, in this scenario, true load balancing does not occur.” Taken from: http://technet.microsoft.com/en-us/library/bb125239.aspx
Requirements
Two or more servers running Windows 2008 R2 (earlier version do have NLB built in but for this blog entry, I will be using Windows 2008 R2). Ideally each server will be configured with two NICs. One for client access and one for the cluster heartbeat. NLB requires all IPs to be on the same network.
Notes on Hyper-V
Exchange 2010 RTM: 10 things about Archiving
- Can only be accessed via Outlook 2010 and OWA 2010. (What about mobile devices?)
- Archive appears as a separate node in the Outlook interface. Items can be dragged and dropped in both directions. The import process is drag and drop through Outlook, no other way.
- There is a separate disk quota setting for the size of the email archive.
- Requires eCAL
- Drag and drop PST to archive. ExMerge is not supported.
- Only difference between main mailbox and archive is that archive cannot be accessed offline.
- Mailbox and mailbox archive has to be stored on the same mailbox server. (What about the database?)
- Mailbox search searches primary mailbox and archive mailbox node.
- No compression used on archived mailboxes.
- Archive dB can be part of a DAG.
Exchange 2010 RTM: DAG software requirements
I recently had my lab trashed. This is really a blessing in disguise. I decided to bring my lab in-house (literally). I was using space in a friend’s lab when his disk array decided to quit. Since then, I’ve acquire a shiny new Shuttle SP45H7. I’ve decided to face the challenge and build a sweet new Hyper-V lab and get on with it. I did encounter a few drawbacks so far. I purchased a really sweet video adapter card (MSI – R4350). Unfortunately there are only two PCI-E slots and the fan on the adapter card overlaps the second PCI slot. This means that I can only use the onboard NIC. Setting up Hyper-V with one NIC only will pose problems when attempting to simulate multiple subnets. I will require multiple subnets to accommodate a cool Exchange 2010 DAG setup.
Now that I’ve decided to test DAG and its features, I started doing a little research on the requirements and was surprised to learn that both Exchange 2010 Enterprise and Standard are supported for DAG.
Here are the software requirements according to Microsoft (http://technet.microsoft.com/en-us/library/dd638104.aspx)
Exchange: Windows Mobile 6.0 Emulator Lab Configuration
Mobile Emulator
I think I spent more time than I should have on this particular test. Finally, I got it working as designed. What I’ve captured here are the general steps to be followed when configuring Windows Mobile ActiveSync tests in the lab. Before deciding to use this emulator in a test, remember that the emulator cannot simulate true Cellular connectivity. It can only test ActiveSync connectivity via the network.
Exchange 2010 RTM: Deploying the first Exchange 2010 server in an Exchange 2007 organization
Before doing anything in an Exchange 2007 environment, it is highly recommended that you run the ExPDA. Why? If the existing Exchange 2007 organization is an Exchange 2007 SP2, the schema extensions for Exchange 2010 will already be present.
Refer to the Exchange 2007 SP2 Prerequisites article by the Exchange Server team. It quotes the following:
- If your Active Directory environment currently does not have any Exchange Server version deployed, then when you extend the schema, the schema changes included with Exchange 2000 through Exchange 2010 will be deployed in your environment.
- If your Active Directory environment is currently Exchange 2000 and you are upgrading to Exchange 2007, then when you extend the schema, the schema changes included with Exchange 2003 through Exchange 2010 will be deployed in your environment.
- If your Active Directory environment is currently Exchange 2003 and you are upgrading to Exchange 2007, then when you extend the schema, the schema changes included with Exchange 2007 through Exchange 2010 will be deployed in your environment.
- If your Active Directory environment is currently Exchange 2007 and you are upgrading to Exchange 2007 SP2, then when you extend the schema, the Exchange 2010 schema changes will be deployed in your environment.
When the ExPDA is run in an Exchange 2007 SP2 environment, navigate to the Forest tab in the results and look for the following:
“The Active Directory schema supports Exchange Server 2010 servers.”
OCS 2007 R2: Standard Edition Pool?
Lately I had a few customers who have been asking about saving some money when it comes to deploying OCS 2007 R2. I got asked on more than one occasion why more than OCS 2007 R2 Standard Edition cannot be used in the same Front End pool. Here’s why: the OCS 2007 R2 Supportability Guide states that the only supported configuration for Standard Edition is one where the default implementation installs a SQL Express 2005 database on the Standard Edition server.
Supported Back-End Server Database
Office Communications Server 2007 R2 is bundled with Microsoft SQL Server 2005 Express Edition with SP2 (32-bit).
This means that the user configuration for OCS is installed locally on each server. This information is not shared between servers. If you install two Standard Edition Servers in a Front End pool, the hardware load balancer (HLB) (which is required for OCS pools that contain more than one Front End server) will not know which Front End server the user is homed on. If a user logs on and is directed to (from the HLB) the Front End server that is not the user’s home, they will not be able to logon. This is not clearly documented in any of the OCS 2007 R2 guides but it is inferred.
Exchange 2010 RTM: Exchange Pre-Deployment Analyzer
This is a pretty simple but effective tool. It looks and feel exactly like the ExBPA. You don’t necessarily want to risk checking the prerequisites for Exchange 2010 by running the setup program in a production environment, especially since it will extend the schema if you install the Exchange 2010 tools. The ExPDA can be downloaded here.
The ExPDA performes the following checks:
Exchange 2010 RTM: Exchange Management Tools (ExBPA) – Caution
DO NOT INSTALL THE TOOLS IF YOU DO NOT HAVE EXCHANGE 2010 INSTALLED IN THE ENVIRONMENT (Read the entire post, it could save you a lot of trouble)
I needed to find a method to run the ExBPA to check for Exchange 2010 Readiness in a lab environment where Exchange 2003 was installed. The ExBPA for Exchange 2003 has an option to perform an Exchange 2007 Readiness check but not an Exchange 2010 Readiness Check. (As of today – 02/21/2010). As a last resort I decided to install the Exchange 2010 Management Tools which includes the Exchange 2010 ExBPA. My lab only has an XP client which is not a supported platform for the management tools. Check the list of supported operating systems here. The tools can only be installed on a 64-bit platform.
NOTE: I attempted to install the Management Tools on a Windows 2003 Ent. Ed. Server x64 and I got an error stating the program could not locate the wer.dll file.
Instead of upgrading my XP client to Windows 7, I decided to install the Exchange Management Tools on the server where I intended to install Exchange 2010 (Windows 2008 SP2).
Exchange 2010 RTM: Exchange Deployment Assistant
Prior to installing Exchange 2010 in the lab, I decided to explore the tools available to assess the environment and test for Exchange 2010 readiness. I encountered the Exchange Deployment Assistant on the Exchange Server Team’s web site and decided to have a look at it.
NOTE: This tool should be run on a workstation with Internet access and NOT a server.
Requirements: This website requires Microsoft Silverlight and Adobe Acrobat Reader if the user wants to download the checklist.
To launch the tool, go to: http://technet.microsoft.com/en-us/exdeploy2010/default.aspx#Home.
-
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
Visitor Locations
