CAS Array configuration

If the network was configured in teaming, you have to break the teaming before configuring the CAS array.

• On both network cards on both servers definitions:

                check mark ipv6 even if we don't need it.

• On the NLB network card definitions on both servers:

                on the ipv4 properties remove default gateway definition.

DNS configuration

Open the DNS in the root Domain and create a new Host with the name where the clients will connect.

Give the IP address and check the "Create associated pointer (PTR) record"

Open the first HUB/CAS server

Open the Exchange powershell

[PS] C:\Windows\system32>Import-Module servermanager

[PS] C:\Windows\system32>Add-WindowsFeature nlb

You should receive the result below

Open the second Hub/CAS server and run exaclty the same functions

[PS] C:\Windows\system32>Import-Module servermanager

[PS] C:\Windows\system32>Add-WindowsFeature nlb

Go back to the first node and run on the Exchange powershell

[PS] C:\Windows\system32>Import-Module NetworkLoadBalancingClusters

Note: Make sure you have an interface for the NLB configuration and the same network name for both servers

[PS] C:\Windows\system32>New-NlbCluster -InterfaceName NLB -ClusterName casarray -HostName HubCas01 -ClusterPrimaryIP 192.168.0.1 -OperationMode MultiCast

Result:

Name                          IPAddress                     SubnetMask                    Mode

----                          ---------                     ----------                    ----

casarray                       192.168.0.1                  255.255.255.0                 MULTICAST

Then run the following

[PS] C:\Windows\system32>Get-NlbClusterPortRule |Remove-NlbClusterPortRule -Force

[PS] C:\Windows\system32>Get-NlbCluster | Add-NlbClusterPortRule -StartPort 80 -EndPort 80 -

Protocol TCP -Affinity Single

[PS] C:\Windows\system32>Get-NlbCluster | Add-NlbClusterPortRule -StartPort 443 -EndPort 443 -Protocol TCP -Affinity Single

[PS] C:\Windows\system32>Get-NlbCluster | Add-NlbClusterPortRule -StartPort 135 -EndPort 135 -Protocol TCP -Affinity Single

[PS] C:\Windows\system32>Get-NlbCluster | Add-NlbClusterPortRule -StartPort 1024 -EndPort 65535 -Protocol TCP -Affinity Single

Adding the second node to the cluster (from the first node)

[PS] C:\Windows\system32>Get-NlbCluster | Add-NlbClusterNode -NewNodeName HubCas02 -NewNodeInterface NLB

Name                             State                            Interface                       HostID

----                             -----                            ---------                       ------

HubCas02                           Converging                       NLB                             2

Note: Verify that the state was converged before continuing

Name                             State                            Interface                       HostID

----                             -----                            ---------                       ------

HubCas01                           Converged(default)               NLB                             1

Creating the CAS array

[PS] C:\Windows\system32>New-ClientAccessArray -Name "CAS Array" -fqdn Exmail.domain.com –site Sydney

You should receive the result below

Name                Site                 Fqdn                           Members

----                ----                 ----                           -------

CAS Array        Sydney           Exmail.domain.com            {HubCas01, HubCas02}

In order to allow other vlans to access the cas enter the netsh command in both Hub/CAS server:

C:\>netsh interface ipv4 set int "nlb" forwarding=enabled