Task has changed in 2.1.6 into 1 or a custom task, but you just install AutoKMS then copy the EXE's you need.
Ok, i will install it in a virtual machine (since in my system i have a genuine key and i don't want to mess up things installing the activator) and copy autokms.exe. There is no need to also copy kmsemulator.exe? It never changes? I will then find a way to update task because you said it's changed in 2.1.6. Maybe regedit or some file stores the task, who knows...
I've used a unpacked one but you could leave it out (delete from WIM) since AutoKMS generates if it it does not exist.
Good to know! For the task question, i'm now a bit confused. When i created the wim file i've installed the activator without selecting the "task method" (i used the default one). I was thinking that default one equals normal autostart of autokms.exe and not the scheduled task, am i wrong? Anyway, if i remember correctly a task is a new file in C:\Windows\Tasks. So i might replace it with the new one... Found something, but i don't know if signatures change every time you install windows... Code: C:\Windows\Tasks\AutoKMS.job [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\CompatibilityAdapter\Signatures] "AutoKMS.job"=hex:ea,51,a6,99,55,27,a6,bb,8d,4e,76,04,38,f8,93,33,ec,55,ff,e2,\ 82,8f,56,b7,23,d5,b0,24,95,97,31,64,05,91,d4,81,c4,ea,fd,80,6e,72,6b,66,7e,\ e8,52,be,b8,26,a7,0d,ef,e8,62,8e,46,62,38,64,68,96,50,52 "AutoKMS.job.fp"=dword:a1faca8d
I am failing to run with command line parameters. every parameter crashed program. normal gui works. tried with 2.1.5.
Should I add Office 15 M2 support? Activation is very trivial to do since just about all of M2 is like office 2010. I already know KMS works but EZ-Activator won't touch M2 since it checks SKUs which Mondo is not included and it probably would have changed in M2 anyway.
I'm in your tokens, stealing your slics... Someone really needs to make a office slic extractor like the OEM extractor for oem certs. M2 is Mondo and C2R meaning I have to go through the tokens.dat with notepad and look for the slics in text, and Mondo has a crapload of slics (if it wasn't c2R i could get them out of the MSI). I only had to do this in 2010 to starter since all other installers had them in the msis. Basically they start like a xml file and end with a license or licensegroup tag, and I can ID which ones I need by the contents. Being able to dump them all would be much easier then going through manually.
Hi guys, I just wanted to know the proper method to install MS project 2010. I'm currently humming along great with office 2010 and visio 2010... Need to install MS Project now and was wondering do I just install it and use it? Do I need to do something with the toolkit or will it kick in automatically? I'm asking cause the last time I added visio, I messed myself up and just wanted to validate the proper procedure now for adding MS Projects. thank you
Because it would take more time and effort than I thought, I will only add limited M2 support. I wanted to add license backup, add, etc, but I will only add EZ-Activator support since I don't feel like getting all the M2 licenses and code only for it to change. I might rewrite some of EZ-Activator to be more inclusive automatically. M2 is KMS out of the box, if you somehow change that I won't be supporting it automatically.
100% wrong It just needs network access to the loopback IP i.e. 127.0.0.1, where the local KMS Server is being emulated
This is how I'll be adding M2 support. For those who have experimented, Toolkit will detect office installed if all you have is M2 (it just checks that OSPPSVC is a working service). Most functions work on M2, and you may be aware pressing Activate or Check will show/handle M2. This is because all these function handle everything. EZ-Activator won't touch M2 because I limit to KMS but I checked by SKUID, now I look if it says Volume, meaning EZ-Activator will try any KMS product even if not officially supported. Do note that M2 is click 2 run and uses it's own keys and licenses. I will not be adding this to the toolkit. You will not be able to add licenses/keys for M2 mondo, only activate it. I cannot repair mondo as it is C2R (I'm looking into this for a new way), so it cannot be repaired if broken. I've basically just changed EZ-Activator to take a crack at any KMS Office even if I don't officially support it (I don't support M2). However, on a PC that has no AV issue, I am confident that activation will be fixed by EZ-Activator before it repairs. I was able to activate all Office 2010 KMS products alongside M2, simply by making EZ-Activator more generic, without adding any M2 specific code (I don't want any M2 code in 2010 toolkit, when I make V3 it will be pure 2012 Office or whatever year). There isn't full M2 support but enough to activate, I need to add this to AutoKMS and test it.
I can't get on TV right now but basically. 1. Take Toolkit Backup 2. Run Script 3. Post if it works or not, it should show ProPlus KMS in notifications in the script cmd window if it worked, else it failed. 4. Restore Toolkit Backup