Ummm ... dosen't works for me for a Windows 2008 R2 standard ... Error returned is: "Error: 0x8007232B DNS name does not exist"
Yes. I have tried to use kms activator menu and "slmgr -ipk 'serial', slmgr /kms 127.0.0.1 and slmgr -ato" commands and same result ... But with another Windows 2008 R2 Enterprise works ok ...
Ok, finally it works ... I have reinstalled Windows 2008 R2 Std and using slmgr -ipk, slmgr /kms .. and slmgr -ato (after three tries) all works now ... But how can I schedule a task to do the same every 180 days and keep windows activated??
Well i could whip up an installer that installs the KMS executable along with a scheduled task. Would be no problem at all, but i dont know how much time i have during the next days. But if there is enough interest i would be willing do it as soon as i do have the time...
Nircmd doesn't work on 64-bit windows. I guess when we are close to day 180 we can just restart Phazor tool and run steps 2, 3 and 4. Is that correct ? Why do we need to start kms at boot ? Wouldn't be enough to have a scheduled task just warning the user that it's time for a new activation event ?
Installing a PKey and setting the IP has to be done only once, which leaves 3 and 4 for a revalidation. That is as of version 4.2 it is sufficient to just select 4, as 4 will start the server automatically if its not already running. In other words; if PKey and IP are already set you merely press 4 to start the KMS Server and initiate a activation request, and in option 4s submenu you press 1 in case the activation request has to be repeated. Since this only has to be done every 6 months i agree that a reminder would probably be sufficient too. After all it takes just a second.
I wonder if they will do this in the KB971033 update. Anyone tried installing this after using the ZWT KMS (or any other KMS activator)?
@ Phazor First of all a big thanks to phazor and of course ZWT for providing a gr8 sol. to activate offline but it will be even grrrr8 to develop the fully automatic sol. using scheduling services which will do all the tasks after every 140 days.
Im currently busy enhancing the app to support Vista as well (i actually didnt plan to but i found its a nice way to brush up on my CMD skills, so...), but like i said, if there is enough interest in the scheduled solution then im willing to do it as soon as i have the time...