I used the real ones as I have confidence they can work. I was considering just generating random stuff but having 11 PID's gives me plenty of room.
Thats cool. Thanks. I will try the one you posted first (as soon as i have the time) and get back to you if i have problems or suggestions. The activation with the different Host has to succeed, otherwise no dice. And yes, whats important is that the license module sorta resets the status. This deletes all old information, making it possible to use a formerly blacklisted Host again. Thats why i do the null-Host as an intermediate step in FixMe...
Sure, i myself would only release Hosts with real-existing PIDs as well because the users certainly dont like to have easily-identifiable stuff like obvious fake-PIDs on their systems. I just meant to share the info, so you know whats possible...
As I said, there are know bugs in the last release (mainly writing to memory). So effectively with your fix is you change the PID like I do in a different way. Though what I do since I in EZ-Activator since I do the least invasive fixes first, is I just if I do have to change the PID, is just save that PID to my settings ini and always use it (including AutoKMS), so that I don't have to change the CMID.
One more thing; always be sure to test alternative PIDs with both Windows and Office. Some work with one, but not the other. I found that out the hard way...
Sounds like a sensible way of doing it. Fortunately you have way more options in your app than i have with mine...
That may be an annoyance with AutoKMS, as it has Windows support but isn't really gone through Windows testing. I wonder if the 11 total PID's (1=ZWT, other 10 posted by letsgoawayhell in various posts) do actually work on windows.
Well, i can vouch for these: (from the notes) I thought i had more because i did excessive testing that one weekend but i had to look if they are still there. Actually there also should be a whole bunch of yet other ones because i made one version of the app where the user could manually select 1 of 20 different hosts...
Nope, seems i binned the files of that other project. Theres a slim chance that i have a copy on one of my VMs, though. Will post if i find it. In the meantime, if you like to try to find some yourself, you can try one thats proven to work (7 ServerEnterprise-R2 GVLK is a good start) and just change the date a bit. Couple of days forward or backward suffices...as long as only one bit in the string is different the licensing module consideres it an entirely different host. The run it on Win and Office and see if both accept it...
If you have a PID that works on both office and windows, could changing the date break compatibility? Because as far as I know the date is simply appended on to when it was generated.
Yes, definitely. I made an extensive test run where i changed only the days bit and the result was that some of the resulting PIDs work with Win only, some with Office only, some with both and some with neither. What works and what doesnt also depends on the installation. Not all PIDs that work for both products on one computer automatically work on another as well. Heres one of the notes i made for Win, (from one of the many customized Hosts i made - dunno its exact other config anymore), just so you see what results are possible: Note how some of the numbers are under 'work' in one test setup, yet under 'nowork' in the other. (301, 318, etc.) Thats why i tested all PIDs on at least 4 different Virtual Machines to be sure they dont work only on one specific setup. (Yes, thats all much more complicated than one would think. Like i said in the notes, there is 'some' yet unidentified condition in play which decides about success or failure.)
It's possible to say this "unidentified condition" may be related to the initial issue. I'm testing the current PID's I have against office 2010, hopefully someone with KMS windows can help confirm if they work on windows.
Based off my testing on my real PC (These are all the PIDs posted by letsgoawayhell) Note that I only did 2-4 CMID changes and that more might have made it work. 55041-00096-199-000004-03-1033-7600.0000-3632009 // Bad For Office 55041-00168-305-246209-03-1033-7600.0000-0522010 // Good For Office 55041-00168-305-100667-03-1033-6002.0000-2372009 // Good For Office 55041-00142-026-982506-03-1033-3790.0000-0962010 // Bad For Office 55041-00152-339-725949-03-1033-3790.0000-0972010 // Good For Office 55041-00140-015-871562-03-1033-7078.0000-0992009 // Bad For Office 55041-00142-026-826687-03-1033-6000.0000-3472006 // Bad For Office 55041-00152-105-000223-03-1033-6001.0000-0692009 // Bad For Office 55041-00168-313-440506-03-1033-7600.0000-2242010 // Good For Office 55041-00142-026-098258-03-1033-6000.0000-3392006 // Bad For Office These are your PIDs - All were good but I had to do one CMID change for the 3rd one. 55041-00168-305-190595-03-1033-3790.0000-3482010 - Server 2003 (GVLK?) [Org string with new date.] 55041-00150-029-010173-02-1033-6002.0000-3512010 - Vista ServerEnterprise OEMSLP 55041-00168-001-000107-03-1033-7600.0000-2962010 - 7 ServerEnterprise-R2 GVLK 55041-00168-006-920006-02-1033-7600.0000-3142010 - 7 ServerEnterprise-R2 OEMSLP So Including the Original ZWT PID, and assuming your 5 are always good for Windows+Office, I have 5 that appear to be confirmed for both. The 4 of letsgoawahell's posted PID's that worked on mine are not yet confirmed for Windows. Windows KMS users can help confirm by taking the above ones that say Good For Office and DLing the CMIDTest.exe, and use it to patch a KMSEmulator file by putting KMSEmulator.exe and CMIDTest.exe in the same folder, and using CMIDTest to patch the file. Then see if you can activate KMS windows with those PID's. Note that you may have a bad CMID, so use up a rearm and try again with that PID (you can use IR4 to get rearms back on windows).
Its exactly this uncertainty why i ultimately decided to make FixMe the way i did. I had lots of concepts planned out, (hot-patching, user selection, aso.), but the one i went with seems to be the only one thats nearly failsafe. (Nearly, because there can still be that odd one-in-a-million installation where something goes wrong for reasons unknown.) At any rate you have to be very careful with this stuff, otherwise you will be in for a surprise or two...
Yes it does to seem to be very weird and the errors come into play for no apparent reason. Do you know if its possible to get a real KMS server's PID jammed/blocked?
I cant prove it, but im absolutely sure. After all Windows thinks ZWTs is a real Host too, otherwise it wouldnt accept it...
Well I've wondered if the error was the result of a bug in the KMS emulation. The only way I could really tell is know the PID to a KMS server that will activate me, test it in CMIDTest.exe using the keygen until it fails, then see if server activation could work.
So, what youre saying is that you need PIDs of public hosts? Or do you actually want to activate over some and need their IPs? Please clarify...i can help in both cases...