Microsoft Toolkit 2.4.4 Stable | 35.40 MB
Official KMS Solution for Microsoft Products
Microsoft Toolkit - multifunctional KMS-activator for the operating
systems Windows Vista, 7, Windows 8/Server, 2012, and Office 2010/2013.
Includes a set of tools for managing licenses and activation. He can use
the KMS-activated, even if you use a retail Retail license. So we get a
single activator for modern products Microsoft.
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.
Requirements
Microsoft. NET Framework 4.0 or 4.5 (Not 3.5)
Microsoft Office 2010 or Later for Office Toolkit Support
Windows Vista or Later for Windows Toolkit Support
KMS Server Virtual Machine for Windows 8 (or Microsoft Office 2013 on Windows 8) Activation Support
PROTIP: Use win8kms.mooo.com as KMS Server to activate Windows 8.
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.
Uninstall Office: Run a script that will uninstall Microsoft Office if you can't manually remove it. Microsoft Office 2003 and later is supported.
Activation Tab:
EZ-Activator: This is a
simple setup for KMS Activation. Unlike previous versions, it CANNOT use
KMS activation if you are using Retail License. EZ-Activator gathers
information about your licensing status to provide the best method of
activation. It can automatically attempt possible fixes in case of
activation failure, and can reverse all changes in case of total
failure.
It automatically installs all KMS Keys for your system, attempts
activation for only KMS Licenses, and if successful, installs AutoKMS
automatically.
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, so don't use
Retail. You can stop this by using Volume Edition and using KMS Product
Key.
KMS Server Service: Install
KMSEmulator as a Windows Service that constantly runs and starts
Automatically, for turning your PC into a KMS Server that can activate
other clients over the network.
You cannot install this alongside AutoKMS, but can set your KMS
Activation Parameters to 127.0.0.2:1688 and installed KMS-Capable
software will use this service to activate every 7 days by default.
NOTE: This
does not use vbc.exe or any in memory tricks, and the Service is
written in C++, not C#\.NET. You will want to AV and Firewall exclude
this service.
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 downloaded updates for Microsoft Office and they
will be integrated into the disc. Any MSP files, or any EXE updates
following Microsoft’s normal command-line parameters can be integrated.
This means you should be able to integrate Service Packs as well.
Add Languages: Browse to language packs for Microsoft Office and
integrate them into the Microsoft Office installer. When you run
Microsoft Office setup, you will be able to use these languages 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.
Credits
-Bosh for the original GUI Design and co-development of Office Toolkit
-ZWT for the original KMSEmulator
-letsgoawayhell, Phazor, nosferati87, and mikmik38 for KMSEmulator fixes and improvements
-MasterDisaster, FreeStyler, Daz, nononsense, and janek2012 for work on Key Checker
Changes in 2.4.4
-Added support for more product key types in PIDX Checker.
-Added support for Windows 8.1 BETA.
-AutoKMS and AutoRearm now have a Login Scheduled Task.
-Better handling of read-only folders and locked ISOs for Customize Setup.
-Compiled as AnyCPU.
-EZ-Activator will check for KMS Server Service before installing AutoKMS.
-Fixed some Yes/No prompts not working.
-Get Rearm Count works on products now, without any license file manipulations.
-Improved Microsoft Office 2013 Channel Switcher compatibility.
-Improved PIDX Checker and added support for more key types such as CSVLK Keys.
-KMSEmulator loaded from DLL in memory instead of vbc.exe.
-Saving Settings will restart KMS Server Service.
-Settings that use a NumericUpDown control can be typed in now.
-Updated KMSEmulator and KMS Server Service.
