well it is really nothing for me to use vmware to test things like that. I won't have to blow my computer out to do it.
It doesnt. The schedule can be installed from the menu (its an option) but it wont be installed unless the user wishes to. And yes, as mentioned in the release posts and the apps tooltip; KMSA 5.0 is built around the code of ZWT. So its not a 'new' (or different) activator per se, its purpose is simply to provide a 'control-center' so that a user can use it on the supported editions without having to find any product keys and/or type any commands. Just see it as a 'everything-integrated' functional interface that allows you to do everything from installing the right pkey to activation-request effortlessly at the press of a button. And of course it works. The few cases where even repeated activation requests wouldnt help were related to non-default licenses and non-default KMS ports, both of which can be fixed. If the problem is the licenses (cases where the system was at some point activated via any non-KMS method like OEM:SLP) you would do a simple slmgr -rearm to reset the system and the licenses to their factory-default state. If the problem is the KMS port (cases where it is no longer at the default of 1688 or for some reason not set at all) you would do either a slmgr -ckms to clear the host machine name and reset the KMS port to the default or a slmgr -skms localhost:1688 to set host machine name and KMS port explicitely to what is required in this case. Aside from that the key is simply to be patient. Dont panick if it doesnt work right on the first attempt, just keep pressing 'Repeat Activation Request' and eventually it will be accepted. Under normal circumstances, if you have to repeat, it shouldnt take more than 3-5 requests until it works. If it doesnt work after the 10-15th consecutive request, and you always get the same error, it is probably safe to say that there is some other problem that needs to be fixed first. Most common are: • Firewall permission not granted (in this case it will never work) • LAN Adaptor not properly initialized (especially MS VirtualPC 2007 VMs) • Non-Default Licenses (due to an earlier activation that was not done via KMS) • Non-Default KMS Port (for whatever reason) If there are others they have not surfaced yet. Sorry, but there wont be a 6.0 anytime soon. Maybe when Office goes RTM, but im not making any promises yet...
w32tm, thats to sync the time with a time-server. Not needed with the ZWT solution as its 100% time (-zone) independent. (BTW, you do know that prodigys script activates via servers in the internet, right?)
Thanks for taking time out of your day to answer noobs like me .. But i was trouble-shooting ZWT's method and trying to figure out why it did not work vs. Prodigy's script working on first try.. and with ZWT's.. it kept returning an error right at that phase of the coding.. (just thinking out loud) .. (right at the activation request stage) with Prodigy's.. it also returned an error.. but because of that code i posted above.. it was able to still proceed and activate .. if you look at my screenshot on the previous page... you will see this error.. then right after.. the activation goes through.. this is why i had a hunch, the "/resync", had something to do with it .. just a thought .. if anyone else experiences trouble activating with KMS .. I do know that ZWT's method does not require Internet Access .. as they state this in their instructions.. but it did not work ..
i dont think i intended for it to be classified as "hot stuff" .. merely sharing what worked for me and what did not.. and giving credit to the deserving people .. Are you jealous you were not included in my list of people to thank ? LoL! Are you jealous of Prodigy ? im sure if you ask him for help.. he would teach you
First, thanks to everyone involved in creation of this wonderful tool. In my tests it worked after at most 10 tries. But there is something that bothers me. What about WindowsUpdate procedure? Do you think it will compromise the PKey used or the KMS server used for activation in any way? I mean when Update-ing there might be some check for the key(s), the KMS server used with its Host key.. e.g. validating the activation on each update. For now it seems to work Ok, but... who knows after 3-4 months. Any opinions are welcome.
Well the VL PKey is not in danger because there is only one for each edition and those are publically available even on Microsofts own websites. (In fact you can even find them on every Windows 7 DVD.) The rest would be pure speculation because only time will tell. Anythings possible, but doesnt necessarily have to happen.
Phazor, is there a way to start your script (either v4.2 or v5.0) with a default menu choice ? I mean, for example, writing a command like: KMS activator.exe /p where p is a parameter that indicates a specific menu action such starting the server or assign the kms server address or so on.. ?
No, there are no switches for default choices. The app can only be used via the console and im afraid thats how its going to stay. Sorry, i wish i could have given you better news. :-(
Sorry for not following the thread closely (been writing something rather complex in sh for some time). Last 2-3 pages were fun to read though. P.S. BTW, if you have problems with my scripts, send me a PM.
New to this activating thing so please help me out. I already know how to activate my w7, the only problem is the kms server i will connect in to. I also know how to make my own kms server using vmware but i still don't have the vmware and it will also take time to download it. So does anyone know what servers are up? Any form of help will be appreciated. Thanks.
Would I be able to active Windows 7 Enterprise Trial edition with this method that I can download from Micro$oft. I am just having hard time finding reliable links to download enterprise edition.
@ Phazor I dled the activator on your post. Tried it and at the last activation step, i get this error. Activating Windows(R) 7, Enterprise edition (ae2ee509-1b34-41c0-acb7-6d4650168915) ... On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0 Error: 0x8007000D Any idea how to solve this?