Windows 7 Enterprise Activation

Please read the Help. It will tell you all you need to know and more.

(I have decided to have the task run on every bootup, not time/date based, because that way the task cannot be missed and it will run way more often too.)

It is already shown in the misc menu. IMO it is better to have it there because for one thing thats where you install/uninstall the schedule from and for another i wouldnt want the main-menu to be full of info some people might not even care about. (After all not everyone is going to use the scheduled task.)

Thats where it was at first, but i thought if i make a misc-menu anyway i might as well put everything thats not required for the actual activation in there so its sort of categorized.

Well the Event Viewer already has an Event Log for the Key Management Service but it is apparently not active. I have no idea why nor how to enable it, (at least not yet), and im not sure if i can do anything here via a simple CMD script either.

But then again, so far the scheduled task was always successful so its probably nothing to be concerned about anyway. After all it runs 5 requests in a row, plus error-check every request, so if your system is not one of those where it doesnt work no matter what you do then those 5 tries should always be more than sufficient.

The way i see it the worst thing that can happen is that it might occasionally fail on one day or another, but with a time-span-total of 180 days this should never ever become a problem since the next reboot will in all likelyhood already make up for it...

 

Update:

The Event Viewer supports commandline so technically the KMS event-log could be shown directly in the application.

The remaining question is: How to make Windows log any KMS events.

The log is 'enabled' under properties, but greyed out, so apparently something else has to be done to actually activate it...

 

You need to login to view this posts content.

 

8007232A Error

Hi,

First of all, thanks for this KMS Activator tool !

I'm facing a little problem though... everytime I try to do the activation, I get this error message :

Code:

KMS Server started and ready
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

Activating Windows Server(R), ServerEnterprise edition (620e2b3d-09e7-42fd-802
a-17a13652fe7a) ...
Error: 0x8007232A DNS server failure

My server is a Win2008 R2 Enterprise, which is a Domain Controller, and a DNS Server.
Do I have to add something in my DNS Server to make it work ?
I already tried, as found on many websites, to do a slmgr /ipk with the key installed by your utility, without success, and also tried removing it with a slmgr /upk.

I must add that while I was testing earlier, I always had the 8007232A error first, and then had the 8007232B until I did an ipconfig /flushdns, then A first and B again, but now I only have A.... without doing anything different than previously !

The KMS.exe exception is effective in the Firewall, and I checked in the logs, the packet is allowed, so not a problem here I presume.

Could someone please help ? Thanks !

Dje

 

You need to login to view this posts content.

 

Can you resolve localhost? And ping yourself at 127.0.0.1?

sebus

 

Djeross, if you still have that error, could you do a slmgr -dlv and post a screenshot of that?

I am trying to verify a theory as to why this fails on some installations...

 

You need to login to view this posts content.

 

Worked perfectly on a VMWare machine, now my questions are:

How long will the activation stay ? 180 days right ?

 

Yes correct, the system has to connect to the KMS server within 180 days to stay activated. If it connects to the KMS server earlier then the cycle starts again.

x-5

 

Which means that i have to run the kms activation every 180 days right ? or it stays memory resident and auto activate later ?

 

Yes, you'll have to do the activation process once every 180 days. If you keep this fake KMS server active all time, Windows will try to activate itself at a specific timeframe.

That's the way it works within a company which has it's own real KMS server running. Their servers will try to connect to their master KMS server and so the activation will stay alive as long as the server can reach the KMS server once every 180 days.

x-5

 

Then a good option would be to load the kms server at every startup no ?
But how to do that since the application is made from a menu ?

 

I see.

Then apparently it is not what i thought.

Thanks for posting the screenshots.

Install the schedule.

This will auto-start the KMS Server and run 5 activation requests every time you boot the computer.

Read the help for more info.

(Which by the way is generally a good tip. Please read the help, theres 9 pages of details.)

 

I would say this is an overkill to keep it running all the time when I would need it only once every 180 days.

The "ZWT keygen" is available without this additional menu too. So you could just use the keygen, and "slmgr -ato" to reactivate for the next 180 days or use a scheduled job for it.

x-5

 

Thanks a lot Phazor, installed the scheduler but during installation i get an error saying there was a problem updating my windows firewall (note that i executed the application as administrator)

I re-started the installation without launching it as admin and no errors, checked then the firewall rules and i see what the application added.

Thanks a lot again

 

Yeah, this can happen when an exception for KMS.exe already exists.

Happened to me too one time, but deleting the existing exception and re-running the installer fixed it.

 

Before i forget:

The other day i installed VAMT and noticed that it includes a lot of GVLKs for Office14.

Now since the server seems to activate all the other GVLKs, couldnt it be that it activates the Office ones too?

Did or can anyone try that? (Im not using Office myself.)

 

Oh ok, strange that there already was an entry, did a fresh win installation, but who cares, it works, i'll keep an eye to the activation and let you know in case of problem.
I'll also test everything on a W2k8 SRV