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
AutoKMS just reactivates your Office every time it's ran, unistalling it just removes the auto-activating feature of the Toolkit (it removes AutoKMS.exe, KMSEmulator.exe and the AutoKMS scheduled task).
yes, this is ok, I know this. But today, 6 march, 3 days after the installation, if I uninstall AutoKMS I come back into 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?
Well we both we're having ideas about the Rearm concept so not much difference. His is written in C# and mine cmd line. Mine is more automated just daily or at boot restore/rearm from backup. His thinks does autorearm need to restore/rearm yet as to avoid, through cody's perspective, unnecessary restoring/rearming til the last moment I too think the daily/boot task is best but both work as long as Autorearm restores/rearms before nags present themselves
I think I just figured things out for you guys Seems the restore from backup is 100% so How bout my idea of activating once with KMS and keygen then at interval of your choicing (startup) just restore from backup done right after activation is confirmed. Then you'll only have to run keygen once and no firewall permission or Av issues again if user changes AV or whatever dude. Also you can delete keygen and keygen accessories after initial one time activation is confirmed...lol That is good idea of combination of KMS/Restore And you would probably only need one task if you got 6 months to restore/rearm ...lol So basically your guaranteeing re-activation without AV flags infinitely instead of there being any chance of not reactivating My gift to you ...lol Also I noticed that you choice the wording activation for when deciding on AutoKMS or Autorearm when autorearm doesn't have anything to do with activation Then you could have the first Hybrid Activation/Backup/Restore solution in the world which I think people would be happy with In essence you woudn't even need Autorearm although I don't discourage Autorearm which works fine I'm sure Now you just gotta figure out how to avoid error Phazor did via running in memory and you got best KMS setup available plus your massive tookit for almost every aspect of office Just two ideas I thought you might enjoy Captains log ...lol
I had used Toolkit 2.0 and just ran the beta and although the Office components still say they are activated, the "check" feature in Toolkit reports Visio Premium has a problem, but Visio itself reports "activated": --------------------------------------- SKU ID: 36756cb8-8e69-4d11-9522-68899507cd6a LICENSE NAME: Office 14, OfficeVisioPrem-MAK LICENSE DESCRIPTION: Office 14, RETAIL channel LICENSE STATUS: Unlicensed ERROR CODE: 0xC004F014 --------------------------------------- --------------------------------------- SKU ID: e558389c-83c3-4b29-adfe-5e4d7f46c358 LICENSE NAME: Office 14, OfficeVisioPro-KMS_Client LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel LICENSE STATUS: Unlicensed ERROR CODE: 0xC004F014 --------------------------------------- Any thoughts on what I could do to correct this? I don't want to deactivate Visio Premium and not be able to reactivate it. Thanks.