First thing to do is do a License Repair, then enable Verbose Check Activation Status in settings, then Check Activation Status and post the results here. This will show licenses even if you don't have a key installed. If you have no products with a key installed, press License Add for Volume Professional Plus. Thing about EZ-Activator is it cannot detect that you have a product to activate if you don't have a key (since it can't do anything about it). By doing the License Add, you will have converted your Retail to VL (something EZ-Activator does but it has to detect a retail key to do so). You should now be able to activate that Volume product via KMS (EZ-Activator).
thanks for the reply cody... I followed your instructions however when I click the Ez-Activator swicth it tells me to uninstall "IORRT" even though I hav already done this. Do I need to delete IORRT If I still don't get anywhere I will post the activation status results, though it does appear quite long Thanks again Oh hang on......it's worked....!! now the programs are opening and starting with an activation box regarding corporate use or change product key...I guess I just close that.....got the big red bar acoss the top
If it mentioned IORRT it means I detected it or part of it. You need it totally uninstalled. I don't allow them to work together since they cancel each other out. IORRT uses backups and rearms to keep your PC in grace (not activated). EZ-Activator does KMS which involves KMS activation. IORRT would restore a backup and totally cancel out any KMS stuff you do since it restores a state to work. My AutoRearm does the same thing as IORRT (it was my idea to do such a thing and me and timesurfer collaborated on the idea later), and for the same reasons I don't let EZ-Activator and AutoRearm both be applied.
@KMS users I know currently that I install AutoKMS as a local tool that runs while needed, but for you network host users (Mini-KMS and LocalHost), would an option to install the KMSEmulator as a service be of any use to anyone? If there is enough demand for such a thing, I would operate it as follows. Upon install set local Windows and Office hosts to 127.0.0.1 A launcher app, triggered at boot by Scheduled Task. It would start the KMSEmulator, and could make use of an INI to inject a PID into memory upon start. It would then close and you'd have the KMSEmulator running. Don't know if there is much demand for this since I prefer the AutoKMS way, which is best if you are just handling your PC, but things like LocalHost are best otherwise. The main difference mine would have is allow the PID change to wahtever you choose, but I don't want to do this unless a lot of people want it. EDIT: Memory Address is the same across all variants of KMS Keygen, ZWT/Phazor/letsgoawayhell/Unpacked/Toolkit
I've run IORRT uninstaller and it says it's not installed.... I even deleted it, but it still shows in Ez-activator. Do i need to get rid of it somewhere else?
Check the Task Scheduler and make sure IORRT deleted its hidden C:\IORRT folder completely. Do note that you have to restart the toolkit for it to notice IORRT is uninstalled (My tools are reset upon uninstall of them so this is not necessary for them, but IORRT is an external tool and I'd rather not check for it every time).
Wow you're a Genius.... everything working fine... I can't Thank You enough. Thanks you once again I really appreciate your help
Sorry I missed these posts. In XP we've seen absence of scktaskc.exe in "home" which disallows task creation as does XP non-language versions. Translations parameters such as "daily" and "startup" must be made with IORRT to have tasks be created This is not IORRT problem but XP non-english problem but I myself and team trilgy have occomadated this problem as much as we can Cody has great developments so you are covered thussoafter IORRT install attempt
I don't know if you fixed it but some versions of IORRT were making Vista Tasks (which broke XP). I added the folder detection because in all versions of IORRT you use the IORRT folder. My Task Library cannot read Vista+ tasks (it is meant to be 100% XP compatible library but no Vista+). I had to do the folder thing as a backup means, because when I made my IORRT detector, I found out the tasks existed but were Vista, and told you. I still do the folder thing for legacy and 100% detection, but what issues do you have left with tasks? Also, couldn't you just use the same name across all languages? I do and it doesn't seem to bother anyone. Have you bundled the task maker exe?
This will come up at Team Trilogy discussions and code revisions. Hope our apps can coincide with eachother Later bro
Not to hijack your thread but, can you explain what you mean by "making Vista Tasks (which broke XP)"? Or maybe you can indicate the thread where this is noticed. The language issue was found to be a bug within the Schtasks.exe of XP when using OnStart and Daily settings. There are no bundled files and I believe this is TS's intent.
By making Vista tasks, I mean ones made for Vista (you can see this is Vista/7 Task manager). You need to make XP tasks to work on XP, plus my library can only detect XP tasks. TS had noticed an issue on XP at the time and this explained why I could see the task but could not detect it. If you look at my tasks they say configured for XP. This is how IORRT tasks should be but older versions weren't doing this.
Forgive me, quite a few pages. Whats the preferred method to deal with Office 2010 with Symantec Endpoint? Just popped it in and now at boot I get them popups 2-3x about removing kmsemulator
xclude it by selecting the location of the kmsemulator but first diasable endpoint the let the kms emulator run then exclude it from being detected
Hey there, sorry if I'm not searching enough... but I searched enough to fix my problem and I just have some follow up questions. So on Friday, my Office2010 VL prof plus on win7prox64 started doing some configuration and unactivated itself. I was using Trilogy and IORRT at the time for about a month. timesurfer pointed me this way and I've uninstalled IORRT, and using the toolkit, I repaired my VL for pro plus, then installed autoKMS then hit the activate button (allowed access through firewall) and looks like it's all good now. No activation warnings/red bars. Now I'm wondering what should I be doing to maintain the activation? Many thanks. I really probably should buy at least one copy of office, but I'll address that a bit later
Add AutoKMS.exe and KMSEmulator.exe to exclusions and your activation should be taken care of for good.
I, for one, would welcome such a feature. To be useful for me (and I guess many more people), it should need the following: - Be able to run as a service (to survive log-on and log-offs, and also to survive when you remotely reboot the server and leave it idle at the logon screen for months!) - Be able to work under Windows 2003 as well as under Windows 2008 (both 32-bit and 64-bit versions, though the service doesn't necessarily need to be 64bit) - Have an "install/uninstall" function if it's possible (it's a hassle to remove services manually, though this is not critical) - Have reasonable and moderate RAM and CPU requirements (which means: please, NOT a huge process gobbling lots of CPU and taking hundreds of megabytes of RAM!) Would that be possible?
The run as service thing would probably require external stuff like mini-kms, and I don't really want to mess with this now. Resources would be light and YOu could install/uninstall via toolkit but the thing it I don't see how it would be much different from mini-kms. I figured a launcher or something would help but I'm just asking. Anyway, if I were to pursue such a thing, it would probably be best done modding/extending AutoKMS vs creating another app.