News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • Aug 2019 patch broke RDS CB

    Posted on sdsalsero Comment on the AskWoody Lounge

    Home Forums Admin IT Lounge Aug 2019 patch broke RDS CB

    Tagged: 

    This topic contains 4 replies, has 2 voices, and was last updated by  woody 5 days, 7 hours ago.

    • Author
      Posts
    • #1907848

      sdsalsero
      AskWoody Lounger

      Last night we upgraded our public-facing Server 2012R2-based RDS Gateway (GW) and Connection Broker (CB) servers to the brand-new Aug 2019 Rollup. Normally we wait at least a week before applying new patches but last night was already a scheduled maintenance window so we took a chance. And got burned.

      After the patching, no one could login. We use an RDP connection file which specifies the use of the GW and has the CB listed as the target system. You would be prompted to authenticate, i.e., I assume your login request was passing through the GW to the CB, but then there was a completely generic error, “Unable to connect.” Since we were under time-pressure I simply rolled-back the updates, and this restored access.

      I am still trying to analyze the logs; I’ll have more info later.

      Has anyone else applied these patches to their 2012 GW/CB successfully?

      1 user thanked author for this post.
    • #1907881

      sdsalsero
      AskWoody Lounger

      Follow-up:

      On the CB’s Windows Event application log,
      Microsoft-Windows-TerminalServices-SessionBroker-Client/Operational

      There are repeating pairs of 1306/1296 errors:

      1306, “RD Connection Broker Client processes request from a user”
      “Remote Desktop Connection Broker Client failed to redirect the user. Error: NULL”

      1296, “RD Connection Broker Client processes request from a user”
      “Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker. Error: Remote Desktop Connection Broker is not ready for RPC communication.”
      ________________________

      My initial research says that this can be caused by the Remote Desktop Connection Broker service (“tssdis”) not running; I regret that I did not check this before rolling-back the update last night.

      • This reply was modified 5 days, 8 hours ago by  sdsalsero.
      1 user thanked author for this post.
      • #1907897

        woody
        Da Boss

        Are you installing the Monthly Rollup or the Security-only update?

        • #1907901

          sdsalsero
          AskWoody Lounger

          the full Monthly Rollup

          1 user thanked author for this post.
    • #1907947

      woody
      Da Boss

    The topic ‘Aug 2019 patch broke RDS CB’ is closed to new replies.