Office 2010 Toolkit and EZ-Activator.

Title changed. I'm gonna send @Bosh my MTK source and see what he can do to the UI, now that I'm on a college internet connection that doesn't suck massively like at home.

 

OK Bosh the source is up. The next thing I'll probably code is C2R conversion if possible. OTK part is largely complete short of changing code structures to make it easier to port code to the next office (which I can't really do till I know what that throws at me.) Basically short of making the network kms tool and C2R support, I think I've beaten down all ideas for office I could come up with with OTK being out for over a year. I'm trying to add all I can now, and have things largely solid until next versions of office or windows are out. I'm mostly there, I'm watching this thread for bugs that occur more than one user to try and compare.

 

I'll PM him and see what he comes up with. I thought about making the buttons nicer and using an image for the currently grey box. I kinda liked the look of the W7 Logoff/Shutdown for XP.

The "W7" task is the same as office. AutoKMS runs itself via the task it always has, and decides how to handle windows and office.

Actually AutoKMS and AutoRearm haven't changed at all in MTK. MTK = Selector UI + Windows Toolkit Added to Office Toolkit.

Basically what I did was add new tabs, like Windows has a main tab and office has a main tab. The selector UI dynamically changes title/icon and hides tabs for the chosen toolkit that shouldn't be there (the customize setup hidden in Windows Toolkit, for example).

Allows me to have one GUI code file regardless of the toolkit, since once you hide the right tabs the only difference is calling a function from its windows or office class.

 

As far as this C2R thing goes, I have to determine how to 100% reliably ID C2R (won't just check for Q. Then backup and license install (maybe repair) have to be modded to import/export into the virtual registry. The only thing C2R breaks is Registration key. All the WMI calls are the same, and all the guts of licensing are out of that bubble.

 

I did plan on a new icon, but there won't be any non usable stuff. I just hide it. I do this so all the tabs fit in the UI without an arrow scroller needed which I find looks like crap. There will never be a Customize Setup tab for windows in the forseeable future, and the license tab doesn't make sense since only OEM stuff is worth installing and there isn't really a "repair" needed. You really have to screw up windows bad to not be able to fix it simply, and if you have you need to PE it. I find deleting the tokens, IR5'ing the WPA key, and rebuilding the tokens to be a 100% repair, and I can't think of any case where windows is this botched.

Honesly given the breakthroughs in KMS, nobody really needs the repair unless office is screwed up. You really can't short of AV interference or a bug, not get EZ-Activator to get you going via the PID fix. I check if office is broken and tell user to repair, and I don't think I've seen a user that didn't have AV/Bug post a log where EZ-Activator had to go past the PID fix (no CMID change/repair stuff and I removed the reinstall license/rearm since it never worked and repaired anyway 99.99999% of the time).

Short of giving back rearms, and office really being broken (and nothing is stopping from doing a setup repair in the latter case, Repair is just a shorter and atumatic equivalent anyway), repair is falling in importance. It was major when my main fix was a CMID change. Even Phazor tool never permanently changed the PID, he preferred to change the PID to null, activate, but then tell the user to rearm and reactivate. It was simpler that way, so he didn't have to keep track of PID or change it every time like I do. I prefer the memory change, because I can change by patching the file but one has to stop/start (don't want to do that multiple times). But if memory injection was giving AV issues (it isn't for the PID change stuff), I could axe that code and just file patch.

So if MS breaks repair in the next office, I probably don't need to code a new one. I have it hardcoded with the SKU codes.

 

I was looking into a much faster repair for office anyway. I can 100% rebuild tokens. Basically delete them, restart OSPPSVC and it makes 17KB tokens. Install some special licenses I have (they are in the MSI like the others but aren't added in OTK anywhere). After installing those, install normal licenses.

Problem is I don't know how to rebuild the trusted store. OSPPSVC won't just remake it. The reason I run the MSI repair (note repair wasn't meant to fix broken installs, but to force change the CMID), is because the MSI builds the trusted store from scratch somehow (while it installs the OSPP stuff, which is why only certain Office MSI's can be used).

 

I should be able to run under the assumption that since the all the main c2r are suites (I think individual apps exist but rare, and starter = auto activated), that C2R won't exist alongside non C2R. I don't even know if MS makes it possible to do that kind of install, but its extremely unlikely and most like a broken and hacked up setup anyway.

 

What do you mean by "replace tokens"? As far as I know you have a backup app, and in my tokens restore I just stop OSPPSVC, overwrite tokens, start OSPPSVC, and reinstall key. I'm talking about how to delete/corrupt the existing tokens and then get them back to an activatible state (notifications). I do the repair to get this stuff rebuilt (registry as well), but I know how to remake tokens without any MSI. It requires all the license files + registration keys. Where I am stuck is remaking the trusted store.

PS: Important thing to note about an office tokens restore. You need the trusted store to be in good shape. If it's fubar'd then you won't be able to restore properly. Basically a tokens only restore by the key install shoves the tokens state into the trusted store.

 

Now I'm baffled. I got conversion working via EZ-Activator without changing a thing. Everyone with an issue said they got a prompt that said enter a key. Maybe your office is just screwed in that case.

hope I'm right, MS doesn't add the exe I need in C2R.

 

I'm sure all you need to do is stop, delete, copy, start. You let it try and create its own little tokens just to nuke them, but that isn't necessary, at least I don't do that.

 

Well it seems I could convert. Repairing C2R is a whole different story. Not sure if I'll be able to, but I'm thinking about phasing out the repair. I shouldn't be using it for activation troubleshooting and now its doing more harm than good. The PID fix pretty much nails all activation issues, and if office is botched bad enough, my repair button doesn't quite cut it.

 

It says "Out Of Tolerance". Office thinks your machine has changed enough to deactivate (either you changed your HW or something or MS just has buggy crap). You just need to uninstall AutoKMS and rerun EZ-Activator.

 

I'll look into this, the switches usually aren't tested much. It will take a little while as I have to get my PC to take a PID it hates and then try the switch. Until then the GUI is working. I must be handling things in a way that breaks in the cmd, not sure what, but something is different.