Discussion in 'Microsoft Office' started by kdo2milger, Sep 4, 2010.
You need to login to view this posts content.
When you install this activator as a service, does it automaticcaly reactivates office 2010 VLK? Or do you still have do to it manually after 180 days?
So what's the auto activation tool for?
I think it activates Office 2010 every time you restart your computer, so the remaining days always is 180 days. Or maybe that's Phazor KMSA 5.0 (soon 6.0) activator thats do that.
What is mini-KMS_Auto_Activation_Tool_v1.13_Office2010_VL_ENG-FreeSoft-WZT ? What utilisation for this ?
Odd's are that any updates for mini-KMS are just trying to copy MD's loop activation script which attempts to activate over and over again unless they had that which I think they did not. Otherwise KMS activation seems to be at a standstill with use of Z.W.T keygen
KMS still only activates Ent/Pro/Office 2010
When it is installed as a service, the keygen runs in the background. Every seven days, the OSPP (Office) or SPP (Win7) or SLS (Vista) request for KMS activation renewal and the Keygen responds to this request. It acts as if the it is always connected to the KMS server.
Running the activator at start-up will add 1.5 seconds in your boot time.
Running the Keygen as service will eat 2 mb of your memory.
Both the methods use resources that are negligible.
Or you can run the activator after the 180 days has expired.
In KMS activation, it does not matter whether you are at 180 days or 1 day. Your Windows or Office copy is activated.
The auto_activation_tool does not use my code, it is more on the lines of Cody's EZ-Activator. It also has an update file, when integrated with your Office ISO will activate as soon as Office is installed.
Are you saying this new build just added integration possibilities
I liked your activation w/ZWT because it didn't install stuff. But how does mini-kms attempt activation if fails first time. Why do you think they came out with new builds?
The principle is same for auto-activation, check grace period is 180 until then try to activate.
Minikms goes as far as rearming office and trying for another set of attempts.
For integration, they have created a home-brew update that needs to be added to the Updates folder of the ISO. What it actually installs is the auto activation tool.
Oh ok so it's actually pretty smart with KMS activation. And when it's run as service there's no chance that task pulls up dialog box whether or not to deal with keygen. I noticed when I set up task for your script as .exe with keygen it would do dialog box hence it was kinda manual in it's confirmation, etc...
If you want to use my script for a task, you can actually comment out or remove the ping parts in the code, this will reduce the amount of time it takes to run or else it will be wasting 5 seconds on windows and 5 seconds on office.
I didn't really mind the "taking time" to work as did I wish I didn't get confirmation box to overwrite, not or cancel regarding keygen use with your script
I'd like it to run silent when it activates. I really liked a simple task to activate both my pro and 2010. But the dialog boxes make it not silent. Any comments?
Which dialog box are you referring to?
Only a single command window opens up when the script is run.
When I run the script as admin wiht keygen in same folder or compiled .exe it does just open cmd window. But when I set task to run .exe or script it opens box saying do I wish to overwrite existing keygen. No other keygen was in folder just the .exe with keygen or script with keygen separate. I didn't get it why it did that. Should I set task as "system" for it to run non-interactive "silent"?
Do not compile a .exe for the script. Setup a task that runs the bat file and keep the keygen along with the file. Administrative privilege is not required while activating.
Your problem would be related to how you compile the exe. If you use Winrar, set Overwrite=1, that will automatically overwrite the existing file without asking you.
Thanks I am stating to understand your simplicity in just doing .bat files. Good work and thanks for your time MD
I was using the .bat to .exe program you suggested to me not winrar
In bat to exe, set it to the following
Working Directory --> Temporary Directory
Miscellaneous --> check Overwrite existing files
[Optional] Visibility --> Invisible application
Thank you very much