none
RD Connection Broker issue RRS feed

  • Question

  • Hi

    From time to time we have BSOD on Session Host servers. Users which had sessions on these server can't reconect to another Session Host server, because Connection Broker redirects them to inaccessible server. It lasts about 30 minutes.

    Is some way to "inform" Connection Broker that Session Host is unavailable now? Or reduce time out?


    • Edited by Yurko__ Friday, September 6, 2019 7:23 AM mistake
    Thursday, September 5, 2019 1:27 PM

All replies

  • HI
    1 what's this phrase "we have BSON on Session Host servers" mean ?
    2 can you detail explain what's your rds deployment ?
    3 are all your session host servers in the same collection ?
    4 if the user logoff the first session host then connect to the other session host ,will the problem persist ?
    5 did you build RDS farm and use DNS round robin in your RDS environment ?
      For example: rdsh1.mydomain.com 192.168.2.2
                         
      rdsh2.mydomain.com 192.168.2.3
      rds farm name: rdsfarm.mydomain.com
    dns round robin :rdsfarm.mydomain.com   192.168.2.2
                              rdsfarm.mydomain.com 192.168.2.3
                                                               


    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Friday, September 6, 2019 7:03 AM
    Moderator
  • 1. BSON - BSOD, typo, sorry

    2. Environment: RD Connection Broker and few RD Session Hosts in one collection, based on Windows Server 2012 R2

    4. User can't logoff session, because Session Host freezes.

    5. Use DNS round robin only for Connection Broker record.

    Friday, September 6, 2019 7:31 AM
  • HI
    6 If there is a method can logoff all users' session on problematical rdsh server ,will it can solve your issue ?
    Force a user logoff remotely with PowerShell
    https://www.heelpbook.net/2018/force-a-user-logoff-remotely-with-powershell/

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Tuesday, September 10, 2019 3:31 PM
    Moderator
  • Problematic server has fatal system error (BSOD).

    How users could be logoff from server which was crash?

    • Edited by Yurko__ Thursday, September 12, 2019 9:33 AM
    Thursday, September 12, 2019 9:29 AM
  • HI
    For example 
    there are AD accounts :testa and testb have been logged on RDSH 2 .
    will the below powershell cmmand(run as admin) be use to log off the test users on your RDCB(RDS management server) when the RDSH2 went to BOSD ?
    $username = "testa",“testb”
    foreach ($row in $username)
    {$sessionId = ((quser /server:rdsh2.printer.local| Where-Object { $_ -match $row }) -split ‘ +’)[2]
    Invoke-RDUserLogoff -HostServer "rdsh2.printer.local" -unifiedsessionid $sessionId
    }


    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Monday, September 16, 2019 3:38 PM
    Moderator
  • I have test it, but quser command returns error:

    Error 0x000006BA enumerating sessionnames
    Error [1722]:The RPC server is unavailable.

    I think this issue shoul be resolved on Connection Broker, should be some way to inform CB that RDSH is unavailable.


    • Edited by Yurko__ Tuesday, September 17, 2019 12:56 PM
    Tuesday, September 17, 2019 8:34 AM
  • HI
    8 if you set Keep-Alive interval to 1 on frequent BOSD session host sever, when the BOSD happen on session host server again ,will your issue persist ?
    Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connection
    In the Configure keep-alive connection interval dialog, select Enabled and set the Keep-Alive interval to 1 (default).
    Remote Desktop Connections Keep Alive
    https://jbcomp.com/keeping-remote-desktop-connections-alive/

    Please Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

     



    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.



    Thursday, September 26, 2019 6:39 AM
    Moderator
  • HI
    Is there any progress on your question?

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Sunday, October 6, 2019 8:20 AM
    Moderator