Office 2010 Toolkit and EZ-Activator.

@Bosh I've done a lot of UI changes to make the toolkit UI look more consistent. It looks like the Customize Setup tab changes you did last.

 

I've got it aligned nicely, but I've got a lot of changes put in so far and still going on my time. I'm doing summer college classes to graduate early and this is the last week of the first 2 out of 3 (that means finals and all that crap next week). That and I've been playing Black Ops alot.

Mostly cosmetic but allow the UI to be reused almost unchanged for another planned tool.

 

The changes so far for those interested.
-UI reworking
-Checks in EZ-Activator/License Repair to not run if Windows Installer is running (as license repair depends on it not being busy).
-Addition of Vista and Windows 7 KMS Keys.
-Removal of dead Retail Office 2010 Keys.
-Ability to check Windows Vista/Server 2008/Windows 7/Server 2008 R2 Keys with the key checker.
-Use seperate KeyLists (just text files with keys in them line by line so you can batch check keys) for above feature.
-Can install/remove Windows Vista+ Keys
-Can in License Backup simply reinstall keys without touching anything. Good if you switch between KMS and MAK like I do in testing.
-Use any port you want between 1-65535 (assuming it isn't in use) for KMS Activation and patch KMSEmulator.exe to use this port.
-Use separate KMS PID for Windows and Office KMS activation.
-Can choose whether AutoKMS activates Office like you can for Windows.

Planned Changes:
-Move default KMSEmulator path to C:\Windows\KMSEmulator (a folder). This is for use with a feature I plan in a different tool.
-Add better support for click 2 run and singleimage installers if possible (I'm referring to license repair and possibly conversion).
-Make AutoKMS attempt PID change upon failure with an option for windows and office.
-AutoKMS will skip windows activation if it is not volume/kms (it blindly attempts to activate whatever knowing only one key is activate but if it is online this is slow/wasteful).
-Modify my source/settings such that I don't have to gut/mod source code files to create AutoKMS and AutoRearm. Likely I will use one settings file type and this would kill the need to have some settings appear in AutoKMS and global.
-Deal with anything SP1 will throw at us but I don't expect SP1 issues.
-Attempt to simplify License Repair as the code is very complex to handle all possibilities.

PS: Anyone know when SP1 comes out? I have held back all Office 2010 updates knowing it is supposed to come out this month
-

 

Given that I'm going to make a new KMS Server and the route I'm going it with it conflicts with the plan, AutoKMS will no longer be a service, it will go back to being local only, and a new service will be made. This is so AutoKMS local settings don't interfere with server activation. AutoKMS uses one KMSEmulator and canonly have 1PID, which if we change it for local we may make some network client fail.

That and because I'm going to make the service capable of multiple KMSEmulators on different ports so you can use different ports and PID to serve all needs ofnetwork clients.

 

Office SP1, I'm running Win 7 Ultimate x64 SP1 now.

 

It's most likely MS being heavy on it given it activates their apps. That being said the DL here is 100% safe so get the toolkit here to be sure.