Activation Script - Rearm

[Patrick]

Due to an expired or now invalid VLSC agreement at a school, a lot of the PC's are in a non genuine state. I've been asked to sort this with a new agreement MAK key. So, i'm trying to knock together a script that will rearm the activation period, and then at the next boot install and activate the new MAK. I'm a long way from a programmer/coder so i could do with some help on my scripts syntax/cmd's. I've hashed out how i think the script should look, but just need help with using the proper commands and syntax, or if i'm going in the complete wrong direction

 

IF C:\activated.txt exists EXIT

IF C:\rearm.txt exists then;

 

{

slmgr /IPK XXXXXXXXXXXXXXXXXXXX

slmgr/ato

}

 

else;

{

slmgr /rearm

cd C:\

dir > rearm.txt

dir > activated.txt

}

 

Exit

 

Any help is much appreciated.

Edited March 20, 2019 by Patrick

[network41]

Can u not just run SLMGR -REARM or am I missing something

[lionsl2005]

Due to an expired or now invalid VLSC agreement at a school, a lot of the PC's are in a non genuine state. I've been asked to sort this with a new agreement MAK key. So, i'm trying to knock together a script that will rearm the activation period, and then at the next boot install and activate the new MAK. I'm a long way from a programmer/coder so i could do with some help on my scripts syntax/cmd's. I've hashed out how i think the script should look, but just need help with using the proper commands and syntax, or if i'm going in the complete wrong direction

 

 

Any help is much appreciated.

 

I believe these are not Win 7 PCs. I have seen couple of schools had this issue. Microsoft black listed the current keys and need to reactivate the Windows. Even used the new valid keys which reported windows could not verify the key due to a windows update.

[Patrick]

Can u not just run SLMGR -REARM or am I missing something

 

After the rearm i need to reboot in order to input the new key. The old key is invalid and now blacklisted by MS.

[mowgli82]

I didn't realise Microsoft blocked the keys from invalid VLSC agreements.

[round2it]

I had something similar the other day on the priniples machine

it turned out that a windows update broke activation

[atcoates]

I've had this on at least 5% of machines at each site I manage. MS have invalidated all old MAK codes so only current ones work. Luckily I used the VAMT to replace all the machines that still showed as genuine but for others I've had to use two .bat files. Anyone that can put this into one script that reboots after the msupdate uninstalls and carry's on I'd appreciate.

 

@echo off

wusa /uninstall /kb:971033 /forcerestart

 

Reboot and then run this.

 

net stop sppuinotify

sc config sppuinotify start= disabled

net stop sppsvc

del %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-0.C7483456-A289-439d-8115-601632D005A0 /ah

del %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-1.C7483456-A289-439d-8115-601632D005A0 /ah

del %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\tokens.dat

del %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\cache\cache.dat

net start sppsvc

cscript c:\windows\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

cscript c:\windows\system32\slmgr.vbs /ato

sc config sppuinotify start= demand

shutdown.exe -r -t 10

[atcoates]

I didn't realise Microsoft blocked the keys from invalid VLSC agreements.

I think this is a new thing as we've had keys from dead agreements in machines for years with no issues...until now. I think it's the same for Office keys as well.

[Patrick]

Yeah, they've changed their policy that old keys on expired agreements are no longer valid.

[lionsl2005]

Yes, MS Update Broke the Activation.

 

Copy the Script and past it in a Notepad and save it as .bat file. Edit the file and insert your valid Key where (FFFFF-FFFFF-FFFFF-FFFFF-FFFFF) Please run this as a batch file. Thanks to my Friend Rob for the Script.

 

:: rp - fEB 19

:: Fix Win 7 Issues of activation after the MS update KB971033

::

wusa /uninstall /kb:971033

::

dism /online /Remove-Package /PackageName:Microsoft-Windows-Security-WindowsActivationTechnologies-Package~31bf3856ad364e35~amd64~~7.1.7600.16395

::

net stop sppuinotify

::

sc config sppuinotify start= disabled

::

net stop sppsvc

::

del %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-0.C7483456-A289-439d-8115-601632D005A0 /ah

::

del %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-1.C7483456-A289-439d-8115-601632D005A0 /ah

::

del %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\tokens.dat

::

del %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\cache\cache.dat

::

net start sppsvc

:: Note You need to replace the WINDOWS 7 PRO key in the note below!!!

cscript c:\windows\system32\slmgr.vbs /ipk FFFFF-FFFFF-FFFFF-FFFFF-FFFFF

::

cscript c:\windows\system32\slmgr.vbs /ato

::

sc config sppuinotify start= demand

::

EXIT

[mukz]

You can rearm, reboot and then activate as normal presuming you still have a VLSC agreement.