Applies To: Windows 8.1, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2
Timeout setting specifies the number of seconds for which the client affinity (either single or network) would be preserved across configuration changes in the Network Load Balancing cluster.
Client affinity is used to associate client requests to cluster hosts.
By default, all network requests are load-balanced across the cluster without respect to their source. Affinity is implemented by directing all client requests from the same IP address to the same cluster host.
When extended client affinity is specified, then after a network connection terminates, it retains ownership of a connection for a configurable amount of time. Requests coming in from the same client during the timeout period are guaranteed to be picked up by the same cluster host. After this time expires, the connection is released.
- This setting will be applied only if the ClientAffinity setting is set to
- To enable this Network Load Balancing setting, the NetworkLoadBalancingFullServer package must be enabled in the Windows® image you are installing. To do this, use Windows System Image Manager to add the Microsoft-Windows-Foundation-Package to your answer file, and then configure the NetworkLoadBalancingFullServer package to enable it. For more information about adding and configuring packages, see the Windows® Assessment and Deployment (Windows ADK) Technical Reference.
Specifies a number of seconds for extended client affinity. During this time, requests coming in from the same client are guaranteed to be picked up by the same cluster host.
Number_of_seconds is an integer value.
The default value is 0, meaning extended affinity is not used. All network requests are load-balanced across the cluster without respect to their source.
For the list of the supported Windows editions and architectures that this component supports, see Microsoft-Windows-NetworkLoadBalancing-Core.
The following XML example shows how to set the network so that requests from the same client are guaranteed to be picked up by the same cluster host until a timeout period of 15 minutes expires.