This message was deleted.

they definitely named that reg key correctly,that's for sure.

LOL yea, I thought the samething.

What the heck? Will we never be free of the grace period RDS bomb?

Probably not lol

dumb question, but i thought it was standard practice to reset the RDS bomb on reseal.

only b/c it's a ticking timebomb 🙂

thats what i mean. we've been doing it since server 2016 for that very reason.

@Paul Brown no doubt, but even experienced teams get caught by this if the image isn't touched within 90 days.

To be honest, I never had to do this. But that doesn't mean it's not needed. I run BIS-F any where I can. I looked at the doc, and I don't see it. So I will be added this to my list of things.

"Grace Period Fix for RDS" is listed as one of the out the box optimizations of BIS-F. I don't use it so can't talk about that particular step - heard great things about the framework in here though.

Okay, Let me go back to the docs, I guess I overlooked that

the basic reseal script we run deletes this: "HKLM\System\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod" via psexec running as system, since standard accounts don't have the rights to delete it.

I delete the timebomb value on my 2016 images but I'm having luck with setting the RDS licensing information in local group policy on my 2022 images. I no longer get the grace period message when logging on as a local admin.