Office 2010 Toolkit and EZ-Activator.

Just to let everyone know how development is going:

I implemented ability to use ini file in AutoKMS and Toolkit, to allow more flexibility and control. Bosh is replacing where the EXIT button is (bottom right) with a settings config that will let you choose your settings and apply them.

Some things added is that EZ-Activator will attempt solutions by default. I can automatically rearm and reinstall license files. I can auto repair office but its unreliable now.
(I check what’s actually installed, repair one of its msi (silently, I need to see it to test though) (Works on my VM but not my real PC). This fixes effects of License Delete and after successful repair any other products are License Added. Thing is this requires reconversion, and then try again. If fails again it just won't work ad needs reinstall.

So the msi repair is a problem. Another issue is I run vbs file for uninstalling office, but in my VM test it gets to a point and hangs, never finishing.

Excluding these issues, I am thinking of making things more efficient and changing the way I do some things.

Some things we do involve using ospp.vbs or running a batch command, saving the output. There seems to be overhead with this. If the command is to have a lot of output (like if you install all licenses and press check) it hangs.

I want to eliminate use of ospp.vbs. Anything we use it for can be done using WMI. I call to WMI using md which suffers the previously mentioned issue.
I can remove keys by license/type, not actual key (this is how I made EZ-Activator remove retail key without knowing it).Somehow I can install a key as well. I can set and remove KMS hostname, activate product (This is how AutoKMS only activates KMS and EZ-Activator does it one at a time). I can get the licensing state and grace of a product (like days if it’s activated or rearm/notifications mode.) I want to collect the info, display it in a user friendly way (As some people don't understand the results of Check).

To make this work I can use WMI, but I need to use real code vs. using cmd and relying on it. Doing this will eliminate a lot of32/64/WOW checks as the WMI call is the same no matter what. Using native code will make it much faster, in both real and perceived speed. Some things simply feel slow because you see nothing until everything is done and displayed in one go.

I just need to figure out how. I can make it totally independent of ospp.vbs, only needing OSPPREARM.exe which has no WMI call I'm aware of and works fine is. I cannot achieve what I say now without direct WMI as the overhead and issues screw it up. I wanted to make a activation status like Win 7 loader but to run the checks with multiple office apps was slow and could lock up rendering toolkit useless. EZ-Activator uses a dumbed down and optimized version of those checks but is still slow if you have a lot of stuff installed (an irregular but possible scenario, imagine running license add for everything and you get that state.

Using the WMI allows for consistency. I know commands can execute differently on XP.

BETA 3 will fail to create AutoKMS task on XP because task make command on XP cannot support /F (Force - Overwrite) parameter. I made a separate XP check but that in itself is inefficient, a waste of code and effort. I'm thinking about adding it under "Run" reg key. It will run at boot like now. If someone wants to change it, I have toolkit option to not delete Keygen and localhost, so someone could use their own script or make their own task for AutoKMS. AutoKMS was meant to keep it at 180 days, without concern, use it any other way (say once every 175 days) and you may as well just use EZ-Activator manually.

 

EZ-Activator installs AutoKMS. If you have it installed you'll never have to worry about reactivation.

No office updates out cause any trouble. If its not OGA or a SP its probably safe.

 

Probably won't work, worth a shot though as it will fix it if it fails, bring things back to before you tried the restore (So your license doesn't get marked as tampered).

 

It runs at every reboot, not every so many days or hours. I assume 99% of people will reboot at least once every six months.

Anyone who regularly uses the newest software or updates has to reboot regularly. If you don't fit this description you probably didn't jump to Office 2010.

Also, even if it totally expires, it should still be able to reactivate when ran.

 

Add license enables use of certain product keys. Its main use is to enable use of VL keys on retail. It still must be activated.

 

I think he means using License Add on VL to add Retail License. This works if you have real retail key. (Keep in mind unlike MAK (which is VL) retail has like up to 10 activations (MSDN, I think store retail is even less). Leaking a retail key online blacklists/uses up instantly. Still, I add leaked retail keys so people can use Key Check to see the key and get past Retail install screen.)

For example I got Legit MSDN Project Pro key. I got VL Project Pro Installed. If I wanted to use my MSDN key on VL I add Retail Project Pro license, install MSDN Key, then activate.

This DOES work, if it didn't, providing retail licenses would be useless.

PS: Toolkit contains license files for EVERYTHING, Retail or VL (Unless server Office Apps like SharePoint Server have them, which the things I've looked at don't)

Also, BCM shows it uses same license files as Home and Business (Something called Bypass-Trial, you get 60 day trial without online activating trial). Weird thing is it does not seem to use it. I install BCM, it adds HomeBusiness-BypassTrial for 60 days. there is no prompt or activation in BCM app (Outlook). Removing key does not disable BCM. Its weird but those license files it adds are from Home Business Retail (There is no VL HS, HB, or Pro)