Office 2010 Toolkit and EZ-Activator.

@Bosh Here is some explanation on some of this. Ask anything else if you need to:

Licenses VS Keys/How Office Apps handle this:
A license is a set of "slics/XRM-MS files" that when installed into the license store allow you to install a product key for that license. Key != License since you can't have MAK+KMS keys active at the same time for Pro Plus.

Here is how Office works with this. When you start an office application, it first checks the "Registration" keys in the registry to figure out what SKU/Suite the app belongs to. You could install Standard and Pro Plus suites, both have Word, and the registry can tell it it is both. It will then ask OSPPSVC for info on the associated license. You could have word a part of an activated standard and unactivated pro plus, it would act activated but checking Info in Word would show one "Product Activated" and one "Not Activated". Remember the pictures letsgoawayhell posted of Retail+VL Pro Plus where I pointed out it looked strange 2 things showed up.

You can uninstall say, the standard key, and now word will only show the pro plus part, which in this running example is not activated, so it will act that way. It does not show standard since OSPPSVC knows no key is activate to give license info for so it doesn't use it. Now, if you uninstall the Pro Plus key, and reopen word, it realizes none of it's licenses have keys, so it might reinstall keys or prompt for them. Do note that uninstalling and reinstalling a key can retain activation. I noticed if I phone activate my MAK, switching to KMS key and going back to MAK, it is in grace. This is only for phone activation, so it is capable to KMS activate, then MAK activate online, and the old KMS status is stored still in the license store, switching back and forth between KMS and MAK keys will switch back and forth between activated licenses.

Conversion:

What we do in conversion is force a Retail or VL channeled product to use the opposite channels licenses. As I said before you open an office app and it checks what SKU it is in Registration. We can add keys so Word Retail can see itself as VL (it can see itself as Retail and VL at the same time just as if they were Standard and Pro Plus like earlier). So this allows Retail Word to read VL license and act on it. We installed the slics so this license is a part of the license store, and can be activated and used. With EZ-Activator, we complete matters by uninstalling the retail product key so the user's word does not show unactivated retail license in info. Since we wouldn't have converted if Retail was activated, it is unactivated and we simply remove the key (remember this means it will now disregard the retail license totally like uninstalling Standard key in earlier example). Word or any office app is the same on retail VS VL and any differences observed in their behavior are dictated by the slics. We can't change the slics because they are signed, but if we could we'd have unimaginable power over office activation/licensing (could have more rearms, longer grace, even disable notifications/activation. Read the slics as an XML file and you'll see stuff like this specified in it).

License Add/Remove/Repair:
As I said installing slics adds to the license store, and I got the slics by ripping them out of office installers MSI files. We can add slics but it is impossible to remove them. Having too many installed can make OSPPSVC WMI insanely slow, and both toolkit and ospp.vbs rely on this WMI, so it could take 10 minutes to show license info if you install ALL slics. A license add simply adds the slics, though it is not possible to remove them from an existing license store, so there is no license uninstall. Removing the product keys can help the WMI lag since our normal checks/use of WMI doesn't bother with licenses without keys.

How the license repair works is this. I first delete all stuff related to licensing (The tokens, registration reg key, and OfficeSoftwareProtectionPlatform reg key). I then have to call office MSI files to rebuild it. If dealing with a 64 bit OS, I may have to first repair a specific MSI (Shared Components of something like that) before the other MSI. The other MSI is the main MSI for office. Pro Plus part of the SKUID is 11, and the MSI I called has this in its code (see EZ-Activator repair code function for more info Bosh). After those MSI files are repaired, we have a "blank" license store. Opening an office app would still do repairs which would add the slics for installed SKU's, but we just call our license add and we can do this for office setup and the user. We have rebuilt the license store to a valid state, but OSPPSVC marked it as tampered since we made it repair (we fix this with activation, but the repair was if the store was shot in the first place).

Do note with our license add, since slics without keys are a waste, I install keys as part of the license add. However, I do not have retail keys for many products, so the only way you can see the effects of the license add of this is in verbose mode (you can see named licenses without keys there, and this would tell you Word Retail was added but had no key).

Product Keys:
The license store will associate a key with a license, but the slics are independent from the key. We can uninstall a key to make office not use a license. Also, you don't need to type a key to remove it with the toolkit (unlike ospp.vbs which demands the last 5 digits - still gettable from ospp). Rather, if you select the right license combo, I use OSPPWMI to remove the key by SKUID, I don't even need the last 5 digits. You only need to type if you check custom, which is meant for Add/Check, but we still provide removal for that custom key, or its 5 digits for the sake of completeness/functionality.

 

Either KMS Host is not set or KMSEmulator isn't running.

 

Use default toolkit settings and disable AV.

 

Object ref error means something killed KMSEmulator.

 

You can change the path in settings and delete the old one.