Forum Discussion

Sascha Stops's avatar
Sascha Stops
Brass Contributor
Nov 13, 2019
Solved

Users are getting license warning and are disconnected after 60 minutes from WVD

Hello,   we have a situation that two minutes after logging into a WVD session (Win 10 1903 multi-user), users are getting a warning about an invalid license and they will be logged off after 60 mi...
  • PieterWigleven's avatar
    PieterWigleven
    Nov 25, 2019

    Sascha Stops This is a known issue and we are updating our documentation while working on a fix. The fix will take a couple of weeks, probably looking at early 2020. I'd recommend to redeploy the 1903 (or 1909) hosts where the grace period will be long enough to bridge the gap until the fix is pushed via Windows Update. Sorry for the inconvenience. 

Nicholas Semenkovich's avatar
Nicholas Semenkovich
Brass Contributor
Nov 26, 2019

Sascha Stops Any luck? Supposedly you can reset the timer by deleting a GracePeriod registry key (under 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod').

 

That might hold us over until a fix is released: https://www.hyper-v.io/reset-120-day-rds-grace-period-windows-server-2016-without-gui/

 

For those debugging this, we found that we have only 15 days remaining before we hit this bug. You can see remaining time by running, in an elevated powershell:

 

(Invoke-WmiMethod -PATH (gwmi -namespace root\cimv2\terminalservices -class win32_terminalservicesetting).__PATH -name GetGracePeriodDays).daysleft

 

  • Mtollex70's avatar
    Mtollex70
    Brass Contributor
    Jan 10, 2020

    Nicholas Semenkovich I've tried that command to find the grace days, it says 469... 🙂 We are getting the license errors and MS Support confirmes we are indeed effected by this bug, but the errors are only in the event logs and users are not effected. Just a little curious about the 469 grace days... 

  • Sascha Stops's avatar
    Sascha Stops
    Brass Contributor
    Nov 28, 2019

    Nicholas Semenkovich  That seems to work. At least it will give us some time to rebuild the servers with all legacy applications.

     

    Best regards

    Sascha

    • Nicholas Semenkovich's avatar
      Nicholas Semenkovich
      Brass Contributor
      Nov 28, 2019

      Sascha Stops Thanks for letting me know! We'll probably do the same until the fix rolls out.

      • knowlite's avatar
        knowlite
        Iron Contributor
        Dec 09, 2019
        Having the same issue on deployment made this weekend.
        Users getting notification that they will be logged out in 2 minutes.
        Following eventlog: (sorry for dutch)
        Er kunnen geen licentiegegevens voor gebruikers door de Extern bureaublad-sessiehostserver uit AAD worden opgehaald. Fout User DOMAIN\user , hr = 0x80070057

        Er kunnen geen licentiegegevens voor gebruikers door de Extern bureaublad-sessiehostserver uit AAD worden opgehaald. Fout CheckLicensingFromAAD - Read AccessToken Failed: hr = 0x80070057
  • Sascha Stops's avatar
    Sascha Stops
    Brass Contributor
    Nov 26, 2019

    Nicholas Semenkovich  Hello, I have been told by the support engineer that there might be long term problems doing this. But I guess it does not matter if we rebuild now or later.

     

    I might give that a try one of the two host groups.

     

    Thank you for your response. 

     

    Best regards

    Sascha

Resources