I already found it. I tried it. From command line it runs fine with /EZ-Activator option. But as soon as I add it to tasksched library run each 179 days, the activator does crash on startup. Why? I run it with highest privilegues. Moreover, which of the three dommand lines should I use to renew KMS activation for Publisher and Visio only?
You can wait and see what CODQX4 has to say but since 2003 and 2007 don't activate like 2010 does, I really doubt this is going to happen. Besides, why use either if 2010 works fine?
2003 to 2007 is a waste of time, as you activate it by having a VL Key, thats it. I won't go back and work on them as basically nothing is the same and none of my code would work on them.
Hey there all! I just reseted my Office 2010, because I didn't have any rearms avaible. I read on this forums how to do it: delete license keys, use EZ-Activator with AV off, and rearms are back! But this is not what I have to ask You. What should I do now to prevent running out of rearms? I mean without using IORT and installing EZ-Activator files. I heard that I need to backup license or something like that, and when Im close to run out of rearms back it up? Do I understand it right or not? I mean that I want to have activated Office 2010 just by rearms, without installing anything. Thanks in advance for helping.
Both the IORRT of Trilogy and the rearming part of EZ-Activator do this for you and as a result, you should not run out of rearms when using either of them. Doing this manually may cause the "out of rearm" issue if you forget. What do you have against using IORRT or EZ-Activator to rearm? Also note that rearming puts you in an infinite trial and does not actually activate (as you said).
If I understand you correctly, you want to keep office in grace forever but not install AutoKMS or AutoRearm. Well as you say you get the rearms back the way you did. You would then take a backup. You'd rearm manually about 25 days (because you'll get nags when you have 5 days or less), if it fails (because you ran out), you'd restore that backup and immediately rearm after (because backups don't save the days), and repeat the process. This is the concept I thought of that led to the creation of IORRT and AutoRearm as a non KMS activator.
Still appreciating your backup/restore method for my rearm concept Still working strong and with no problems Go rearm concept go...lol But of course everyone want's activation which makes Daz and your toolkit supreme in the solution world This person should use AR but it seems he doesn't know how it works as it sounds it's exactly what he wants
Two quick questions 1.If i use the Toolkit to activate my windows 7 enterprise as well, is there anyway to tell how long is left on the windows activation, just like you can 'check' the grace period (259200 minute(s) before expiring) of the Office 2010 suite. Or does this number (259200 minutes), also represent how long is left on the windows 7 enterprise grace before expiration? Because if i dont install Office 2010, i can still run AutoKMS to activate my windows 7 enterprise, but i cant 'force activate it' in the Toolkit GUI, nor can i 'Check' how long is left on the grace. This option only becomes available when i install office 2010 suite and push 'run ez-activator', leading me to believe there isnt a way to check how long i have left on my windows enterprise grace period before i get flagged as being non-genuine (this is all assuming that the auto-kms stops working for whatever reason, in which case, it would be nice to see how long i have left on my grace period like i can check with the office suite. 2. If my copy of windows enterprise isn't reactivated in the grace period, and it goes 'black' and essentially locks me out and constantly nags me for not being genuine, can i run ez-activator and it will it revive the copy of windows, make it genuine with the 180 days of grace again and put it in working status again?
Making an important change to the Backup Key Checker. Unlike the normal Key Checker and Key List checker, this will use the pkeyconfig.xrm-ms of the existing system as opposed to my built in ones. This allows me to know what these keys go to. For example, it would be difficult for me to know the difference from a Vista and 7 key, but if you check your backup key list, it will only be valid if on the right OS. This goes along with the fact I am working on my Windows backup now. I found a way to stick to one GUI but mod it dynamically to account for Office or windows, instead of two cs files with 99% code overlap.
I'm uploading but will need Mod approval for the new topic, as I can't seem to create a new topic in projects.