NLB on Session Broker

[Morten]

Hi,

I'm wondering if it isn't considered best practice to set up NLB on the
session broker? In other words set up 2 servers in a cluster to get high
availability. I don't see this described in any of the articles I've read
but it seems to make sense. Has anybody done this and is it a problem?

Thanks in advance
Morten

 

[Davide Bertarelli]

Hi Morten, I have the seme problem and the same doubt...

I have a Test Lab configuration using two 2008 R2 Servers with RD Web+RD Gateway+RD Brober and other two Servers with RD Session Host for applications.

On the first couple of servers I have created one NLB cluster (Multiple Server, secondary IP address, port 443, Affinity None) for IIS (HTTPS) traffic, and a second NLB cluster (Single Server, third IP address, All ports) for Session Broker service.

Then I have created a DNS static entry for my NLB Session Broker cluster (broker.test.lan), and in RemotApp Manager and Session Host manager configuration I have used this FQDN to indicate my session broker "server".

In this way (using NLB cluster in Single Server Mode) only one server are used to store users sessions, but if that server crash, or is off-line, the other member of the NLB cluster it's able to serve Session Host requests.

Wath do you mean about this configuration?

Bye
Davide




Posted as a reply to:

NLB on Session Broker

Hi,

I'm wondering if it isn't considered best practice to set up NLB on the
session broker? In other words set up 2 servers in a cluster to get high
availability. I don't see this described in any of the articles I've read
but it seems to make sense. Has anybody done this and is it a problem?

Thanks in advance
Morten

EggHeadCafe - Software Developer Portal of Choice
WCF Workflow Services Using External Data Exchange
http://www.eggheadcafe.com/tutorials/aspne...rvices-usi.aspx

 

[Davide Bertarelli]

It seems it's not a valid idea for RD Web Access Configuration. I'm not able to use the Session Broker NLB FQDN in RD Web Access administration configuration web interface, because the FQDN it's not a computer account in TS Web Access group. :-(

"RD Web Access was not able to access the RD Connection Broker server specified. Ensure that the computer account of the RD Web Access server is a member of the TS Web Access Computer security group on the RD Connection Broker server"

Any Idea?



Posted as a reply to:

NLB on Session Broker

Hi Morten, I have the seme problem and the same doubt...

I have a Test Lab configuration using two 2008 R2 Servers with RD Web+RD Gateway+RD Brober and other two Servers with RD Session Host for applications.

On the first couple of servers I have created one NLB cluster (Multiple Server, secondary IP address, port 443, Affinity None) for IIS (HTTPS) traffic, and a second NLB cluster (Single Server, third IP address, All ports) for Session Broker service.

Then I have created a DNS static entry for my NLB Session Broker cluster (broker.test.lan), and in RemotApp Manager and Session Host manager configuration I have used this FQDN to indicate my session broker "server".

In this way (using NLB cluster in Single Server Mode) only one server are used to store users sessions, but if that server crash, or is off-line, the other member of the NLB cluster it's able to serve Session Host requests.

Wath do you mean about this configuration?

Bye
Davide

EggHeadCafe - Software Developer Portal of Choice
WCF Workflow Services Using External Data Exchange
http://www.eggheadcafe.com/tutorials/aspne...rvices-usi.aspx