Its good that u r enhancing the app futher but as you know that every body is not equally expert and for them it is difficult to reactivate again and again so, developing the automatic sol will help them and of course it is the interest of majority.
What i need right now to complete the current WIP is a Vista EnterpriseN GVLK key. If anyone has one, please post it so i can debug and finish 5.0. When 5.0 is completed i can start concepting the other thing.
Failure with error 0xC004F074 I finally tried on a freshly installed Enterprise x64 (installed on a 2nd HD in dual booting config. with XP 32). First applied all updates. I did not activate the trial. Then I used Phazor's tool, executing all the steps one by one. All went fine until the activation. I get this error: "KMS Server started and ready Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. Activating Windows(R) 7, Enterprise edition (ae2ee509-1b34-41c0-acb7-6d4650168915) ... Error: 0xC004F074 The Software Licensing Service reported that the computer could not be activated. The Key Management Service (KMS) is unavailable" I checked with the network performance tool and kms.exe was up and running, with no firewall restriction and listening on port 1688. Yet no way to get activation. Always the same error 0xC004F074. I also tried all other tricks described in the help and throughout this thread. No way. The machine stubbornly gives the same error and stays in grace state. MS info says that error 0xC004F074 often occurs when the host is server 2003 and they provide updates to fix the problem, but we can't "update" the mock server from ZWT, of course. I can't really try activating with an external server, because the machine is behind a company firewall that blocks all outbound connections except those on port 80. Has anybody encountered this type of error yet ?
From my experience with actual KMS hosts, 0xC004F074 is usually caused by time mismatch between the client and the KMS host. Shouldn't be the case for ZWT-keygen, if I understand correctly. I'd suggest you to probe port 1688 of the KMS host with telnet first. Use "telnet localhost 1688" if you run ZWT-keygen locally. If telnet connection fails with timeout, you've got a communication problem somewhere.
This sounds like sound advice. I am still convinced that failures, if/when they occur, are most likely due to a momentary (or general) malfunction in the network communication...
No it's not so simple... I reformatted and reinstalled a fresh copy of Enterprise (this is a genuine iso directly from MS - HSChronic !) Then I did some diagnostics prior to attempting reactivation I started the kms server and checked connectivity with: 1. Prodigy's bat file checker (after inserting localhost address in the string) 2. netstat -a -n -o 3. telnet localhost 1688 (after enabling telnet which is not by default in Enterpise) Everything was OK, apparently. Kms up and reachable on port 1688, and telnet connection established. At this point I tried all the procedure from start using Phazor tool: insert KMS key -> set local address for KMS -> start the mock server The final activation step ends up in error 0xC004F074 once again. All I can say is that the procedure doesn't work when the machine is behind a corporate firewall. The problem in my case cannot be blamed to non genuine or tampered iso images of the OS.
Well i never said it is a problem with the ISO or the files, i said i think it is a problem with the network and a firewall would obviously fall into that very category. Anyhow, i still need a Vista EnterpriseN GVLK key to complete 5.0. Come on folks, somebody has got to have one?
The one i thought i had appeared to be Business retail?! So weird... But, anyway, was Enterprise N actually released and made available? I thought N versions for Vista ended up on market with Business N and HomeBasic N only.
Aahh...OK...that explains it. Thanks very much, and thanks MD for confirming that Microsoft lists it as EnterpriseE too. That means 5.0 is finished then...am going to test everything one more time and then upload it...
Well, 5.0 is done and the scheduled solution too. Made a new exe only for that, and, if i may say so, it works damn f*cking good. The task runs every 1st of the month at exactly 8:00PM (20:00h) and repeats 3 times inside 3 minutes in 1 minute intervals. Every run is 3 consecutive tries so we have a total of 12 tries in 3 minutes. That should be more than enough on systems where it worked before, no? The question is now what to do with the GUIed one... Should i put it in the installer as well so that a user has it all, (after all they have to install a key and set the IP first), or should i keep the two seperate? I myself am leaning more towards including it since that way they can at least not be seperated once they are out in the wild. Of course if i include it i will make both of them optional so that a user may install only one or the other and add or remove either one at any time. What do you think?
Hi Phazor I try to activate windows 7 professional freshly installed by KMS activator 4.2 and I am still getting error:0xc004f035 Error Code: 0xc004f035 The Software Licensing Service reported that the computer could not be activated with a Volume license product key. Volume licensed systems require upgrading from a qualified operating system. Please contact your system administrator or use a different type of key. any suggestion please
one question. What will happen if the computer is turned off on first day of the month at 8 pm? Will it retry on next day?
Put them together in one .exe. From your text GUI provide an option to install/de-install the scheduled task. You could also add to the text GUI a status whether the scheduler is installed or not, and perhaps even show the last activation date.