none
Strange Events Logged on my Windows 2008 R2 Connection Broker Server

    Question

  • Hello and Good Morning Microsoft Community....

    My organization is doing preliminary testing with upgrading our Widows 2003  Terminal Servers to Windows 2008 R2 Remote Desktop Session Hosts....

    Including the update to the RDS servers themselves, we are now using Remote Desktop Connection Broker, instead of the Window 2003 equivalent Session Directory

    In our 2008 R2 test environment, we have 5 Windows 2008 R2 RDS servers in a farm. They are load balanced by a F5 LTM appliance. We do not use NLB, and we do not use the built in Connection Broker load balancing. Throughout the day, we see this error on the Connection\Session Broker server:

    Event ID 802

    Source: Terminal Services - Session Broker

    Description: RD Connection Broker failed to process the connection request for user domain\Username. Load balancing failed OR specified endpoint could not be found. HRESULT = x80070515.

    Now, I have tested several times that Session Broker is indeed doing what I want it to do, with is direct users to a disconnected session if one exists. I am just not sure why this error pops up on the Session Broker server. (the log is the Microsoft - Windows - TerminalServices-SessionBroker-Operational.) We limit the number of Remote Desktop sessions to 1 on each server via group policy. We have disabled the "Use RD Session Broker Load Balancing". via GPO in Computer Settings - Administrative Templates - Windows Components -Remote Desktop Services - Remote Desktop Session Host -RD Connection Broker. We also via GP, have the Session Broker server selected, and all servers are specifying the same Session Broker Farm Name. All RDS servers in the Farm are member of the "Session Broker Computers" local group on the Session Directory Server.

    Is anyone else getting this on theri Session Broker server? Any ideas on how to get rid of the error?

    -Harold

     

    Friday, February 15, 2013 2:44 PM

Answers

  • Hi,

    The issue may be related to your load balancer.Pls try to use the built-in Connection Broker load balancing with round robin to test whether it works.

    Regards,

    Clarence

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedbackhere.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Monday, February 18, 2013 9:26 AM