Rearming Windows Server 2016 pass it's maximum rearm count period?

can anyone post the script...thanx

 

Just look better and You will find script.

 

I see it #13

 

Off topic but when is MS going to start IP with gui servers? Any news?

 

Probably shortly before the next LTSC server hits. 2021 or 2022.

 

This Script Will Reset Rearm Count As Well In Windows Server 2016?

 

I send pm my buddy

 

confirmed working on windows 10 education 1909.
it would be nice to be able to run it in windows preboot environment before windows starts

 

slmgr -rearm
How many times can you use it with newer Windows 10 versions and for how long in total?

 

It should be 3 times.
A little known fact is that after reaching the maximum count, a single KMS activation would allow another rearm.
This is very useful when sysprepping images updated in place each time.

 

And the script in post #13 for older versions.
How many rearms?

 

Windows 8 and 10 do not have Grace Period, you can rearm 100 time without any use

the script in post #13 only reset the rearm count

 

Does that apply only to Enterprise though? Windows 7 Enterprise would also work without activation, but with black desktop.

 

All Windows 7 editions has grace period
the activation nag won't be just black desktop

 

Just tried running the script as an Administrator on a Windows Server 2019 Datacenter edition and I'm getting multiple "access denied" errors. It looks like this error is being raised during the following loop:

for /f %%i in ('reg query HKLM\SYSTEM\WPA') do reg delete "%%i" /f

If I try to manually delete the keys in "HKLM\SYSTEM\WPA" then I get a "Cannot delete...Error while deleting key" error message.

Is this script not supported on Server 2019?

 

You might need Trusted Installer rights for that key. Check out the "RunAsTI" script from @AveYo.

 

Thanks, Carlos. I just installed the script from @AveYo and when I ran the command file as a Trusted Installer I received the same access denied errors as it attempted to delete those keys.

Could this be some additional lockdown in Server 2019 for that "HKLM\SYSTEM\WPA" area?

 

"HKLM\SYSTEM\WPA" is THE SINGLE MOST PROTECTED key in updated windows. It's locked early in the boot process and literally nothing can unlock it once done.
But I guess you can still manipulate it offline. Or use outdated windows version

 

Running WinPE, loading the Hive there, manipulating the key, and unloading the Hive again is the way to go in this case.

It's the activation system. What did you expect?

 

Perhaps kernel protected keys are not a novelty.

Try to change online the "MediaCenterInstalled" key, if you can.