It installs a task that activates on startup and/or 24 hours after it last ran. When this task runs, AutoKMS.exe runs, activates, and when it is done it closes along with KMSEmulator. The default task can be replaced with a custom one that oyu set your own triggers with. It used to have a service but I nuked it so as to make a dedicated network service in the AIO.
Can someone help me find more KMS keys? I hear these products exist and are KMS compatible: Server 2008 R2 Foundation Server 2008 R2 Storage Server 2008 R2 Essential Business Multipoint Server 2010 Server 2008 Foundation Server 2008 Small Business Embedded 7 Standard Compact Embedded 7 Enterprise Embedded 7 Standard Evaluation 7 Thin PC Anyone have KMS keys for them? I want to add them to the toolkit so 100% of KMS products have keys listed. Let me know if any products exist that can use KMS (beta/RC stuff doesn't count, so no Windows 8 stuff).
What's "AIO" ??? I think it probably means "All In One", but the word "all" is always very relative What does the word "all" include in this case?? I'm interested specifically in the network service. We know that wzor's Mini-KMS service is acceptable, but unfortunately it suffers from the annoying bug that produces always "invalid data" responses unless you change the CMID (client machine ID) of the computer. Changing the CMID is a cumbersome process that involves deleting the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OfficeSoftwareProtectionPlatform" registry key, rebooting windows, and then launching Office several times until it repairs itself. It's extremely annoying and time consuming!! Can you please advance some info about this future project?
Well I have Windows capable code but the toolkit is Office centered and does more than just KMS. I plan to gut non KMS office specific code, and release a separate toolkit that does KMS for windows and office. No OEM stuff but like Phazor's tool which aimed to cover all KMS options you could ever need. I want to add all possible windows kms keys though. PS: Another way to beat the constant fail is to change PID instead of CMID. I am going to allow multiple instances of KMS Network Service (on different ports) so you can have different PIDs. Phazor used a PID change except he used it to allow you to rearm which changed CMID. I just in AutoKMS force it to use the working PID so you don't have to use the rearm.
The PID that you're mentioning is the same that can be obtained with this command? cscript "C:\Program Files (x86)\Microsoft Office\Office14\OSPP.VBS" /dinstid As opposed to the CMID, that is obtained with this other command? cscript "C:\Program Files (x86)\Microsoft Office\Office14\OSPP.VBS" /dcmid Or is it a different identifier???
That is called the "OfflineInstallationId" and is used in Phone Activation, which can't even be done with KMS. KMS PID is a PID used by a KMS server (or in our cases, KMS Keygen").
Over 23,000 DL's of V2.2 in 3 days, and that's ignoring the fact it must have been mirrored by now. That's nice, too bad I can't find a reliable image host. Might just remove the screenshot and be done with it since it isn't that important.
Can someone spare me a 3GB download that will take forever and upload the pkeyconfig.xrm-ms for MultiPoint Server 2010? I saw links but they were all dead.
Congrats on that! BTW, let me know when you upload the code . I'd like to take a look at the RAM execution in action
I'd upload the source but I'm adding a few more keys and I've had issues with my host and connection.
I know, just busy, and TinyPic sucks and my main host is not working. I'll reup whenever but it isn't important enough right now.
The "rearm available" option works for me now with version 2.2. I get back the 5 rearms i had long time ago. Thank you for this new update.
In this latest version, i cannot extract setup and set installer path. In 2.1.6, that functions works.