Farm Settings

Enable Load Balancing

Usage of the Farm capabilities does start with Enabling the Load Balancing.

IP Address of this Server

This is the IP Address clients will use for connecting to this AADS Terminal Server.
In the example above, all Clients will connect to this AADServer:

• IPv4: 192.168.12.34
• IPv6: FD00::1:2:3:4

The Clients can connect by either IPv4 or IPv6.

DHCP not recommended / Use fixed IP Address for the Servers.

It is recommended to give the AADServers a fixed IP Address. Do not use DHCP for assigning an IP Address to the AADServers.

DHCP implies that the IP Addresses of the AADServer might change every few hours or days, and that will only cause trouble with the Load Balancing. Servers should have a fixed IP Address.

IPv6

The small, green (IPv)6 can be used to toggle between the various ways an IPv6 address can be displayed.

Broadcast IP Address and Portnumber

The UDP Broadcast IP Address and Portnumber is used between the AADS Terminal Servers in the Farm for communication between each other.
It is not used in any way between Clients and Servers.

Example:

• There are 3 Terminal Servers in the Farm:
  
  
  • Terminal Server 1
    
    • Terminal Server network IP Address 10.1.50.5
    • Client network IP Address 192.168.200.247
      
  • Terminal Server 2
    
    • Terminal Server network IP Address 10.1.100.5
    • Client network IP Address 192.168.200.248
      
  • Terminal Server 3
    • Terminal Server network IP Address 10.1.150.5
    • Client network IP Address 192.168.200.249
      
• The UDP Broadcast IP Address is set as 10.255.255.255

The Farm used IPv4  UDP for communication among the Servers in the Farm.

Note

The broadcast IP is a setting that is determined by the IP address and Subnetmask of the network card.

Broadcast IP Example 1

• IP Address 192.168.1.1
• Subnetmask 255.255.0.0
• Broadcast IP Address of this network is 192.168.255.255

Broadcast IP Example 2

• IP Address 10.1.50.5
• Subnetmask 255.0.0.0
• Broadcast IP Address of this network is 10.255.255.255

Block multiple login

It is important to block multiple logins from users. The reason for this is the use of roaming profiles. When an user is allowed to login twice or more, there will be trouble with his roaming profile, because it is being used and changed on 2 or more Terminal Servers at the same time, and this does always results in "conflicts". The profile of the user might get damaged.
Therefore it is advised to block multiple logins among the Farm.

Create Logfiles

If required, each Terminal Server in an AADS Farm can create logfiles, per month for user activity. Purpose of these logfiles is auditing if such is required.
The format of the logfiles is fixed, with exception of the date/time stamp, which can be local time or UTC time.
The logfiles are located in:

aad_YYYYMM_UserActivities.log

The first line of the log file denotes the format:

'Activities','Server','Domain','Username','Date (YYYY-MM-DD)','Time (HH:MM:SS)'

Redundancy in the Farm: let each Terminal Server generate the logfiles

Each Terminal Server in the Farm is able to generate the same log file. From a redundancy point of view it is indeed better to let each Terminal Server in the Farm generate the same log file about the user activities.