Restoring won't help for KMS. You could activate then backup but the restore would have no effect on the count. Restoring does not change the count. The reason restore allows for AutoRearm technique is because the registry saves the rearm count. You can take a 180 day backup, wait till it gets to 175 but restoring won't change the fact that you still have 175 days.
Show the full count, if it says in Office that it's activated then it's activated. The "Unlicensed" are license types you don't have a key installed for. If you activated Visio Premium KMS then that is activated, what you show is Visio Premium MAK and Visio Professional KMS. These are 2 different licenses/product key types you can install. I display output such that the activated stuff is at the top (I append Unlicensed to the bottom, if "Verbose Check Setting" is enabled).
I think you might have missed what I was saying 1. You activate with keygen 2. Upon activation confirmation you backup 3. Instead of having autoKMS and emulator on system you create task to restore instead of being dependent on KMS or keygen ever again...lol 4. You could do it at startup then you'd be fine with in a 6 mo period 5. You only need keygen for the initial activation then form their no AV flag stuff on system just backup and task Make sense Edit: lol...Ok I see what your saying well it was worth a try Are you sure it won't go back to 180 upon restore?
The reason I use the 5 day remaining check is to allow you to dow what you are suggesting. You already can KMS activate once, and install AutoRearm and it take 175 days for the first rearm/restore to occur. Subsequent rearms would be 30 but what you suggest is already possible if you install AutoRearm when successfully KMS Activated. The ideal state of 180 days + 5 rearms (150+180 days) could work and you could reactivate manually. This is why I don't trigger AutoRearm unless 5 days or less remain as I let the KMS or Trial or Subscription or whatever count run down to a low level first. PS: 5 days is an arbitrary number (I could and should and probably will make it 1 day since I picked 5 days before the Hybrid Task idea), it shouldn't nag at this point. If someone can confirm that there is a point at which in the grace does nag then verify first and let me know. Keep in mind retail ALWAYS nags, so you need VL/KMS, which should not nag until you hit 0 days. It may be a while but I'll released a fixed AutoRearm in a second BETA, otherwise testing of other things is recommended. The main bugs seem to be resolved, and the "Unlicensed" is NOT a bug it is simply extra info, so other than AutoRearm things seem solid, but I need more time/info to tell.
Ok I thought I had stumbled onto something new but if count lessens then restore is useless in an activated state hence only grace state can facilitate restoring I tried...lol
Sorry, you are correct. I must have been too tired to notice that the proper installation was activated: --------------------------------------- SKU ID: 92236105-bb67-494f-94c7-7f7a607929bd LICENSE NAME: Office 14, OfficeVisioPrem-KMS_Client LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel LICENSE STATUS: Activated ERROR CODE: 0 as licensed Last 5 characters of installed product key: WX8BJ REMAINING GRACE: 179 days (258060 minute(s) before expiring) ---------------------------------------
Yea that is what I got also so 5 day til is no longer arbitrary but I already told cody this 3 months ago...lol
And speaking about tolding things, there has been very few feedback from users (in proportion to downloads). I can think of 2 reasons: 1. The Beta was released with almost zero errors (yeah right) 2. The link was shared in other places and the users never get to know where to ask Anyway, just a comment since this thread seems to be lacking user feedback
Banned for tolding things ...lol Funny too is you guys have so many link dl's so thanks to who responds if they do ...lol
OK I have confirmed that when the count drops to 4 days, a nag does appear and so I will keep the 5 days as it will prevent ever getting 4 days.
Backups and Rearm count was screwed up for me on my PC for BETA 1 but it seems I have made it solid, and I tested AutoRearm by installing, stopping OSPPSVC, changing date, starting OSPPSVC, checking to make sure I had 5 days left (you get nags at 4), then run AutoRearm task and it did what it did. I didn't test it by rebooting but it should work then, which the tester said it ran but did nothing (I couldn't personally confirm they had 5 days or less but they said they did). BETA 2 will drop in a few minutes, and I've disabled Verbose Check Activation by default (turn it on if you have conversion issue to troubleshoot). I removed the "Permissions Fix" in repair for now because I can't confirm if it helps (I have never seen anyone report the issue after repair), or it it was making things worse but it seems unnecessary. Please provide feedback on the BETA.
OK I uploaded the new BETA. I plan a new feature soon, to allow where to install AutoKMS, AutoRearm, and KMSEmulator.exe. It will be a path saved in the INI, and if the path is inaccessible/doesn't exist the defaults will be used. The default for AutoKMS will be changed to c:\windows\autokms\ instead of c:\windows\. I'll figure out the location when uninstalling by reading the task if I can.
Ty for the Beta2. My test: IT_Office 2010 ProPlus MSDN Retail with license converted to VL by means of OTK B1. The grace was 180 days. Yesterday uninstalled the AutoKMS. Today used the new Tool kit B2 - the Office 2010 Activation check is: --------------------------------------- SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c 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: 179 days (258289 minute(s) before expiring) --------------------------------------- Installed the AutoKMS activation tool and the display console shows: Created C:\Windows\AutoKMS.exe Created C:\Windows\AutoKMS.ini Created AutoKMS Scheduled Tasks AutoKMS was succesfully installed. After reboot, the AutoKMS.log is: ------------------------------------ AutoKMS Ran At 08/03/2011 07:45:42. Successfully Checked Installed KMS Products. Professional Plus KMS Installed. Successfully Set KMS Host To 127.0.0.1 Started KMSEmulator.exe Attempting To Activate Professional Plus. Successfully activated after 1 attempts. Stopped KMSEmulator. No AV issue with NOD32 AV - C:\Windows\AutoKMS.exe and C:\Windows\KMSEmulator.exe added to exclusions in the extended setup. The taskschd.msc with the AutoKMS and AutoKMSDaily task in the library. All Office applications are working without problems. Please, provide also the md5 or sha1 of the .exe file in the release. Thankyou for all your work
AutoKMS: activates Office 2010 for 180 days. Task set time back to 180 every day. Effect: you never run Office under 179 days. AutoRearm: "activates" Office for 30 days. Task set time back before 5 days of expire. Effect: you never run Office under 5 days. My Question: on the one hand you set 180 days back every day and on the other hand you set 30 days back only 5 days before end and let office almost die in expiration. Why that? On the next beta you will improve the path of AutoKMS, thats very great. Would you like to improve the days in AutoRearm, too? I think it is more uniform, consistent and professional if AutoKMS and AutoRearm have the same Path and TimeSetBackTask in the figurative sense.
also on beta 2 the AutoReam task do not set back time to 30 :-( i used a clean vm with win 7 x86 and office 2010 x86 vl and set time after installation to 4 days before expire. Restart, no 30 days :-( i dont no what's wrong i used a clean machine?!? did anyone else have the same prob? cody or bosh whats your opinion?
AutoRearm and AutoKMS work very differently. I can keep AutoKMS at 180 forever by KMS activation, which if you successfully KMS activated and have AV configured to ignore AutoKMS stuff, it will always reactivate to 180 days (with no limit on how many times I can do so). AutoRearm uses Office's built in "Grace Period/Rearms". You only have up to 5 and once out you are out. Each rearm gives 30 days but you start getting nags at 4 days (so run at 5 so this never happens". I can only rearm till the count is down then restore backup to reset rearm count. I could restore every day every time like IORRT but this takes longer. To keep Office in perpetual 30 days means restoring backup every day which is not as efficient. The Hybrid task setup makes sure you'll never fall below 5 or hit zero (if you reboot it runs). Basically I wait till 5 as it means that it takes less time until needed (Restore + Rearm is slower than just seeing how many days are left, and backups may fail but unlikely).
OK, wonderful! Very good, clear explanation for the difference between the AutoKMS and the AutoRearm functions. Always good work cody & bosh