• Report that Server 2012 R2 Monthly Rollup KB 4512488 breaks RDP login

    Reader @sdsalsero reports:

    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. 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.”

    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.”

    Anybody else hitting that problem?