This message was deleted.

We clear the reg key as part of every reseal. Since we will patch every month it should never get past a 90 day threshold

Have a script that runs during shutdown to seal image. Calls psexec to delete the grace period key as the system account. “psexec -s -i reg delete [reg item]” Script has other things going on but that is one part of it.

Or just change perms in the image so admins have rights to clear it

Yeah cool, I do all that. The problem happens when you hit 120 days of uptime. Once you delete the value from the registry, the only way to reinitialise it is to restart the machine. The issue won't go away unless the machine is restarted so a new value is created.

I think we all assumed you were licensed.

We are absolutely licensed. There seems to be a bug in 2016 (same as 2012R2), where when uptime hits 120 days, the time bomb kicks in. It's not consistent, as it's happened across some machines in two different pools all built from the same PVS image, but not all. None of the machines have any connectivity issues to the license server. It's a weird issue. Probably rarely seen due to the long uptime we've hit on these two pools.

Do you have the local group policy on the image configured with the RDS license host and license type? Do you also have a group policy with the same? Putting it another way, with that all configured and the above reseal script i mentioned earlier we don't have the issue you are facing, because the clock on the timebomb does not start..

We have not found a way to refresh timer once it goes boom without kicking users. Which is why we make sure it is a process at the end of every image update

Strange, we manage a lot of PVS environments but very rarely face this issue.

Cool. Thanks @Hal Lange. I've added that process back in now. @Dennis, you may only see it if you allow the uptime to hit 120 days, so I shouldn't expect it happens often. I just got caught out this time because I was spinning too many plates.