Load Balancing Exchange 2010 with F5 LTM

In a earlier blogpost on load balancing Exchange 2010 I explained how to achieve this with a Kemp Loadmaster. In this blogpost I’d like to demonstrate how to configure this with an F5 Local Traffic Manager (LTM). This is actually part I of what I’ve demo’ d in the MEC 2012.

The configuration looks like this. There are two multi-role servers configured with a Database Availability Group (DAG). There’s a File Share Witness (FSW) configured on server FS01. The F5 itself is installed in a two arm configuration, so the VIP for the clients is on a different subnet then the Exchange Server.

image

Continue reading Load Balancing Exchange 2010 with F5 LTM

How to brand OWA in Exchange 2013

Jeff Guillet wrote an excellent post on his EXPTA {blog} on how to brand the OWA logon page with the CAS server name which is perfect when testing load balancing solutions. You can find this post here: http://www.expta.com/2010/03/how-to-brand-owa-2007-and-2010-with.html. For testing OWA in Exchange 2013 the process in somewhat similar. On the Exchange 2013 Client Access server, navigate to the C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\owa\auth directory and open the logon.aspx page with (for example) Notepad.

In this file, scroll down to the <div class=”logonContainer”> section and add the servername text just before the <div class=”signInInputLabel” id=”userNameLabel” aria-hidden=”true”> section.

image

Save the file and in your browser navigate to the Exchange 2013 Client Access Server:

image

I’m pretty sure this is not supported, and you’ll lose the changes after an upgrade, but for testing purposes it’s perfect.

Exchange 2010 SP3 on Windows Server 2012

Now that Exchange 2010 SP3 is available it’s also possible to install it on Windows Server 2012. Normally that’s not a problem, but you have to be careful with the prerequisite software. Windows Server 2012 comes with .NET Framework 4.5 and Management Framework 3.0 (including Powershell 3.0) but Exchange 2010 still requires .NET Framework 3.5 and Powershell 2.0. Luckily Powershell 2.0 and Powershell 3.0 can coexist on the same box with any issues.

Install .NET Framework 3.5 and Powershell 2.0

To install .NET Framework 3.5 (which automatically includes Powershell 2.0 on Windows Server 2012) you can use Server Manager, but there’s a little snag because Server Manager does not know where the install files are located 🙂 Continue reading Exchange 2010 SP3 on Windows Server 2012

TMG 2010 Console fails on startup

I ran into this issue several times now. After installing a new Forefront Threat Management Gateway (TMG) 2010 when the TMG Console is started the first time it fails with the following error:

An error has occurred in the script on this page.
Line: 283
Char: 13
Error: invalid argument
Code: 0
URL:file:///C:/Program%20Files/Microsoft%20/Forefront%20Threat%20 Management %20Gateway/UI_HTMLs/Generic.htm?guid=%7B43E06AFC-729B-8BC2-33A9E35BB12D%7D
Do you want to continue running scripts on this page?

image

This is a small bug in HTML interface code. To solve it, navigate to the C:\Program Files\Microsoft Forefront Threat Management Gateway\UI_HTMLs\TabsHandler\ directory and open the TabsHandler.htc file.

There are 3 lines containing “paddingTop” causing this issue. Find the lines and disable them by adding // at the beginning of the line.

image

Save the file and the console opens as expected.

Load balancing Exchange 2010 (part II)

In my previous post I discussed Exchange 2010 load balancing principles briefly (I need to leave some additional stuff for my MEC presentation) and how to setup a Kemp LoadMaster in a single-arm configuration. In this 2nd (and final) blog post I’ll show you how to configure Virtual Services for OWA 2010 and MAPI (Outlook clients).

Create a new Virtual Service for OWA

To create a new Virtual Service expand the Virtual Services and click Add New to open the wizard and fill in the necessary options like the IP Address of the new virtual service, the accompanying port number and give the service a nickname. In the Use Template option you can select a predefined template for the service. The advantage of using a template is of course that all options are filled in by Kemp, optimized specifically for the LoadMaster. Since we’re creating an OWA service select the Exchange HTTPS Offloaded template and click the Add this Virtual Service button.

In this example the Client Access Servers are configured with SSL offloading. The clients connect to the LoadMaster using SSL, the LoadMaster in turn connects just on port 80. For more information on how to configure SSL offloading in Exchange Server 2010 please check this blog post: http://www.jaapwesselius.com/2012/06/10/ssl-offloading-with-powershell/

image

Figure 1. Select a preconfigured template to use when creating a new Virtual Service.

Continue reading Load balancing Exchange 2010 (part II)

Microsoft UC Specialist