Office 2010 Toolkit and EZ-Activator.

It will redo KMS activation (which lasts for 180 days) at boot and every 12 hours, in effect keeping you at 180 days activated. There is no limit to KMS activation, you are thinking of 30 day rearms which you have up to 5 of.

 

OK I would like to add non default install path support but it complicates things just to make it work for a few people who adjust install path. First I have ospp.vbs and ospprearm.exe in the toolkit update I am working on. The toolkit can be ready to support this soon if I can know one thing: If you install Office 2010 to different path/partition, does this cause the tokens.dat to be located elsewhere?

For the EZ-Activator I don't quite know about supporting this as I need to know the office install path to check if Visio, SharePoint Designer, or Project exist (I assume you can't install different office apps/suites to different paths). Also I need a way to check if office is 32 or 64 bit and checking the default paths gives an easy way. Another question I have is does OSPPSVC.exe locate in same path if office path is changed? I can't think of a reasonable way to check if visio, etc exists if they can be anywhere.

 

Can you use my toolkit's "Check Activation Status" and screenshot it for me?

 

Chances are the you used the EZ-ACtivator which installs AutoKMS. Activation may have succeeded later after running activator.

 

EZ-Activator is recommended for people using RETAIL office as it converts office to VL. The cleanest way to activate is to install VL Office, activate using my toolkit's "Attempt Activation", and you could either manually reactivate the same way (so nothing is on your PC like installed tasks) or install AutoKMS using the toolkit which will take care of reactivation.

I recommend not using EZ-Activator with VL office as it goes way beyond what is necessary. Simply activate with the toolkit/mini-kms and install AutoKMS with the toolkit if you have VL office naturally without conversion. The EZ-Activator converts retail into VL (which is OK if you have VL) and then tries to activate by KMS. It is meant to be a works regardless of what office you have installed.

PS:Chances are that missing file is AutoKMS or the keygen. Some things can get detected as FPs by AV and deleted (I add exclusions for AutoKMS on my NIS 2010).

 

Now that I think about it, I'd like to avoid the whole conversion thing if already VL and just activate by KMS (changing key if necessary). I have to look into some registry tricks I thought of to find this info which could also replace the determine if office is 32 or 64 bit by install path.

I think the EZ-Activator method right now is geared for retail (since VL users can just use default key any one of the KMS activators), but I want it to do the best thing for whatever is installed. I feel that when converting to VL it is best to do Pro Plus since it will work no matter what suite is installed.

 

OK The new 1.3.5 stuff has been greatly improved. I managed to get both EZ-Activator and the Toolkit to work regardless of office path and still figure out whether on 64 bit office the installed office copy is 32 or 64 bit. I removed the Auto Silent Restore Tool since it is useless and never really took off and fixed registry redirect issue (If your OS is 64 bit run the 64 Bit version of EZ-Activator that has been optimized for 64 bit, if your OS is 32 Bit run the 32 bit version.).

The EZ-Activator is now more flexible. If ALL your office installs are VL (nothing is retail), it won't screw with your registry or licensing files which makes it cleaner and more reliable. It will take awhile as it will install KMS serials for everything (Only what you have installed will install, this is to ensure you have KMS key and not MAK key installed), then activate and install AutoKMS. If you have Retail Office it will work the same process as usual, convert office to VL, check for Visio, Project, and SharePoint Designer and install the right keys and activate and install AutoKMS.

I get the install path of office from the registry, go to that directory, and check for Visio, Project, and SharePoint Designer. You can have a non default install path but you can't have Office installed in different paths at the same time, such as installing Pro Plus to C:\Office and Visio to C:\Visio. This is a bad idea anyway since it will eat up more space to copy common component files in multiple places.

I check if Office is VL or Retail by the SKU in the registry and I determine if it is 32 or 64 bit office by the location (If the key shows up under Wow6432Node) of the InstallRoot Registry Key.

 

Norton bothered me about some of the exes I made, it hasn't cared about the keygen though. Also another thing that can show up as missing is at the end the batch will delete the temp folder it was extracted to but if you ran it as a batch (EZ-Activator to fix reg issues) then this folder didn't exist at the end but its so fast at the end before closing you have to pay close attention. New Activator doesn't need extracted on 64 bit to work, there is a separate 64 bit version that doesn't get redirected. EZ-Activator DL contains 32 and 64 bit exes.