Configuration Examples

Example 1

• Three AADS Terminal Servers are working together in a Farm.
• The name of the Farm is the name of the Domain Server.
• All three AADS Terminal Servers do have the same applications installed. This is done by the System Administrator:
  • Office
  • Email
  • Browser
  • etc
• The central fileserver holds all the user data.
  

The clients can use any of the AADS Terminal Servers, without noticing any difference in their user experience, desktop, applications and data.

Example 2

• The AADS Terminal Servers are connected to both the “Client” network and the “Server” network.
  • The AADS Terminal Servers have 2 network cards.
• The AADS Terminal Servers are configured in such a way that their internal network communication related to the Farm and related to the Load Balancing, is done using the “Server” network and is not done using the “Client” network.
  • By separating Client network traffic from the Server network traffic, more reliability is accomplished.

Example 3

AADServer WXP

Clients network card

Farm network card

Domain settings

Load Balancing settings

AADServer Win10

Clients network card

Farm network card

Domain settings

Load Balancing settings

Default Gateways

In this example both the Clients and Farm network cards do have a Default Gateway assigned. It is possible, and sometimes recommended to assign a Default Gateway to only 1 network card: the network card which is connected somehow to the rest of the company or the internet.

In this example, the Farm network is not connected to the rest of the company, and is not connected to the internet. Such a configuration can be considered as "more secure". Because the Farm network is not connected to the rest of the company or the internet, the Farm network card does not need a Default Gateway.

AADServer WXP Farm network card

AADServer Win10 Farm network card

Preferred DNS server

Both the Clients and Farm network card needs a Preferred DNS Server.

• The Domain Controller on the 10.x.x.x network does include a DNS server. The AADServers do need to find and use the Domain Controller and its DNS function. Otherwise the AADServer would not be able to find and join the Domain with the name "ipc.w2k3domain.intern".
• The AADServers and the Clients are connected to the company and the internet thru the 192.168.x.x network. This network has a router / DNS server with the IP address 192.168.200.124.

(it is theoretically possible to "copy" all DNS entries from the Domain Controller in the 10.x.x.x network, and copy them to the DNS server in the 192.168.x.x network, but that is just "more" work and not very convenient...)