Activate your Office 2016 Professional Plus within seconds Believe it or not, KMSPico 10. KMS 20161102. 20170617 1111. Hey, thanks for the great post. Helped out a lot. In my case, I onlywanted to do an Office 2010 KMS host. I didnt care at least for now about KMS for OS or. SummaryExplains how to use the Office Customization Tool OCT to customize Windows Installerbased Office 2013 installations. KMSAuto Lite adalah versi terbaru dari KMSAuto Lite yang dapat anda gunakan untuk melakukan aktifasi pada berbagai macam windows maupun office. Install Kms Host Office 2017 Professional' title='Install Kms Host Office 2017 Professional' />Office Freischaltungen Alle Versionen Sammelthread. Microsoft Toolkit Changelog. Office 2. 01. 6 Support WARNING Preliminary Assumed to work, but may fail if unexpected changesassumptions about Office install are introduced by Office 2. RTM. Windows 1. Support. Added Licensing State message Store License. Occurs when getting the free permanent Windows 1. Upgrade. Disable KMS Online Ticket Validation Windows 8. Disable Windows Vista Rearm Count OS doesnt support it. Fixed Backup of Windows Vista due to lack of cache. Fixed KMS Server Service crash on XP due to corrupt HWID. Improved TAP Drivers. Improved Win. Divert Uninstall. SDP 385880d069b7f491090c3923c3437f6b2 Office Client KMS activation diagnostic. If youve installed Windows with a MAK key and now want to change it to KMS or installed OS never activated, and need to activate WIndows with KMS server, this. Remove Trial and Grace Keys when using EZ Activator. Support for KMS PID with 5 Digit Build Number EX 1. Auto. KMS enables the Windows Event Log Service if it is disabled. Changed TAP Adapter drivers for Windows 1. Moved Win. Divert folder to reduce delete errors. Preliminary Windows 1. Tech Preview Support. Reworked Windows Version detection. Updated Task. Scheduler Library. Added Label to show Microsoft Office Setup Version and Architecture on Customize Setup tab. Added more checks to Add Languages and do better filtering of Language Packs. Auto. KMS no longer attempts activationdisplays error when there are no KMS keys installed. Auto. KMS skips running if a BSOD occurred within 3. Scheduled Task run. Fixed Customize Setup failing if file extensions were not lowercase. Diana F User Manual. Scheduled Tasks now retain their last run date. Updated TAP Driver. Added Channel Switching of Microsoft Office 2. SP1 pure edition SP1 not in Updates folder. Allow Auto. KMS to use EZ Activator routines using command line parameters Auto. KMS. exe EZActivator. Fixed Show CMID not working due to being located in 1 of 2 different WMI SPP providers depending on OS. Fixed Show Unlicensed display never showing if you have no keys installed. Improved Channel Switcher unsupported detection. Added ability to specify KMS Hardware ID. Added KMSPID option to reuse the last KMSPID from KMS Activation. Auto. KMS gives messages about what type of KMS Server it is connecting to. Can install Auto. KMS alongside KMS Server Service to be able to use it for Local. Host KMS Activation. Disabled Default. KMSPID as a valid option for KMS Server Service please change it to Random. KMSPID if you have it set to Default. KMSPID Fixed KMS Server Service Installer arithmetic overflow by changing the way Service Handles were compared to NULL If KMS activation fails twice with DLL Injection, kill KMS Connection Broker with each further attempt KMSPID options not for KMS Server Service set to Reuse. KMSPID by default. Use DLL Injection is now the default Local. Host Bypass method. BETA 5 Added DLL Injection Local. Host Bypass Method Create and Delete IP Routes with Win. API instead of command line No longer require SFX EXE files to Remove or Restart TAP Adapter Prevented exception when Local. Host Bypass IP in in use when using TAP Adapter Bypass Retry up to 1. Local. Host Bypass and you get 0x. C0. 04. F0. 74 error Set DHCP and Static IP addresses on TAP Adapters using WMI instead of command line Warning if more than 1 TAP Adapter is installed before Activation. BETA 4 Fixed registry exception if installing a new TAP Adapter If another TAP adapter is using the Local. Host Bypass IP that adapter will be set to DHCP More Win. Divert failure logging to distiguish it as the cause of 0x. C0. 04. F0. 74 activation failure TAP Adapter used for activation will be automatically removed, and without VPN disruption Updated Win. Divert to 1. 1. 1 Using 2 variants of TAP Adapter based on current TAP Adapter to avoid VPN conflict. BETA 3 Automatically add and remove Windows Firewall permissions Updated Win. Divert to not need MSVC Runtimes Using external loader for Win. Divert to allow multiple runs in one MTK instance. BETA 2 Added Local. Host Bypass options Added Win. Divert as a Local. Host Bypass method Always use IP Configuration in new Local. Host Bypass Settings Autodetect usable TAP Adapter Detect TAP Adapters with numbers 2 in the name Enable All Disabled TAP Adapters on Install Check Fixed License Backups Browse button Restart TAP Adapter if we change IP Address or set Media. Status Set Media. Status1 on IP Change or TAP Listener Start Verify TAP Adapter IP was set to avoid invalid IP parse exceptions. BETA 1 Added functions to get MSDM and Default Product Keys Automatically use TAP Adapter if using localhost IP, localhost string, or Machine Name on KMS V6. Detect OEMM Keys for License Backup and Restore Full KMS Activation support for Windows 8. Server 2. 01. 2 R2 and Microsoft Office 2. KMSEmulator requires TAP Adapter. Improved Network Drive Check. License Backup and Restore will not prompt for Windows Embedded Volume Keys such as Windows Thin PC. Renamed CheckShow Registry to CheckShow System. Activation wont crash if attempting to activate KMS V6 clients which currently cant be activated. EZ Activator will attempt to install Windows Embedded Volume Keys such as Windows Thin PC. License Backup and Restore supported for Windows 8. Windows Server 2. R2. Updated functionality and inclusion of Windows 8. Windows Server 2. R2 RTM Keys. 2. 4. KMS Server Service will properly use Application Specific KMS PID. Fixed crashes on Windows Vista. Fixed Windows Version number detection for Windows Vista and Windows 8. Added Windows 8 Embedded Industry KMS keys. Fixed KMS Server Service crash most common on Windows XP. Removed use of embedded KMS Client for boosting KMS Server Client Count on real servers. Unified Windows Embedded product key sections. Using pure. NET KMS Server for activation. Fixed OS Version internationalization bug that would cause OS Detection to fail or trigger an Exception. Added support for more product key types in PIDX Checker. Added support for Windows 8. BETA. Auto. KMS and Auto. Rearm now have a Login Scheduled Task. Better handling of read only folders and locked ISOs for Customize Setup. Compiled as Any. CPU. EZ Activator will check for KMS Server Service before installing Auto. KMS. Fixed some YesNo prompts not working. Get Rearm Count works on products now, without any license file manipulations. Improved Microsoft Office 2. 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. Saving Settings will restart KMS Server Service. Settings that use a Numeric. Up. Down control can be typed in now. Updated KMSEmulator and KMS Server Service. All KMS PID Settings default to Random. KMSPID due to KMS PID blacklisting. Disable all KMS Server Service settings if it is not installed. Fixed Auto. KMS Scheduled Task paths breaking if you installed or removed Custom Task after rerunning the program. Using new program icon. Added warning prompts for Rearm and Microsoft Office Uninstaller. Allow KMS PID to have a 5 digit LCID. Auto. KMS Scheduled Task works when the local calendar is not Gregorian. KMS Client used to charge a KMS Server with insufficient client count now works on KMS Servers running Windows Vista. More options for KMS Server Service. Settings moved to ALLUSERSPROFILEMicrosoft Toolkit. Please delete or move your old settings. Show KMS Server PID in License Check for KMS Activated licenses. Support for newer Microsoft Office 2. Channel Switcher. Fixed broken validation of custom KMS PID in Settings. How to configure a KMS server in Windows Server 2. R2. Well I have had the pleasure of setting up a KMS server in our environment, and found that the documentation from Microsoft is somewhat confusing. In light of this I will write the steps I used to configure the first KMS server in our organisation for use with Windows Server, Windows client and Microsoft Office activation. These steps will only include the installation of 1 KMS server. Installing first KMS Server. Below are the steps I used to install the KMS server. We determined that due to the number of client activations, and the capacity of our infrastructure we had no problems installing this server on our secondary domain controller. From here on we will call it DC2. Log onto https www. Win Srv 2. 00. 8 R2 Data CtrItan KMS C Note your key may be similar, but either way it must end in either KMS B, or KMS C. On DC2 we run CMD with elevation. Type slmgr ipk xxxxx xxxxx xxxxx xxxxx xxxxx where the last section is the Key from your volume licensing website. Open Windows Firewall with Advanced Security via Start menu Administrative Tools. Under Inbound Rules scroll down to Key Management Service TCP In, right click and select enable. Reboot the machine note you can restart the Software Licensing service but I preferred to reboot it seeing as the server was not in use for anything else. Activate server after reboot. This can be done via the GUI or by executing the following command from an elevated command prompt. Enables automatic DNS publishing by the KMS host by entering the below command in an elevated command promt. Note this should already be enabled, but just in case, we execute the command. Now you are done installing your KMS server. Note this will provide activation for clients andor servers depending on the KMS key you used to activate DC2. Office KMS activation will be covered in a later section. I do recommend verifying that the SRV record in DNS is created. Note that you should have no problems with the automatic creation if you are using the vanilla install of AD and have no specific security restrictions in DNS. To verify that the DNS record has been created open up DNS and check. Refer to the screenshot below to see where it lives Installing Office KMS Host. As mentioned above we have determined that the one KMS box DC2 is suitable to do all of our activations for Microsoft products, so now we have to configure the Office KMS host on DC2. To do this we do the following Log onto https www. Office 2. 01. 0 Suites and Apps KMS Note your key may be similar. If unsure speak to your Microsoft Account Manager. Download the Office 2. KMS Host License Pack from the Microsoft website http www. Family. ID9. 7b. Its only 9. Execute Key. Management. Service. Host. exe from your existing KMS server In our case its DC2. Follow the prompt to finish the setup process. When prompted enter the KMS key for Office 2. Thats it. Just as easy to setup. Now you are ready to activate Office 2. KMS. To help monitor this, please refer the the section below. Administering the KMS server. I take it now you want to see whether it works and if clients can be activated. Now i will go into administering the KMS server, which will be quite brief as there is not much to it, and is really only there to aid in troubleshooting, and to have a sticky beak when implementing it. Once its running there is no real reason to keep going in and checking up on it. All functions to view settings and make changes are done through the already used VBS script slmgr. To see all the commands simply run slmgr from the command prompt. Note to execute changes you will need elevated command prompt. You will see the following screens So the most common command that i used were Displays license information KMS Activation Countcscript slmgr. Displays detailed license informationcscript slmgr. For Office specific information you can run the below command to get the info wanted cscript slmgr. Note I add cscript to the front of the command so that the output stays within the command window, this lets me outputscroll if there is a lot of data where as the usual vbs dialog crops the output. Configuring KMS Clients. By default, Volume Licensing edition of Windows Vista, Windows 7, Windows Server 2. Windows Server 2. R2 are KMS clients. If the computers the organisation wants to activate using KMS are using any of these operating systems and the network allows DNS auto discovery, no further configuration is needed. If required you can configure the KMS client to connect to a specific KMS host, use a specific port and disable KMS auto discovery. When deploying KMS clients using WAIK you can use 2 different methods to prepare the client SYSPREP run Sysprep generalize which will reset the activation timer along with removing SID and a few other settings. Read about this before actually using it. Software License Manager run slmgr. Note you can only perform this 3 times in total. You can also manually force activation of the client by using the GUI from Control Panel System or by running slmgr ato. If you want to convert MAK installations of Windows or Office to KMS, you need to change their product key, and then reactivate. Use the below keys to perform this Operating system edition. Product key. Windows 7. Windows 7 Professional. FJ8. 2H XT6. CR J8. D7. P XQJJ2 GPDD4. Windows 7 Professional NMRPKT YTG2. K7. D7. T X2. JMM QY7. MGWindows 7 Enterprise. PXH 7. Y6. KF 2. VJC9 XBBR8 HVTHHWindows 7 Enterprise NYDRBP 3. D8. 3W TY2. 6F D4. B2 XCKRJWindows Server 2. R2. Windows Server 2. R2 HPC Edition. FKJQ8 TMCVP FRMR7 4. WR4. 2 3. JCD7. Windows Server 2. R2 Datacenter. 74. YFP 3. QFB3 KQT8. W PMXWJ 7. M6. 48. Windows Server 2. R2 Enterprise. 48. J6 VHDMP X6. 3PK 3. K7. 98 CPX3. YWindows Server 2. R2 for Itanium Based Systems. GT6. 3C RJFQ3 4. GMB6 BRFB9 CB8. VWindows Server 2. R2 Standard. YC6. KT GKW9. T YTKYR T4. X3. 4 R7. VHCWindows Web Server 2. R2. 6TPJF RBVHG WBW2. R 8. 6QPH 6. RTM4. Office 2. 01. 0 Suites. Office Professional Plus 2. VYBBJ TRJPB QFQRF QFT4. D H3. GVBOffice Standard 2. V7. QKV 4. XVVR XYV4. D F7. DFM 8. R6. BMOffice Home and Business 2. D6. QFG VBYP2 XQHM7 J9. RH VVRCKOffice 2. Stand alone products. Access 2. 01. 0V7. Y4. 4 9. T3. 8C R2. VJK 6. 66. HK T7. DDXExcel 2. 01. 0H6. QG HXVKF PP4. HP 6. KMR CW9. BMShare. Point Workspace 2. QYYW6 QP4. CB MBV6. G HYMCJ 4. T3. J4. Info. Path 2. 01. K9. 6W8 6. 7RPQ 6. T9. Y J8. FQJ BT3. TOne. Note 2. 01. Q4. Y4. M RHWJM PY3. F MTKWH D3. XHXOutlook 2. YDC2 CWM8. M RRTJC 8. MDVC X3. DWQPower. Point 2. 01. 0RC8. FX 8. 8JRY 3. PF7. C X8. P6. 7 P4. VTTProject Professional 2. YGX6. F PGV4. 9 PGW3. J 9. BTGG VHKC6. Project Standard 2. HP3. K 8. 8W3. F W2. K3. D 6. 67. 7X F9. PGBPublisher 2. 01. BFK7. F 9. MYHM V6. C7 DRQ6. 6 8. 3YTPWord 2. HVHB3 C6. FV7 KQX9. W YQG7. 9 CRY7. TVisio 2. Visio Premium 2. D9. DWC HPYVV JGF4. P BTWQB WX8. BJVisio Professional 2. MCW8 VRQVK G6. 77. T PDJCM Q8. TCPVisio Standard 2. HD QGMWX 8. QTDB 9. G3. R2 KHFGJYou can convert Windows and Office from MAC to KMS using the GUI available, or you can use the following commands Windows. To install a KMS key, type slmgr. Kms. Key at a command prompt. To active online, type slmgr. To activate by using the telephone, type slui. Office. To install a KMS key, type ospp. Kms. Key at a command prompt. To active online, type ospp.