This message was deleted.

The only time I see it is when the GPO is not applied for the RDS Licensing server in the RDSH/XA area here " HKLM\SOftware\Polices\Microsoft\Windows NT\Terminal Services

And it is for my latest case. I have a theory that once the grace period expires legitimately, something else is set that causes RDS to assume it is unlicensed rather than look at that registry key.

That is so strange

I have also seen a properly licensed XenApp server pop up a message about it not being licensed for the local Administrator account, but not domain users or administrators.

Use bis-f and this killed the timebomb reg key 😅

Oh no! 😨 Being part of BIS-F, that tells me this is common and deleting the key is the best remedy.

BIS-F deletes the key? Or you saying add it to do that?

one step of bis-f is killing this reg key. I can send u a screenshot with this Part later ray 😅

Thanks man. I never acutally knew it did that. Or I never paid attention

This has been a plague for us too. Happened on 2012R2 and 2016 and I'm going to assume 2019 (although we haven't got any VDA's in production yet). We had to delete the key as part of the PVS reseal process and with App Layering we have to do the same on the Platform before it runs out. We've opened tickets with Microsoft and their suggestion was to create a cluster for our RDS license servers. This doesn't address the issue. I'd love to hear someone figured this out. Deleting the key within 120 days seems to be the only fix.

For those of us with this problem, does your image have this reg value set to 1? [HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server] Name=fDenyTSConnectionsBackup REG_DWORD 1 I have 4 images and my problem child has this set to 1. My other 3 have 0. My google-fu finds nothing about this value.

Not just fDenyTSConnections, but there's another value called fDenyTSConnectionsBackup

yes, we have the same behavior. with TS-Server 2016, at the moment Server 2019 is good. we do a complete restaging of the system, all strange to me. but as i can see, solution is to delete TimeBomb reg value. thx

Where did that backup value come from?

@Ray Davis, I have Server 2016 images. I don't have anything else to compare it to if it's there for 2019 and 2022. But the value exists on all 4 images I manage.

Right on man, well good find though.

I just don't know what it does. If it is benign or operates as some sort of fall back for RDS. It bugs me that deleting a reg value that should have no bearing on a RDS server once it is licensed fixes a license issue every 120 days.