Windows Server 2008: Event ID 1019, 1016, or 1001 with a source of TerminalServices-SessionBroker or TerminalServices-SessionBroker-Client logged in the system event log of the Session Broker server or the Terminal Server There are several common issues that we see with Terminal Server Load Balancing, and scoping the issue will depend on the symptoms that you are experiencing: * Microsoft Network Load Balancing can still be used for Windows Server 2008 Terminal Servers although it is not necessary A Terminal Server Farm is often described as two or more Terminal Servers configured to use a Session Directory or Session Broker server and load balanced with either Microsoft NLB, DNS round-robin, or a third-party load balancer. Terminal Server Load Balancing refers to either Session Directory and Microsoft Network Load Balancing used with Windows Server 2003 Terminal Servers, or Session Broker used with Windows Server 2008 Terminal Servers*. First published on TECHNET on May 14, 2009
0 kommentar(er)
