Bilgisayarımızda uzak masaütsü bağlantısı sürekli kopuyor

Fatih Ozturk 0 Reputation points
2026-06-05T10:52:40.7166667+00:00

Termianl server lisansımızomasına rağmen ekteki hataları alıyoruz

WhatsApp Image 2026-06-05 at 13.32.14

WhatsApp Image 2026-06-05 at 13.37.13

Windows for business | Windows Client for IT Pros | User experience | Remote desktop clients
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. VPHAN 42,485 Reputation points Independent Advisor
    2026-06-20T05:16:02.1033333+00:00

    Hi Fatih Ozturk,

    Has your issue been resolved yet? If it has, please consider accepting the answer as it helps others sharing the same problem benefit too. Thank you :)

    VPHAN

    Was this answer helpful?

    0 comments
  2. VPHAN 42,485 Reputation points Independent Advisor
    2026-06-05T11:34:46.8733333+00:00

    Hi Fatih Ozturk,

    The 60-minute disconnection warning typically stems from a communication failure between your Remote Desktop Session Host and the Remote Desktop Licensing Server. You can resolve this by opening the Local Group Policy Editor and navigating through Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, and into the Licensing folder. Here, explicitly enable the policy to specify the Remote Desktop license servers using your server's exact IP or hostname, and set the licensing mode to match your purchased Per User or Per Device Client Access Licenses.

    If you have configured the Group Policy and the 60-minute error persists, your server is likely experiencing a known Windows bug where it caches an expired 120-day evaluation state even after valid licenses are installed. To clear this bugged cache, open the Registry Editor and navigate to HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Control, Terminal Server, RCM, and locate the GracePeriod key. Because this is a protected system directory, you must right-click the GracePeriod key, take ownership to grant your administrator account full control, and then delete the binary value located inside. Rebooting the server afterward will force the operating system to discard the trial status and successfully query your valid licensing certificates.

    The second error indicating that the total logon time limit was reached is controlled by administrative session duration policies rather than your terminal server licenses. To correct this, return to the Remote Desktop Session Host directory within the Local Group Policy Editor and access the Session Time Limits folder. Modify the policies governing active and idle Remote Desktop Services sessions, setting them to "Never" or a specific timeframe that aligns with your enterprise operations. This will stop the server from automatically terminating authenticated user sessions based on strict duration limits.

    Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.

    VPHAN

    Was this answer helpful?

    0 comments

  3. AI answer

    2026-06-05T10:53:01.03+00:00

    The messages indicate that Remote Desktop Services (Terminal Services) licensing on the server is not working correctly. Even though licenses exist, the server is treating the connections as having “license issues” and is enforcing a time limit, then disconnecting sessions.

    From the provided context, this behavior matches scenarios where the Remote Desktop/Terminal Services license certificate or licensing configuration is corrupted or the RD Session Host cannot correctly use the license server.

    Recommended checks and fixes on the Remote Desktop (RD Session Host) and license server side:

    1. Verify licensing-related events
      • On the RD Session Host server, check Event Viewer under:
        • Applications and Services Logs → Microsoft → Windows → RemoteApp and Desktop Connections
        • Applications and Services Logs → Microsoft → Windows → TerminalServices-LocalSessionManager
        • Applications and Services Logs → Microsoft → Windows → TerminalServices-RemoteSessionManager
      • On the RD License Server, check:
        • Applications and Services Logs → Microsoft → Windows → TerminalServices-Licensing
      • Look for events such as:
        • Event ID 1088 from TermService indicating the licensing grace period has expired and the server has not registered with a license server.
        • Event ID 1004, 1010, or 28 indicating the terminal server cannot issue a client license or cannot locate a license server.
    2. Confirm that the RD License Server is reachable and running
      • Ensure the Terminal Services/Remote Desktop Licensing service is running on the license server.
      • Confirm the license server is correctly registered in DNS/WINS and accepting network requests.
      • Make sure the RD Session Host is configured to use this license server and the correct licensing mode (Per User / Per Device) in Remote Desktop Services configuration.
    3. Repair possible license certificate corruption on the RD Session Host
      • Back up the registry on the RD Session Host.
      • In Registry Editor, export the key:
        • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\
      • Under the Parameters subkey, delete these values if present:
        • Certificate
        • X509 Certificate
        • X509 Certificate ID
      • Restart the RD Session Host server.
      • After restart, reactivate the Terminal Services/Remote Desktop Licensing server (for older versions, use the Licensing Wizard and the telephone method as described in the documentation).
    4. Check the license database and temporary files on the license server
      • Licenses are stored in %systemroot%\system32\lserver\hydra.mdb.
      • Terminal Server License Manager may leave multiple JETx.TMP files in System32 if the server was shut down abruptly. If there are many leftover JET*.TMP files and they are not in use, they can be deleted; only closed files will be removed. This can help if licensing operations are failing due to stale temporary files.

    After these steps, new RDS CALs should be issued correctly and sessions should no longer be limited or disconnected due to licensing.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.