Exchange 2013: OpenSource Loadbalancer Zen

On my forays through the Internet, I came across Zen. Zen is an OpenSource load balancer that is easy to install and has a nice web configuration interface. Reason enough for me to write a howto.

So quickly set up and install a VM

The installation of Zen is identical to the minimal installation of Debian, a few basic configurations such as IP, gateway and DNS are requested and everything is installed.

As soon as Zen is installed, you can log in to the configuration website. The Zen configuration is accessed via https://ZEN_IP:444 (User: admin Password: admin)

After logging in, you will see the web interface

Since I have installed Zen in a VM with only one network card, I create a virtual network card that will provide the virtual service for Exchange. The configuration of the virtual interface is done under "Settings" -> "Interfaces". In my case, the default gateway, which I specified during installation, was not adopted; it can be added here.

Now, under "Manage" -> "Farms", you can create the farm, i.e. the virtual service under which Exchange will be accessible in the future. I select the previously created virtual interface as the virtual IP. I have selected "Exchange2013" as the name and TCP as the profile. Only 443 (HTTPS) is required as the virtual port.

The farm has been successfully created, now the Exchange servers can be added to the farm. As soon as the farm has been created, the "Edit Farm Settings" button can be found in the "Actions" column

Exchange servers can now be added in the farm settings

Done. That was all. The "View Backend Status" button can be found in the farm overview. Here you can check whether the Exchange 2013 servers are available and how many connections each server has.

Now all that remains is to configure Exchange, but I have already described this in detail in this article (including Kerberos authentication):

https://www.frankysweb.de/exchange-2013-authentifizierung-auf-kerberos-umstellen/

Note: If you do not want to use Kerberos, you only need to use these commands from the above article:

Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -InternalUrl "https://outlook.frankysweb.local/owa"
Get-EcpVirtualDirectory | Set-EcpVirtualDirectory -InternalUrl "https://outlook.frankysweb.local/ecp"
Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -InternalUrl "https://outlook.frankysweb.local/EWS/exchange.asmx"
Get-OabVirtualDirectory | Set-OabVirtualDirectory -InternalUrl "https://outlook.frankysweb.local/OAB"
Get-ActiveSyncVirtualDirectory | Set-ActiveSyncVirtualDirectory -InternalUrl "https://outlook.frankysweb.local/Microsoft-Server-ActiveSync"
Get-OutlookAnywhere | Set-OutlookAnywhere -InternalHostname outlook.frankysweb.local -InternalClientsRequireSsl:$true

The values for the InternalUrl/InternalHostname parameters must then correspond to the configured DNS entry and the IP address of the DNS entry must correspond to the farm IP

Important: Also remember the certificate! The new internal host name must also be on the certificate.

https://www.frankysweb.de/exchange-2013-san-zertifikat-und-interne-zertifizierungsstelle-ca/