When running in environment using Connection broker. How to give one specific user access to a specific RDSH server
hi
i have done quite a few implementation of rdfarm - using connection broker.
it works fine, there 1 thing anoying.
especially when testing or reconfiguring, need give specific user access specific rdsh server. how can acomplish this, without changing running environment? know can remove dns-rr, remove server security group, reboot rdsh server. clumsy way.
can tell me if there workaround - so i easyly can make sure 1 specific user connected specific rdsh server. in other words, i want overrule connection broker without interfering running environment.
looking forward genious workarounds :-)
have nice day
-thomas
hi thomas,
since using dns-rr "load balance" initial rd session host connect to, have load balance function of rd connection broker enabled or disabled?
here's happens, user connects using dns-rr , gets connected 1 of rd session hosts based on dns-rr mechanism. since rd session host member of rd connection broker farm, contact rd connection broker farm check whether sessions should redirected different rd session host 1 connected to.
rd connection broker redirect session in following scenarios:
1. user has disconnected session on 1 of rd session host servers. if so, rd connection broker make sure user gets redirected disconnected session
2. load balancing feature of rd connection broker enabled. if so, rd connection broker will, based on internal connection list, decide server has least load (in other words least amount of sessions). if server not connected server dns-rr handed back, user redirected server least load.
so in other scenarios, when either load balancing feature of rd connector broker not enabled or server least load happens same rd session host handed out dns-rr user not redirected.
in other words, if disable load balancing feature of rd connection broker, user in question not have disconnected session left open , let him connect rd session host directly achieve want.
note generates pitfalls. load balancing feature of rd connection broker disabled load less evenly spread on rd session host servers, because dns-rr no load evaluation , returns dns records in round robin. issues dns caching etc. have effect on this. furthermore, allowing users connect specific server cause less evenly spread sessions. if tell user can connect host correct while doing testing, after testing (whether or not on purpose) connect directly instead of using rr-dns. (users users :-)
there other load balancing options available gain flexibility in regards temporarily adding / removing hosts load balancing. example, nlb or hardware load balancer. however, before looking take in mind nlb adds other (network related) issues , complexity , hardware load balancer adds additional costs.
kind regards,
freek berson
Windows Server > Remote Desktop Services (Terminal Services)
Comments
Post a Comment