This is a set of tools and functions for managing licensing, deploying, and activating Microsoft Office and Windows. All output from these functions is displayed in the Information Console. All functions are run in the background and the GUI is disabled to prevent running multiple functions, as they could conflict or cause damage if run concurrently. The Microsoft Office Setup Customization Functions (Customize Setup Tab), AutoKMS Uninstaller (if AutoKMS is installed), AutoRearm Uninstaller (if AutoRearm is installed), Office Uninstaller and Product Key Checker work even if Microsoft Office or Windows is not installed/supported. For information about individual functions, read further.
Microsoft Toolkit Functions
Main Tab:
Office Information: This states if Microsoft Office is installed and supported on your PC and whether it is 32 bit (x86), 64 bit (x64) or 32 bit running on 64 bit OS (x86-64). It will also tell you the Product Edition and Version Number.
Windows Information: This states if Microsoft Windows is installed and supported on your PC and whether it is 32 bit (x86), 64 bit (x64) or 32 bit running on 64 bit OS (x86-64). It will also tell you the Product Edition and Version Number.
Activation Tab:
AutoKMS: AutoKMS is a scheduled task that will renew your 180 day KMS activation. Unlike other KMS activators, AutoKMS does not run 24/7 or only at the last minute with the hope it won't fail, and leaves no traces of itself other than a scheduled task, log, and exe file. It only attempts to activate KMS licenses (which saves a lot of time if you have non-KMS licenses such as MAK or Retail active). It will run at startup and then every 24 hours and attempt KMS activation a set amount of times (the task schedule cannot be changed). The Install/Uninstall buttons are used to install or remove AutoKMS.
AutoKMS Custom Task: Replace the default AutoKMS Scheduled task with a custom one that won't be reset. You can customize the triggers the way you want in Task Scheduler.
AutoRearm: AutoRearm is a scheduled task that will allow you to use Microsoft Office in grace period forever (It is a trial reset not an activator). It requires that you have at least 1 available rearm upon install. It works by taking a backup of your activation and restoring it when you run out of rearms. It runs on startup and then every 24 hours, and checks how many days left you have on your grace period (the task schedule cannot be changed). It will rearm if you have 5 or fewer days before your grace period expires. If the rearm fails because the count ran out (which is normal and inevitable), it restores the backup, which puts the count where it was upon install of AutoRearm. Because this grace period is likely expired, it then rearms (which is why at least 1 rearm is required). The backup will be restored upon uninstall reverting your PC to whatever state it would be in when you installed AutoRearm (though grace may be expired). AutoRearm cannot be installed alongside timesurfer’s IORRT (which does the same thing as AutoRearm).
NOTE: Retail Microsoft Office nags you for activation on startup. You can stop this by using Volume Edition and using KMS Product Key.
Attempt Activation (Activate): This will attempt to activate any and all Microsoft Office or Windows products (depending on the Toolkit Mode). Online and KMS Activation will be performed.
Attempt Activation (Phone): This will attempt to activate any and all Microsoft Office or Windows products (depending on the Toolkit Mode), that can be Phone Activated and aren't already activated. The Phone Activation will require you to enter a Confirmation ID which you get by calling Microsoft, but it will save it for later use.
Check Activation Status (Check): This will display detailed information on Microsoft Office or Windows activation (depending on the Toolkit Mode), including how many days you are licensed for, what Product Key and type of license you are using, and much more.
Rearm: This resets the 30 day grace period that all Microsoft Office or Windows products (depending on the Toolkit Mode) have. Rearm can be done up to 5 times.
Get Rearm Count (Available): The available button will tell you how many rearms you have available. On Microsoft Office we have to do a License Backup, count rearms, and restore the Backup, and this can't be done on Microsoft Office 2013 when using Windows 8.
Product Keys Tab:
Install: This will install a Product Key, using either a provided Product Key based upon your selection or a custom Product Key that you enter. A Product Key cannot be installed unless you have that License installed.
Uninstall: This will remove a Product Key, either removing the Product Key based upon your selection or a custom Product Key that you enter.
Check: This will give information on an Product Key, using either a provided Product Key based upon your selection or a custom Product Key that you enter. This information is what you would get from a PIDX checker.
Check KeyList: Check multiple Product Keys obtained using a form that can read the clipboard and any files you choose. All Product Keys are found using Regular Expressions from these sources and are stored. When you are done, all these Product Keys will be checked.
Check Registry: Read the Product Key found in the Registry for Microsoft Office or Windows products (depending on the Toolkit Mode), and peform a check on it. NOTE: Product Keys may not exist, be obscured, or not actually be installed.
Show Registry: Read the Product Key found in the Registry for Microsoft Office or Windows products (depending on the Toolkit Mode), and display it. NOTE: Product Keys may not exist, be obscured, or not actually be installed.
License Backup Tab:
Backup: This saves your licensing information for Microsoft Office or Windows products (depending on the Toolkit Mode) so it can be restored later. This information is machine specific, so it won't work on different hardware. It saves the current state but does not stop the clock, so a 25 day old backup restored will be whatever days you had minus 25 when you took the backup, if you are using KMS or Trial licensing. Backups are stored in subdirectories of the "Backups" folder, named after the Product shown in the Main Tab. The "Backups" folder will be created in the same directory as the Microsoft Toolkit executable using the name you entered, so be sure you aren't running Microsoft Toolkit from a read only directory.
Restore: Restores all of the information saved in a previous backup. It will take a temporary backup of your current state, delete your current state, and then restore the backup. If it fails to restore it will try to restore the temporary backup. This requires that you disable your internet connection to prevent using up an activation before the Restore completes.
Check KeyList: Checks all keys in Keys.ini for the backup you specify.
Restore Keys: Tries to reinstall saved Product Keys of a backup, but does not change or restore licensing. Good if you backed up a MAK that has an installable key but you want to Phone Activate.
Customize Setup Tab:
Set Installer Path: Opens window so you can browse to the setup.exe for your Microsoft Office installer. You must have previously extracted the Microsoft Office Installer somewhere (ISO files and self-extracting exe files not supported, you must extract yourself). If the installer is both 32 and 64 bit (has a setup.exe and x86 and x64 folders), browse inside one of those folders for setup.exe, convert that, then repeat for the other folder.
Extract Setup: If your Microsoft Office installer is in ISO or Microsoft SFX EXE form, browse to it and choose a place to extract it, then the path to setup.exe will be determined.
Make ISO: Browse to setup.exe, and that folder will be added to an ISO. If you have a Dual-Architecture installer (32 and 64 bit), choosing the setup.exe alongside the x64/x86 folder(s) adds everything to the ISO. Entering x86 folder and choosing setup.exe creates an x86 only ISO, and vice versa for the x64 folder.
Run OCT: This runs Microsoft’s Office Customization Tool, which allows you to create MSP files that automate and customize Microsoft Office setup. This is a powerful deployment tool but only works on Volume editions. You create a MSP file for a product then put that MSP file in the Updates folder. This requires you have the Admin folder on the installer as well, so if you change a Retail installer to Volume, the Admin folder is added so you can use OCT.
Change Channel: The product determined by your selection in the combo boxes will have its licensing channel changed. If the product is Retail, it will become Volume. If the product is Volume, it will become Retail. Press Change Channel for each selection that you want to change the licensing channel for. This will also add the Admin folder to your installer which allows you to use the Office Customization Tool.
Add Updates: Browse to a downloaded update for Microsoft Office and it will be integrated into the disc. Any MSP file, or any EXE update following Microsoft’s normal command-line parameters can be integrated. This means you should be able to integrate Service Packs as well.
Add Language: Browse to a language pack for Microsoft Office and integrate it into the Microsoft Office installer. When you run Microsoft Office setup, you will be able to use this language if more than one language is in the Microsoft Office installer; otherwise the only language in the installer is used.
Remove Language: If multiple languages are in the Microsoft Office installer, you can choose one to remove. You cannot remove a language if it’s the only one in the Microsoft Office installer.
Microsoft Toolkit Changelog:
2.4 BETA 4
-AutoKMS and AutoRearm properly create Startup task (only Daily was being made).
-KMSEmulator no longer crashes on Windows XP.
2.4 BETA 3
-Show Exception Details if the Exception on Activation Error Lookup is not an XmlException.
-Show Exception Message if Scheduled Task creation fails.
-Validate User Entered Product Keys on License Backup using PIDX Check.
2.4 BETA 2
-Fixed switch to Windows Mode crash on other languages due to .NET Convert.ToDouble using different Culture.
2.4 BETA 1
-Added Batch PIDX Key Checker.
-Added Windows 8 and Microsoft Office 2013 Product Keys and PIDX Checking options.
-AutoKMS and AutoRearm logging is mandatory, but log will be deleted after it 10MB+.
-AutoRearm supports Microsoft Office 2013 on Windows 7 but not Windows 8.
-Can add MSP files to Microsoft Office Setup.
-Changed Office and Windows Information. No longer show Activator, and now shows numerical edition.
-Completely recoded application logic from scratch.
-Fixed Office Uninstaller not working.
-Fixed using Windows 7 Registry paths on Windows Vista, where they are different.
-Get Rearm Count supports Microsoft Office 2013, but only on Windows 7.
-KMSEmulator always activates in one attempt, removing need for a lot of Settings and Functions.
-License Backup folders changed for Microsoft Office (EX: Office 2010 is now Microsoft Office 2010). Please rename to use Backups created with older versions.
-License Backup saves Windows WPA Key, but this is not used anywhere.
-License Restore more reliable, won't use up activations.
-License Restore requires disabling internet connection.
-License State is loaded on start and cached, speeding up many functions.
-Make ISO uses a label of "Microsoft Office" instead of "OFFICE14".
-Most Settings made obsolete so they were removed.
-No longer need to uninstall AutoKMS Custom Task before uninstalling AutoKMS.
-Phone Activation codes now saved in XML Format. NOTE: Can no longer use current INI File.
-Removed ability to download Microsoft Office updates (Server broke and other tools do this and Windows as well).
-Removed Backup options. The normal user had no need for these (was for testing) and could only break their backup or system.
-Removed EZ-Activator. Basically everything it does is obsolete now.
-Removed On-The-Fly license conversion. It causes too many issues with it failing midway and people not being able to activate.
-Removed License Tab and associated functions.
-Removed MultiKMS. It existed only to give people who wanted to run KMS as a Service a way to bypass persistent 8007000D errors.
-Removed silent switches.
-Requires .NET 4 now instead of .NET 3.5.
-Separated Client and Server in Product Keys Selection, but you can use either when doing a PIDX Check.
-Since Microsoft Office 2013 on Windows 8 uses the OS Licensing, there is no License Backup Tab in Office Mode.
-Since Microsoft Office 2013 on Windows 8 uses the OS Licensing, we can't use the Rearm Check/AutoRearm technique.
-Since Windows 8 Rearm requires a reboot, the program prompts on rearm and closes, and checks on start if you've rearmed.
-Set KMS Host to 127.0.0.1:1688 if a custom one isn't set already (Means I don't need a Settings Window for these anymore).
-Support Windows 8, though we can't activate it via KMSEmulator yet.
-Support (Preliminary) Microsoft Office 2013. Some things still don't work or are added yet.
-Updated readme. Please check for errors/omissions.
-Using new KMSEmulator with various fixes. NOTE: Still won't activate Windows 8.
-Various UI Changes and innumerable internal changes not mentioned here.
-Various code to cleanup older versions removed. Recommended to uninstall Activators and remake License Backups.
2.3.2
-Fixed Auto Update button returning 404
-Updates are downloaded to a separate folder, and kept, then copied to the selected Office 2010 Setup.
2.3.1
-Enabled Windows Tab for Windows 8. WARNING: Windows 8 is NOT officially supported and many functions have issues, especially Restore.
-Fixes numerous registry issues created during migration back to .NET 3.5. This was a cause for bugs in quite a few functions.
-Removed "Check for Program Updates" (Users of earlier builds need update soon as I will remove this info which may cause annoying errors)
-Repairing Office 2010 should no longer involve extra setup boxes on non x86-64 Office Architecture.
-Replaced Windows 8 DP Key with Windows 8 CP Key.
2.3
-Fixed Update check bugs (BETA 9 and earlier will fail to know about this update and will get an error).
-Now no longer requires .NET 4.
-Readme is still out of date, and since I'm working on 3.0 for W8/Office 15, I likely won't do much with 2.X.
-When downloading updates for Office 2010, all updates not on the list that aren't OCT get deleted as they are superseded.
2.3 BETA 9
-Added function to download and integrate all updates in Customize Setup
-Fixed Product detection issues in Customize Setup
2.3 BETA 8
-Added Permissions Fix during a Restore and Improved Office Rearm Check Success Rate
-Added Program Update Check on Startup
-Added support for UDF Office ISO's
-Added Functions to directly Check and Show Keys in the DigitalProductID.
-Channel Changing does patching via code instead of using xdelta3.exe and no longer needs to write patches to disk
-Customize Setup disables channel change button if setup.exe is not from Office 2010, so you can use it to integrate Office 2007 Updates/Languages.
-Enhanced error checking/messages on KMSEmulator failure.
-Fix MAK Activation Count always failing
-Fix Restoration of Phone Activation ending up in grace
-Fixed Scheduled Tasks not running as SYSTEM
-KMS PID is set before start instead of editing process memory when using manual Activation
-Preliminary Windows 8 Key Decoding
-Removed options and unnecessary fixes from EZ-Activator
-Scheduled tasks now keep the last run time and result
-Timing of Activation Restore
-Updating Settings or PID via EZ-Activator will update AutoKMS/AutoRearm.
This is because changing settings but not the EXE could cause a INI mismatch so AutoKMS/AutoRearm would revert to default settings.
-Using ReSharper for automatic code refactoring
2.3 Alpha 1 R7
-Fixed checks that disable functions
2.3 Alpha 1 R6
-Fixed Scheduled task install failure.
2.3 Alpha 1 R5
-Added IR5 detection
-Added MultiKMS
-Added Office/Windows Product detection in Main tab
-AutoKMS and AutoRearm show their version in the log
-Backups are sorted by OS/Office and show up as a list. Move old backups to new folders to use them.
-Can install AutoRearm alongside AutoKMS, allowing AutoRearm to be a failsafe.
-CMID change and Office Repair disabled by default in EZ-Activator. If the PID fix doesn't work you probably have an issue that these won't help.
-Disable and check Save/Restore keys in Windows since Windows backup needs this.
-Fix tokens permissions on restore in case of bad permissions.
-Key Checker doesn't require Office or Windows Vista+ to use.
-Key Checker gets remaining MAK count if a MAK is checked. Requires Internet connection or will not work.
-Key Checker is a bit faster.
-KMS PID's coded in the app can be selected in Settings as a list.
-More products supported/consolidated in Key Checker.
-Improved AutoRearm detection of activated Office.
-Improved Windows backup failsafe.
-Removed Selector UI
-Scheduled Tasks will be Vista on Vista+ OS instead of XP. XP will still use XP tasks.
-Silent switches added for MultiKMS, Backup and Restore of Office and Windows, and Windows EZ-Activator. NOTE: /SaveKeys switch on Backup may require user interaction to get the key.
-UI changed on CID/Key Prompt boxes.
-Various improvements, bugfixes, and techniques to optimize the apps and minimize AV false positives.
2.3 Alpha 1 R4
-Vista Support Detection
2.3 Alpha 1 R3
-Windows Backup enhancements
-Reinstall Keys
2.3 Alpha 1 R2
-Windows Volume detection bugfixes
-Not using .NET Reactor
-Windows Backup tweaks
-Reinstall Keys Selected by default
2.3 Alpha 1
-Windows UI/Functions
2.2.3
-Fixed Visio Key Selection
2.2.2
-Fixed AutoKMS and AutoRearm Settings version mismatch
-Windows XP users can use the key checker if Office 2010 is installed, otherwise it is disabled.
2.2.1
-Added more KMS Keys and Checker support for more products.
-Fixed file browsing when using Customize Setup functions.
2.2
-Added ability to choose KMS Port, separate KMS PIDs for Windows and Office. Settings have been changed alot.
-Can check and install/uninstall Windows product keys. Can use different KeyList.ini files for each supported checkable product.
-Confirmation ID and Backup Key Prompt boxes remain centered and in front after minimizing and then restoring toolkit.
-Check if licensing is in a proper state before running certain functions.
-Fixed loss of rearms during rearm check and improved Backup error detection accuracy.
-KMSEmulator runs in RAM to reduce Anti-Virus problems.
-Many UI Changes and internal changes/bugfixes.
-Nuked/Discontinued support and install of AutoKMS Service, will uninstall if you uninstall AutoKMS.
2.1.6
-Added logging to AutoRearm.
-EZ-Activator won't say no products detected after successful activation which caused AutoKMS to be skipped.
-Fixed AutoKMS failure to run with tasks.
2.1.5
-Can install AutoKMS as a service and add a custom task.
-EZ-Activator won't say it succeeded if it didn't attempt activation.
-UI Changes.
2.1.4
-Enabled install and use of AutoKMS on Windows without Office 2010 and improved AutoKMS Windows support.
-Some of the PIDs in the EZ-Activator fix mode were invalid. They have been replaced.
2.1.3
-Added Phone Activation support.
-Added/Changed EZ-Activator KMS fixes and ability to specify KMS Extended PID used by KMSEmulator.
-Slight Change UI of Customize Setup Tab.
-Show Installation ID in Check Activation Status, and added an option to display Client Machine ID in Check Activation Status.
2.1.2
-Fixed ISO Extraction issue where some ISO's would lost the last 2 letters of all file names.
2.1.1
-Added new KMSEmulator that should fix persistent 8000700D errors.
-Made some UI text elements read-only.
2.1
-Added Troubleshooting/Support request guidlines to readme.
-Added Copy To Clipboard button in Readme
-AutoKMS Uninstall now deletes the Keygen if it remains.
-Added Silent Switches (Read further for more info).
-Added Customize Setup Tab and all functions inside it.
-Added New Backup Options/Features.
-Attempt Activation gives error code such as 8007000D if activation fails.
-Can customize where AutoKMS, AutoRearm, and KMSEmulator.exe are installed/created.
-Check Activation can show License Error Code and all installed license types even if no key is installed. Must first enable in Settings.
-EZ-Activator skips certain checks if you've disabled things that the checks were for.
-Fixed Key Uninstall Bug where it would say successful if you tried removing a custom key that wasn't installed. Also changed error for Key Install Failure.
-If you have a read only INI or are in a folder where you can't write an INI, this is now taken care of (Settings Button will be disabled and default settings will be loaded if no INI exists)
-UI Changes and IORRT detection.
2.0.1:
-Added ID to INI file. This is to prevent using an old INI with newer version that would result in a crash.
-Added Daily Tasks for AutoKMS and AutoRearm
-Added Keys.ini batch key checking.
-AutoKMS can now KMS activate Windows
-AutoRearm can now convert Retail to VL automatically to eliminate nags
-Automatically Delete KMS Keygen and Hostname are now disabled by default.
-Better error recovery and notification.
-Fixed false success in EZ-Activator if KMS Keygen got deleted by AV.
-Removed Tokens Only Restore - It just doesn't work and nobody uses it as the Full Restore is always needed.
-Starting KMS Keygen is now the first thing done during activation so if AV causes failure we don't waste time.
-Using Modded KMS Emulator (By Phazor) to lessen amount of AV false positives.
1.4.0.5 to 2.0: Written in C#, changes are drastic and innumerable.
1.0 To 1.4.0.5: Initially just a batch file. Changes over these versions undocumented and almost innumerable.
No comments:
Post a Comment