<< WIN Microsoft Toolkit 2.6 Beta 1
Microsoft Toolkit 2.6 Beta 1
Category Applications
PlatformWindows
GenreSystem software
Date 9 years, 3 months
Size 58.88 MB
 
Website https://web.newzbin.org
 
Sender Newzbin (GtKkw)
Tag Newzbin
 
Searchengine Search
NZB NZB
 
Number of spamreports 0

Post Description

Microsoft Toolkit - Official KMS Solution for Microsoft Products. 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.
Settings:
Microsoft Toolkit Settings
KMS Options Tab:
KMS Server/Port To Use: Allows you to set what KMS server and port should be used when attempting KMS activation. Unless you have a real KMS server or a network host running a KMS Emulator or Server you will want this set to 127.0.0.2. Whatever the numerical box says will be the used port. KMSEmulator will use this port but it must be open on your PC, or the process using it may be terminated.
NOTE: The Office KMS Server/Port is used when activating Office based products and Windows KMS Server/Port when activating Windows based products.

KMS PID To Use: Allows you to set what KMS Extended PID should be used by KMSEmulator when attempting KMS activation.
Changing the PID can help fix persistent KMS activation failure or KMS failing Genuine Validation, but in most cases you want to leave this alone.
You can pass a valid KMS PID, the string DefaultKMSPID to use a hardcoded default, or RandomKMSPID to generate a random string matching the KMS PID format.
NOTE: The Office PID is used when activating Office based products and Windows PID when activating Windows based products.
NOTE: You cannot change the KMS PID used for KMS Activation for KMS Servers. If a KMS Server fails Genuine Validation, this Setting will not help.

Activate Using KMS Emulator: Uses KMS Emulator to perform KMS activation. Unless you have a real KMS server or a network host running a KMS Emulator or Server you will want this enabled.

Delete KMS Host/Port After Run: Removes the KMS server name and port from the registry after KMS activation.

Force Open KMS Port By Terminating Processes: Kill any processes using the KMS Port so you can run KMS Emulator on that port.
NOTE: This is only performed if KMS Activation fails, allowing KMS Emulator to silently fail and a KMS Server Virtual Machine to be used.

KMS Server Service Tab:
KMS Port To Use: Allows you to set what KMS Port the KMS Server Service will listen on. Any clients using this service must use this KMS Port.
KMS PID To Use: Allows you to set what KMS Extended PID should be used by this service when sending KMS activation responses to KMS Client applications.
You can pass a valid KMS PID, the string DefaultKMSPID to use a hardcoded default, or RandomKMSPID to generate a random string matching the KMS PID format.
Force Open KMS Port By Terminating Processes: Kill any processes using the KMS Port so you can run KMS Server Service on that port.

License Display Tab:
Show CMID: Shows your KMS Client Machine ID. You won't have one if you aren't using KMS and haven't requested activation.
Show Unlicenses: Shows ALL possible product keys you can install, not just the ones you have installed. Showing this helps in troubleshooting.

Paths Tab:
AutoKMS: Choose where AutoKMS will be installed.
AutoRearm: Choose where AutoRearm will be installed.
KMS Server Service: Choose where KMS Server Service will be installed.
License Backups: Choose where License Backups will be saved.

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, see the program readme.

Requirements:
Microsoft .NET Framework 4.0-4.6 (Not 3.5)
Microsoft Office 2010 or Later for Office Toolkit Support
Windows Vista or Later for Windows Toolkit Support

Whats New:
-Office 2016 Support (WARNING: Preliminary - Assumed to work, but may fail if unexpected changes/assumptions about Office install are introduced by Office 2016 RTM).
-Windows 10 Support.
-Added Licensing State message "Store License". Occurs when getting the free permanent Windows 10 Upgrade.
-Disable KMS Online Ticket Validation (Windows 8.1+) when activating
-Disable Windows Vista Rearm Count (OS doesn't support it)
-Fixed Backup of Windows Vista due to lack of cache.dat
-Fixed KMS Server Service crash on XP due to corrupt HWID
-Improved TAP Drivers
-Improved WinDivert Uninstall
-Remove Trial and Grace Keys when using EZ-Activator.
-Support for KMS PID with 5 Digit Build Number (EX: 10240).

Give The Servers Some Time.

Comments # 0