Office 2010 Toolkit and EZ-Activator.

OK I have fixed a lot of things and will release 1.4.0.5 of everything soon in a matter of minutes. The EZ-Activator will be less dangerous on Retail. To anyone stuck in notifications mode, one thing I have tried is to run the keygen with localhost set in the registry, with all office apps closed, then open them. This got me out of notifications mode into fresh rearms (30 days) then I was able to activate.

Easiest way to do this is to delete license info with toolkit, let office repair, when it opens up in notifications mode close the app, try "Attempt activation" If it fails and asks to activate again don't answer, just let it sit (keygen is now running with reg entry set). Open up that office app and wait awhile, close it, then open it to see if it exited notifications mode. If successful it will get 30 days, and it will try to activate using the running keygen.

 

These files are injected into tokens.dat and simply tell Office what types of keys it can install. Those files are already a part of your system if you use Standard VL, however the Standard Retail files are different and would allow you to use different keys.

Interesting thing is that I have found out how to extract these license files from tokens.dat which should allow me to add to my license adder, the VL section is complete but Retail is a bit empty, plus I was able to get Starter license from a Click To Run USB thing.

 

You said your Standard was VL, you don't need to do anything with the tokens, what you need is a MAK key for Standard. If you were on retail Standard and wanted to use VL/MAK Standard key you would use my toolkit's add licenses function, select VL, then Standard, and install MAK key using the toolkit if you want MAK key (It installs VL/KMS key by default.)

 

You are correct, you need the MAK serial, in your case best to stick with VL and do KMS activation which lasts for 180 days but can be redone, unless you have a unblocked MAK key for Standard. You can doKMS activation manually with "Attempt Activation" in toolkit and use the toolkit to install AutoKMS so you don't have to worry about reactivation.

 

I'll have to look into it, but the XML allows for more configuration than the simple create. Your setup will start at boot, mine starts at boot + every 12 hours. I've planned to do a bit more testing of things on different OS, and maybe improve backup and license adder.

 

Glad it worked for you, backup is one thing I want to look into.

 

If you mean the message after EZ-Activator finishes, it means it "may" have failed, it says this to get you to check it for yourself instead of assuming it works, and will always say this. It should be activated by KMS now.

 

OK I found a good way not to have to try and fix reg permissions when backing up. I have been exporting a key as a .reg file, deleting old key and importing, but the permissions assigned don't let OSPPSVC read data so I was running a tool to fix the permissions by assigning Full Control to "Everyone", and this tool can accidently redirect on 64 bit OS and fail to work.

Now I export the key as .hiv, which saves permissions. I am hoping this is good enough, because in theory there shouldn't be conflicts since you are supposed to use restore on same machine.

Also to backup instead of naming it the PC name and only allowing one backup per PC, you now enter a name for the backup and it gets dumped into Tookit Folder\Backups\BackupName. to restore you type out the name.

To restore you enter the name. I want to include something that will generate a unique HWID and create a file with that ID, then check your PC when restoring to see if ID matches and warn if not (since restoring to different PC will likely fail), then give a choice to do it anyway or not, though this ID thing is likely off as I need a commandline tool to do all this.

Since the difference from taking a FullBackup and Token Backup is the reg key, I removed TokenOnly backup, because if you wanted to restore Full and/or TokenOnly you needed 2 backups which backuped the tokens twice. Now its one backup and the TokenOnly Restore just leaves the reg key alone.

This and some more license adding options are in store for 1.4.1.0, I am making stuff more compatible with other OS's. One thing is AutoKMS won't install by XML in XP, and I use TaskKill (which is not in XP Home) to kill processes. TaskKill is in the toolkit, I'll come up with a universal AutoKMS install (I've had a lot of issues with AutoKMS as when it ran as a task as SYSTEM it operated different which I fixed in 1.4.0.5.). AutoKMS will start OSPPSVC if not running like everything else already does.

There is no ETA for 1.4.1 as I have no idea how long it will take me to finish it and test and I have a very busy week.

 

Well since you are using VL it doesn't need converted or any hard stuff.

You can use the EZ-Activator after installing Pro Plus.

What is your OS? If you got XP there are some incompatibility issues with AutoKMS (My Automatic KMS activator). If you have XP better to use the toolkit. Just Choose "Attempt Activation" and look for it to say "Product Activated Successfully", if not try activation again until successful.

 

Just use the EZ-Activator then and it will take care of everything.