This is awesome CODYQX4 I tested it like a hundred times in different situations and had no errors yet. seems more stable than the previous one to me even if it is beta. I had in mind to tell you that the 2.0.1 would crash if "osppsvc.exe" process was running but apparently in this new version it's been taken care of. Excellent job buddy. One question : have you received any bug yet ? I mean can I consider this as the 2.1 final release ?
The bottom of the readme states POSSIBLE bugs, as in this beta may have fixed them, other than those no new bugs have shown.
Just letting you know that I retried 2.0.1 to make sure it the freeze was still an issue (it was). I then switched over to v2.1 beta, and AutoRearm worked like a charm, seems like it's bug fixed. Office Standard/VL/64bit: You have 5 rearms. Getting Office License Configuration Information. --------------------------------------- Backing Up License Info In Case Of Failure. --------------------------------------- Converting Unactivated, Trial, Or Subscription Retail Versions of Office to VL. --------------------------------------- Removing Any Unactivated Retail Keys Left Installed After Conversion To VL. --------------------------------------- Created C:\Windows\AutoRearm\AutoRearm.exe Created AutoRearm Scheduled Tasks Created License Backup Of Current Configuration AutoRearm was succesfully installed. Check Office 2010 Activation: --------------------------------------- SKU ID: 9da2a678-fb6b-4e67-ab84-60dd6a9c819a LICENSE NAME: Office 14, OfficeStandard-KMS_Client LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel LICENSE STATUS: Activated ERROR CODE: 0 as licensed Last 5 characters of installed product key: 8R6BM REMAINING GRACE: 175 days (252580 minute(s) before expiring) --------------------------------------- SKU ID: 1f76e346-e0be-49bc-9954-70ec53a4fcfe LICENSE NAME: Office 14, OfficeStandard-MAK LICENSE DESCRIPTION: Office 14, RETAIL channel LICENSE STATUS: Unlicensed ERROR CODE: 0xC004F014 --------------------------------------- SKU ID: dd457678-5c3e-48e4-bc67-a89b7a3e3b44 LICENSE NAME: Office 14, OfficeStandardAcad-MAK LICENSE DESCRIPTION: Office 14, RETAIL channel LICENSE STATUS: Unlicensed ERROR CODE: 0xC004F014 --------------------------------------- I was suprised to see the remaining grace is 175 days. I'm guessing that once the previous KMS activation runs down to 5 days AutoRearm will kick in? The beta looks great. Thanks for your hard work Cody, and to everyone else who helped! You are kings among men!!
I am using this toolkit on two machines now and every so often eset smart security keeps popping up a message about a virus each time i click clean it goes away and comes back a couple of days later Anything i can do please ?
Add them to the exception of the Antivirus. For ESET Smart Security: - Open ESET Smart Security - Press F5 to enter advanced configuration - Go to the "Exclusions" option in the "Antivirus" part (in the left pane) - Add the exclusion for "AutoKMS.exe" and "KMSEmulator.exe" in the directory C:\Windows\
Hi CODYQX4 and Bosh, i have tested v2.1 Beta in a clean virtual maschine only with windows 7 ultimate sp1 x86 and office 2010 pro plus x86 installed. I took the AutoRearm Method to "activate" my office. You have 5 rearms. Getting Office License Configuration Information. --------------------------------------- Backing Up License Info In Case Of Failure. --------------------------------------- Converting Unactivated, Trial, Or Subscription Retail Versions of Office to VL. --------------------------------------- Removing Any Unactivated Retail Keys Left Installed After Conversion To VL. --------------------------------------- Created C:\Windows\AutoRearm\AutoRearm.exe Created AutoRearm Scheduled Tasks Created License Backup Of Current Configuration AutoRearm was succesfully installed. Remaining grace: 30 days. so i turned time a few days in future --> Remainig grace: 4 days. --> Reboot virtual maschine --> remaining grace: 4 days :-( it should be turned back to 30 days? am i right? whats wrong? in my opinion it is better du set back Remaining grace once a week instead of 5 days before End, because bad naggy screens appear when remaining grace is at 4 days.
Can you verify that the task is running at boot? Basically jot down the time the daily task is supposed to run then reboot and see if that time changes (it should).
i have testet the same scenario with v2.0.1 and here it works.... AutoRearm task runs at boot. Does the AutoReam.exe create some logs?
No it doesn't log things. I'll look into the AutoRearm V2.1 when I can, but you can use 2.0.1 for now. I tested manually triggering the task before and it seemed fine.
yes the task says allright, i have triggered both manually, but the grace period is not set back to 30days. thx for looking for the bug in AutoReam v2.1
hey CODYQX4, i have found out a way to suppress the windows firewall warning: Code: @echo off netsh advfirewall firewall add rule name="Office 2010 - Local KMS Host - TCP" dir=in action=allow program="C:\windows\kmsemulator.exe" description="Office 2010 - Local KMS Host - TCP" enable=yes profile=any localip=any remoteip=any localport=any remoteport=any protocol=TCP interfacetype=any edge=deferuser netsh advfirewall firewall add rule name="Office 2010 - Local KMS Host - UDP" dir=in action=allow program="C:\windows\kmsemulator.exe" description="Office 2010 - Local KMS Host - UDP" enable=yes profile=any localip=any remoteip=any localport=any remoteport=any protocol=UDP interfacetype=any edge=deferuser exit what do you think would you like to integrate that code for more user friendlyness?
i don't want to add that as that just takes care of Windows Firewall, where more firewalls may be installed. Strange thing is sometimes activation works despite Windows Firewall.
Is there something up with AutoRearm? Are you considering the changes users here made about your restore/rearm duration? Thanks
I resue code from toolkit to make AutoRearm, and it's likely a change has broken things. I'll have to see but though I'd like to burn the rearms down before restoring a backup, I'm not sure if I should wait the 25 days or just do what you have done and run daily.
I have Avira personal version installed and windows firewall activated, toolkit works without a warning. I also tried microsoft security essential and it just showed a warning to clean the kms but didn't stop the process. thought you might wanna know. thanks again. it's greater and faster than the previous version.
Mine is just easier to see it working cause you wait less days but in theory yours should also always restore/rearm but more "on the edge" kinda
Used the OTK 2.1.b1: Office14-OfficeProPlusMSDN-Retail x64 and Windows 7 Ultimate x64. First In the License Files Panel I made: License Type: Volume License for: Professional Plus -> Install -> ok After in the Main Panel: activated with EZ-Activator and now my status is: -------------------------------------- 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 (259159 minute(s) before expiring) --------------------------------------- installed on the 3 march. Only added c:\windows\AutoKMS.exe and C:\Windows\KMSEmulator in the exclusion panel of the Eset Nod32 AV 4.2.71.3. Nothing about some windows firewall warning. In the taskschd.msc are working the two tasks: AutoKMS AutoKMS Daily All is working at the top, I use in an intensive way Excel, Word and Outlook. I ask this, now I can't check myself: if today, 6 march, 3 days after the installation, I uninstall AutoKMS I come back in to OfficeProPlus Retail with 30 days grace, or 27 days grace or 0 days grace or what? The uninstall process reset the token or change it?
AutoRearm v2.1b run much faster than in v2.01 but do not reset the gracetime back but i think you will find the prob ;-) i think a daily rearm how it is made in IORRT is better than waiting 25 days, because user is safe of naggy MS popoups of activiation and the user has more time if it fails one time. Alternatively 1 rearm in 1 week is also ok. What is the difference between IORRT and AutoRearm? is one faster or make more system checks?
could u please add the kmsemulator.exe and autokms.exe in a single folder autokms inside the c:windows/system32. it wil be easier to exclude this folder from antivirus scanning list. that would be cool