:::Readme for $oem$ folder for KMS Server Service 2.4.3 v2 -murphy78::: MTK 2.4.3's "KMS Server Service.exe" Size: 288KB CRC32: F2ECE63C MD5: E8C965A3FADE7CEA724BE2E561CCE0F3 SHA-1: 77A25890389A6DFBB572C4E2F379B58BCC001E27 :::Changelog::: v2 for MTK2.4.3 -Moved the meat of the process to the setupcomplete.cmd. Back when I did the reg import I had problems using setupcomplete.cmd -Changed Post-Setup.cmd runonce so that it functions as a sppsvc.exe detector and scripts folder cleanup. (If you run a slmgr /ipk it will lock system folders for approx 30 seconds. Using the setupcomplete for the work and a runonce for cleanup, the system will have long enough that if you install a product key, by the time the system finishes installing, the sppsvc.exe will self-terminate and allow you to once-again delete the scripts folder.)(Post-Setup does not loop. It will search every 5 seconds for 50 seconds, then give up and exit if the sppsvc.exe is still running. It's really not a big deal if the sppsvc.exe never stops running and you don't delete the scripts folder, but I like to be tidy) -added firewall lines again. (This time I tested it on my network! :) s1ave77 had it correct in his scripting. Uncomment the appropriate lines in setupcomplete to enable either network activation, or internet activation. This only needs to be done on the activator system. My test setup did not respond to pings, but successfully activated once the firewall settings were added. I added a Add-Firewall-Settings.cmd script to the KMSServerService folder for those that might want to enable it after installing, but not during. You do NOT need a firewall setting for self-activation or self-renewal. v1 for MTK2.4.3 -Removed the Reg import of the original installed version. (Unreliable on custom windows) -Added sc config description and sc config group. -Added the KMSServerService to WMI group so Windows 7 users will have instantaneous re-activation renewal. -Removed Firewall settings. They don't do anything. Your system will have firewall permission already. Any firewall problems you have will be your own doing. Windows defaults to allow access. -Removed the xml settings copy. This is not needed. It is simply created when you run MTK, but is not used by KMS Server Service. -Added a pause to the Activate-Windows.cmd script so people can read the results like they can with s1ave77's office script; though the office script will still error-out without a pause if no Office versions are installed. -Uninstall script no longer needs a reboot, Thx SC STOP! -Went around and changed everything with C:\Windows to %WinDir% for the oddly-named windows directory ppl v2: -Removed install script. People were trying to use this as an offline activator. You can already do that with MTK241. I have no intention of making another activator. I only intend for this to be in a Windows Install. -Removed product key lines from Office script and unused exit function lines as it errors out if no Office is installed. Key is useless when conversion is not done; just slows down activation, and will not correctly fix any problem with multi-keying. You would need to uninstall or rearm to do that. Unnecessary. -Added reg import of the actual reg entries that MTK creates for the service. x64 version has a SYSWOW64 key, else it is the same as the normal x86 version. The KMS Server Service.exe works on either x86 or x64. -Added settings.xml file and copied over to the proper location in users\%username%\appdata\local\Microsoft Toolkit\ The settings.xml is used by MTK, and although not required for the service, it will help identify things if you run MS Toolkit. The settings are set to 127.0.0.2 and port 1688 with RandomKMSPID. -Added outgoing firewall setting for people who disable outgoing firewall by default. non-local activation is still supported but commented out of use. You need to uncomment the line in the script to enable it. :::Features::: -Pre-added A/V exclusion. (I will not help people figure out how to get post-setup A/V exclusion permissions. Dont ask) -For Windows 7's Security Essentials, it's not pre-installed so you shouldn't add a key for that. It does not use the defender exclusion list so you need to add it manually. -Should be able to use MTK after install to change the settings around in KSS if you want.* *Note that reboot or sc stop/start is required currently in 2.4.3 after changing settings. *You also need to re-activate after the restart or the new settings won't actually be applied to your system. *If you change your IP or port, you need to change the activate scripts. -.NET4 is NOT required with this $oem$ folder, but you would need it to use MTK to change settings afterward. -Can activate other people's systems as long as they point their activation at your computer and you have the appropriate firewall setting added. Example: slmgr /skms 192.168.0.2:1688 (where 192.168.0.2 is your activator computer on the network) -Slightly faster than AutoKMS -Once set up and activated correctly, should keep re-activing your system every 7 days. -Automatic Windows Activation using the service using runonce after it creates the service. (Done at first logon. Windows 8 setup from boot did not display watermark. Upgrades may have delay till watermark disappears, I haven't tested windows upgrades on the service) Added optional scripts to KMSServerService folder that MTK creates. -Activate-Office.cmd (slightly modified version of s1ave77's script that will activate VL office editions) (Seems to attempt to activate all Office 2010 versions and 2013 versions, even uninstalled ones, just in case) -Activate-Windows.cmd (you guessed it, activates Windows) -Create-Daily-Restart-Task.cmd (Creates a daily and boot task that resets the KMSServerService) (Resetting the service should not be necessary at all. Some people, however might want to run this as a long term activation server, and hence might want to change PID by restarting once a day) -restart.cmd stops and starts the KMSServerService. It is called by the daily task, but you can use it any time you want if you run as admin. -Uninstall-KMSServerService.cmd (Removes Settings Windows KMS-host cache, Daily Tasks, KMSServerService) -Add-Firewall-Settings.cmd (Post-Install firewall setting adder for people who want to add the ability to activate people on their network or people on the internet. (You have the choice of which.) Self-Activation does not require a firewall setting. :::General Use::: This $oem$ folder was intended to be placed in the \sources\ directory of a windows version that uses KMS install. It needs to have a gVLK already set. If you haven't already set it, you can edit the setupcomplete.cmd line: cscript %windir%\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX Some useful gVLK are: FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4 (Win7Pro) MRPKT-YTG23-K7D7T-X2JMM-QY7MG (Win7ProN) BN3D2-R7TKB-3YPBD-8DRP2-27GG4 (Win8Core) 8N2M2-HWPGY-7PGT9-HGDD8-GVGGY (Win8CoreN) NG4HW-VH26C-733KW-K6F98-J8CK4 (Win8Pro) XCVCF-2NXM9-723PB-MHCB7-2RYQQ (Win8ProN) GNBB8-YVD74-QJHX6-27H4K-8QHDG (Win8ProWMC) I have added a sample command, but you have to uncomment it and change the Xs to the gVLK of your desired OS. If you are using a usb drive simply copy the $oem$ folder and paste into \sources\ If you are using a DVD, you need to load the desired source dvd in a program like ultra-iso or power-iso. Navigate into the sources folder in the iso program. Drag the $oem$ folder from windows explorer to the iso program's sources contents. You should be able to then burn the image to dvd. If the boot sector is not preserved, (sometimes the case with large dvds) you need to get oscdimg.exe by downloading the Windows ADK. You don't need to download the WinPE stuff, just the default tools. Open admin command prompt and run the following command on an extracted windows source with the $oem$ pre-copied: oscdimg -bc:\windvd\boot\etfsboot.com -u2 -h -m c:\windvd\ c:\windvd.iso For UEFI it is a bit different. Windows 7 doesn't come with a uefi boot sector by default, but windows 8 does. You can get the efisys.bin in the ADK, and change the command around for win7. In windows 8 the oscdimg command for a UEFI disc, assuming win8 directory, would be: oscdimg -bc:\Win8\efi\microsoft\boot\efisys.bin -pEF -m -u2 -udfver102 -bootdata:2#p0,e,bc:\win8\boot\etfsboot.com#pEF,e,bc:\Win8\efi\microsoft\boot\efisys.bin C:\Win8\ FinishedWin8.iso :::Known issues::: You shouldn't use 127.0.0.1 if testing on a VM because VMs use 127.0.0.1 typically for their Network address translations. You can use anything from 127.0.0.2 to 127.255.255.254 :::Advanced usage::: You should not try to do a reg load / unload and pre-integrate this. The SC commands or Import/Reboot methods are the only two methods that will not crash your system during setup. You can copy everything inside $oem$\$$\ to your mounted image's Windows directory. This does the same thing as letting windows copy it by using the $oem$ structure, but might be required for using a distrubution share. I'm not familiar with distrubution shares, so use your own judgement. :::Permission::: You DO have my permission to re-upload this. You do NOT have my permission to make any money using this. This includes counterfeit dvds or other scams. You do NOT have my permission to turn this into an activator. There are quite enough KMS activation methods in MS toolkit. The only reason I made this $oem$ is because there is currently no commandline installers for the KSS in 2.4.3. Cody was less than enthusiastic about doing the work required to make a commandline installer for KSS when we already know ...
iLLEGAL_FTP