Download key generator for KMS Client Emulator v1.0 - For Increasing KMS Server Client Count

If you have ever used a KMS Server, whether a leaked online server or a Virtual Machine like KMSMicro, you know that you need so many clients to ask the KMS Server for activation before it gives them out.
If you try to activate against a KMS Server, and the client count is not at least the following:
25 for any Windows Client Operating System
5 for any Windows Server Operating System
5 for any Microsoft Office Application/Suite
You will get the following error if the client count is not at that minimum:
0xC004F038 The software Licensing Service reported that the computer could not be activated. The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator.
The problem with using a VM to create your own personal KMS Server is you need to achieve this count, and after 30 days, the count is lost, so you need to maintain the client count. So far people have been using a client Virtual Machine and scripts to boost the count, but this is a slow and hacky method and requires running 2 virtual machines.
So, based on source code nosferat87 made of a KMS Server Emulator, which ZWT made the original version but nosferati87 fixed bugs in, I created a KMS Client Emulator that can boost the supported products on ANY KMS Server. Anyone is welcome to use this in however way they want, but I will have this integrated into Microsoft Toolkit and AutoKMS, so you can use KMS Servers with those applications without setting up any kind of script based on this application, or ever worrying about the count.
The KMS Client Emulator is a tiny console commandline application that can boost any KMS Server client count. It sends an activation request like a real client, spoofing it and sending a unique Client Machine ID every time, so every request is acknowledged as unique. It is a tiny application that replaces the client VMs people have been using to boost the count, is much faster, and can be easily automated.
The KMS Client Emulator uses the following commandline parameters:
"KMS Client.exe" KMSPort KMSHost ClientMode
KMSPort is the TCP/IP Port, usually 1688, that the KMS Server listens on.
KMSHost is the IP or Hostname of the KMS Host.
ClientMode is the product you want to increase the KMS Count of.
Valid Parameters:
KMSPort can be DefaultPort or any number from 0 to 65535. It is usually 1688 which DefaultPort=1688
ClientMode can be Windows, Office2010, or Office2013. Windows will increase any Windows KMS Host count, Office2010 will boost Office 2010 KMS Host Count, and Office2013 will boost any Office 2013 KMS Host count. You cannot use Office2010 to boost Office 2013 KMS Host count or Office2013 to boost Office 2010 KMS Host count. If you leave this blank, it will default to Windows.
Examples of Use:
If you enter any invalid parameters, such as Port 99999, the app won't run, and will tell you the parameter was invalid. The KMS Host you specify must be online, and listening for KMS Requests on the given Port. Any network issues or Firewall issues, or the host not listening will cause the KMS Client to end with an error code, typically "Error 1722: The RPC Server is Unavailable". If you try to boost a client count of a product that the KMS Host doesn't support, such as trying to boost Office2013 on a KMS Server without an active Office 2013 KMS Host Key, you will get the error "Failed to get Activation response.".