Remote Desktop Connection Broker – Events 1306, 1296, 1280, 802

This started out as an issue with the 120 day grace period expiring.  I went into the Remote Desktop Licensing Manager and added the Microsoft Open agreement with the RDS CAL’s.
I noticed there was a yellow explanation point in the RDS licensing screen, and had the following warning.
The license server is not a member of the Terminal Service License Servers group in Active Direectory Domain Services.  The license server will not be able to issue RDS Per User CALs to users in the domain, and you will not be able to track or report the usage of RDS Per User CALs on this license server.  Clicked Add to Group, Click Continue.


RD Connection Broker failed to process the connection request for domain/user
Remote Desktop Services failed to join the Connection Broker on server RDS.domain.  Error: Current async message was dropped by async dispatcher, because there is a new message which will override the current one.
Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.  Error: Element not found.
Remote Desktop Connection Broker Client failed to redirect the user domainuser.  Error: NULL

Finding destination computer…



Troubleshooting with MS

  1. Create a test admin account, on the RDS server connected to ‘localhost’ and used test admin account, that worked fine.
  2. Modify Group Policy RDS Licensing, set name, and user CALs
  3. Restart RDS services
  4. Reboot Server
  5. Still getting error “Licenses are not available for this Remote Desktop Session Host server, and RD Licensing Diagnoser has identified licensing RD Session Host server.
  6. works with mstsc /admin which allows it to connect without certs
  7. Modified the group policies for licensing server, licensing mode
  8. Licensing issues still
  9. net stop termservlicensing
  10. c windows system32.lserver.old
  11. create new lserver folder, change permissions
  12. network service full control
  13. net start termservlicensing
  14. licmgr, add licesning again
  15. Delete all certificate entries from RCM key, reboot
  16. remove incorrect certificate in cert MMC
  17. Modify the following registry
  18. HKLM – System – Current Control Set – Control – Terminal Server – WinStations – RDP-TCP – Security Layer changed from 1 to 0

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s