Run EZ-Activator. Code: Getting Office License Configuration Information. --------------------------------------- Backing Up License Info In Case Of Failure. --------------------------------------- Changing any Unactivated MAK Keys to KMS Keys. --------------------------------------- If You Have Starter Subscription It Will Now Use Permanently Activated Key. --------------------------------------- Converting Unactivated, Trial, Or Subscription Retail Versions of Office to VL. --------------------------------------- Removing Any Unactivated Retail Keys Left Installed After Conversion To VL. --------------------------------------- Getting Office License Configuration Information. --------------------------------------- Attempting To Activate Office 2010 KMS Products. Attempting To Activate Professional Plus. Successfully activated after 4 attempts. --------------------------------------- No KMS products detected. AutoKMS can't auto install, so i manaul install it. Code: Created C:\Windows\AutoKMS\AutoKMS.exe Created C:\Windows\AutoKMS\AutoKMS.ini Created AutoKMS Scheduled Task AutoKMS was succesfully installed. Check status. Code: --------------------------------------- CMID: 77803c12-2c4a-4a14-b2c0-c8c07fe57b43 --------------------------------------- SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c OID: 000306-237632-302166-599533-853690-099743-502226-055366-931130 LICENSE NAME: Office 14, OfficeProPlus-KMS_Client LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel LICENSE STATUS: Activated ERROR CODE: 0 as licensed Last 5 characters of installed product key: H3GVB REMAINING GRACE: 180 days (259200 minute(s) before expiring) --------------------------------------- SKU ID: 191301d3-a579-428c-b0c7-d7988500f9e3 LICENSE NAME: Office 14, OfficeProPlusAcad-MAK LICENSE DESCRIPTION: Office 14, RETAIL channel LICENSE STATUS: Unlicensed ERROR CODE: 0xC004F014 --------------------------------------- SKU ID: fdf3ecb9-b56f-43b2-a9b8-1b48b6bae1a7 LICENSE NAME: Office 14, OfficeProPlus-MAK LICENSE DESCRIPTION: Office 14, RETAIL channel LICENSE STATUS: Unlicensed ERROR CODE: 0xC004F014 --------------------------------------- Recheck after reboot. Code: --------------------------------------- CMID: 77803c12-2c4a-4a14-b2c0-c8c07fe57b43 --------------------------------------- SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c OID: 000306-237632-302166-599533-853690-099743-502226-055366-931130 LICENSE NAME: Office 14, OfficeProPlus-KMS_Client LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel LICENSE STATUS: Activated ERROR CODE: 0 as licensed Last 5 characters of installed product key: H3GVB REMAINING GRACE: 180 days (259190 minute(s) before expiring) --------------------------------------- SKU ID: 191301d3-a579-428c-b0c7-d7988500f9e3 LICENSE NAME: Office 14, OfficeProPlusAcad-MAK LICENSE DESCRIPTION: Office 14, RETAIL channel LICENSE STATUS: Unlicensed ERROR CODE: 0xC004F014 --------------------------------------- SKU ID: fdf3ecb9-b56f-43b2-a9b8-1b48b6bae1a7 LICENSE NAME: Office 14, OfficeProPlus-MAK LICENSE DESCRIPTION: Office 14, RETAIL channel LICENSE STATUS: Unlicensed ERROR CODE: 0xC004F014 --------------------------------------- AutoKMS.log doesn't create.
Not sure about AutoKMS failing but I see I screwed up part of EZ-Activator... I'll look closer tomorrow.
Yup, 2.1.5 needs more beta testing I also found the AutoKMS startup task wasn't activating Office, although the manual Activate button worked fine. Couple of other things: EZ-Activator doesn't automatically install AutoKMS, it justs activates Office one time, the same as if you clicked the Activate button (I wasn't sure if this behaviour was intentional, now there is the option to install AutoKMS as a service?) Also, clicking the AutoKMS Uninstall button gives the error "uninstall AutoKMS service first", even though I hadn't installed the service! Going through the motions of uninstalling the service allows you to uninstall AutoKMS and tasks. I've gone back to using 2.1.4 which works fine on my system Thanks for the hard work.. looking forward to 2.1.6! A.
OK my EZ-activator issue was because of a < that should be a >. I think the tasks are at fault for AutoKMS issues. I ran AutoKMS manually and it worked. Do note that if you click AutoKMS to run it, it won't work. By default it acts like a service. I run it with /Application manually and it works but fails with the tasks.
Solved the problem. I forgot to add this switch when I had to rebuild from V2.1.3 source. Expect 2.1.6 soon, I want to add logging to AutoRearm though.
Man at SetupComplete.cmd (that is end of OOBE) you shouldn't have any AV. CODYQX4 what do you think? Thanks
Unless integrated I don't think so but Windows Defender may be active. I personally don't think FW is a killer but you can't be sure. I can block everything on Norton Firewall and still KMS activate but AV kills it before it can even start.
I'm certain the Rearm Check error is timing related, at fault of OSPPSVC and not my code. I notice it happens rarely and other times a backup that is normally doomed to restore shows good until you restart OSPP. I am adding a delay in the "RestoreSuccessCheck" in addition to restarting OSPPSVC. I have also added more checks so I won't even let you start some functions is office 2010 has no keys or is broken VS allowing the function to continue and possibly fail (there right now is nothing stopping you from trying to EZ-Activate after a license delete. It will throw up errors about backup and then try to activate.). I plan to release a BETA dedicated to people trying to make the Rearm Check screw up. I notice a lot of times it throws it in grace yet another Rearm Check still shows 5, then still in grace. My code would detect any kind of Restore failure and throw an error so I believe it has to do with the way license info is remembered (delete your license info with Word open and it won't care until you close and reopen it). The OSPP restart should make it read it fresh.
This relates to why I added logging to AutoRearm. Everyone who lost rearms did so by pressing Available, but AutoRearm install calls the same function and no report of lost rearms afterwards was reported. Thing is if you did lose them by installing AutoRearm, and didn't check yourself you wouldn't notice for 30 days. I never in testing lost installing but have lost checking, and once you realize you know nothing of what happened with AutoRearm. I only log action, if it just checks and sees you have too many days to bother doing anything it won't add to the log. It won't log until you get to 5 days so don't think it is broken logging.
Never thought of it that way. I simply wanted AutoRearm to do as little work as possible. Of course if OSPPSVC decides all of a sudden it doesn't like the backup, office licensing is done and dead there, but I have yet to see this happen for a backup from the same OS/Format. Strangely AutoRearm seems faster/less resource-using than AutoKMS. While both are light, AutoKMS has to query the license database and operate on each license one at a time whereas once AutoRearm queries the next step (Rearm or Restore) covers everything. If you noticed instead of the old Hybrid task I now use a Hybrid Trigger task. I have one task but 2 triggers. I don't know how to/if possible this can be done via commandline but I like it
Nice. I know that people gotta have KMS activation and you need it to restore rearms but AR/IORRT rule
2.1.7 B1 is uploading. My connection is awful so link is posted but not up yet. Could use mirrors for 2.1.6 and 2.1.7. The whole point of this BETA is to test the "Available Rearms" function thoroughally, nothing else core has changed. If you aren't going to test that function and respond and/or you are happily activated (AutoKMS/AutoRearm are still 2.1.6), don't bother. @Bosh when I can get the 2.1.7 source up I'll PM you. I have UI plans for the Confirmation ID and Backup Key boxes. For the Confirmation ID box, I'd like the OID displayed in individual boxes that are read only, with no dashes. Also The CID would be similar but typable, with the letters A-H (easier to correspond from the phone) below them. Note that OID is one box longer than CID. These boxes could look a bit nicer/user friendly then now. I have at least made them stay centered (I hated having to look for MAK and then open the toolkit but the prompt is in the background, so I changed that). I'd like similar to the key box but the thing is that may make things harder. Most people paste their key, dashes and all. I'd like to hear some feedback on this. Of course, being able to paste into one box and the rest automagically end up in the other boxes could be nice.
OK 2.17 B1 is up. @Bosh the source for it has been updated, last link was 2.1.3 and I've kept on to 2.1.6 source.
It seems 2.1.6 has fixed the problems of AutoKMS. Available button also works fine and shows only 1 rearm in 2.1.7 B1.