├── .gitattributes ├── .wiki ├── images │ ├── pp3.png │ ├── ppg1.png │ ├── ppg2.png │ ├── ppg4.png │ ├── gpo-01.png │ ├── hyperv-passth-01.png │ ├── hyperv-passth-02.png │ ├── hyperv-passth-03.png │ ├── hyperv-passth-04.png │ └── hyperv-passth-05.png ├── GPO Checker.md ├── Home.md ├── PortProxyGUI.md ├── Hyper-V Device Passthrough.md ├── Port Scanner.md └── VLMCSD & License Manager.md ├── .editorconfig ├── .github ├── pull_request_template.md ├── workflows │ ├── auto-assign.yml │ └── codeql.yml ├── dependabot.yml └── ISSUE_TEMPLATE │ ├── feature_request.md │ └── bug_report.md ├── .gitignore ├── .gitmodules ├── LICENSE ├── SECURITY.md ├── CONTRIBUTING.md ├── README.md ├── CODE_OF_CONDUCT.md ├── vlmcsd-repos ├── README.md └── ListProductKeys.md └── Global.sln /.gitattributes: -------------------------------------------------------------------------------- 1 | * eol=lf 2 | -------------------------------------------------------------------------------- /.wiki/images/pp3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/TheFlightSims/windowsserver-mgmttools/HEAD/.wiki/images/pp3.png -------------------------------------------------------------------------------- /.wiki/images/ppg1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/TheFlightSims/windowsserver-mgmttools/HEAD/.wiki/images/ppg1.png -------------------------------------------------------------------------------- /.wiki/images/ppg2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/TheFlightSims/windowsserver-mgmttools/HEAD/.wiki/images/ppg2.png -------------------------------------------------------------------------------- /.wiki/images/ppg4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/TheFlightSims/windowsserver-mgmttools/HEAD/.wiki/images/ppg4.png -------------------------------------------------------------------------------- /.wiki/images/gpo-01.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/TheFlightSims/windowsserver-mgmttools/HEAD/.wiki/images/gpo-01.png -------------------------------------------------------------------------------- /.wiki/images/hyperv-passth-01.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/TheFlightSims/windowsserver-mgmttools/HEAD/.wiki/images/hyperv-passth-01.png -------------------------------------------------------------------------------- /.wiki/images/hyperv-passth-02.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/TheFlightSims/windowsserver-mgmttools/HEAD/.wiki/images/hyperv-passth-02.png -------------------------------------------------------------------------------- /.wiki/images/hyperv-passth-03.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/TheFlightSims/windowsserver-mgmttools/HEAD/.wiki/images/hyperv-passth-03.png -------------------------------------------------------------------------------- /.wiki/images/hyperv-passth-04.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/TheFlightSims/windowsserver-mgmttools/HEAD/.wiki/images/hyperv-passth-04.png -------------------------------------------------------------------------------- /.wiki/images/hyperv-passth-05.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/TheFlightSims/windowsserver-mgmttools/HEAD/.wiki/images/hyperv-passth-05.png -------------------------------------------------------------------------------- /.editorconfig: -------------------------------------------------------------------------------- 1 | [*.cs] 2 | 3 | # CS1591: Missing XML comment for publicly visible type or member 4 | dotnet_diagnostic.CS1591.severity = silent 5 | -------------------------------------------------------------------------------- /.github/pull_request_template.md: -------------------------------------------------------------------------------- 1 | Contributors (included all co-authors): 2 | 3 | Time/Day (HH:MM MM/DD/YYYY): 4 | 5 | Pull request note: 6 | 7 | What's new, what's changed?: 8 | 9 | -------------------------------------------------------------------------------- /.github/workflows/auto-assign.yml: -------------------------------------------------------------------------------- 1 | name: Auto Assign 2 | on: 3 | issues: 4 | types: [opened] 5 | pull_request: 6 | types: [opened] 7 | jobs: 8 | run: 9 | runs-on: ubuntu-latest 10 | permissions: 11 | issues: write 12 | pull-requests: write 13 | steps: 14 | - name: 'Auto-assign issue' 15 | uses: pozil/auto-assign-issue@v1 16 | with: 17 | repo-token: ${{ secrets.GITHUB_TOKEN }} 18 | assignees: shiroinekotfs 19 | numOfAssignee: 1 20 | -------------------------------------------------------------------------------- /.github/dependabot.yml: -------------------------------------------------------------------------------- 1 | # To get started with Dependabot version updates, you'll need to specify which 2 | # package ecosystems to update and where the package manifests are located. 3 | # Please see the documentation for all configuration options: 4 | # https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates 5 | 6 | version: 2 7 | updates: 8 | - package-ecosystem: "pip,docker,nuget" # See documentation for possible values 9 | directory: "/" # Location of package manifests 10 | schedule: 11 | interval: "weekly" 12 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | /.vs 2 | *.vs 3 | /!bin! 4 | *.suo 5 | *.cache 6 | *.exe 7 | *.compressed 8 | *.pdb 9 | *.CopyComplete 10 | *.dll 11 | *.pfx 12 | 13 | gpo-checker/.vs 14 | gpo-checker/obj 15 | 16 | hyperv-passthrough/.vs 17 | hyperv-passthrough/obj 18 | 19 | port-scanner/.vs 20 | port-scanner/obj 21 | 22 | vlmcsd-beta/license-manager/.vs 23 | vlmcsd-beta/license-manager/obj 24 | 25 | vlmcsd-beta/vlmcsd/buildroot-configs 26 | vlmcsd-beta/vlmcsd/hotbird64-mass-build 27 | vlmcsd-beta/vlmcsd/src/GNUmakefile 28 | vlmcsd-beta/vlmcsd/VisualStudio 29 | vlmcsd-beta/vlmcsd-floppy/vlmcsd-floppy-content/mkinitrd.guide 30 | 31 | vlmcsd-beta/vlmcsd/bin/vlmcs 32 | vlmcsd-beta/vlmcsd/bin/vlmcsd 33 | 34 | *.o -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea for this project 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Is your feature request related to a problem? Please describe.** 11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] 12 | 13 | **Describe the solution you'd like** 14 | A clear and concise description of what you want to happen. 15 | 16 | **Describe alternatives you've considered** 17 | A clear and concise description of any alternative solutions or features you've considered. 18 | 19 | **Additional context** 20 | Add any other context or screenshots about the feature request here. 21 | -------------------------------------------------------------------------------- /.gitmodules: -------------------------------------------------------------------------------- 1 | [submodule "hyperv-passthrough"] 2 | path = hyperv-passthrough 3 | url = https://github.com/tfslabs/hyperv-passthrough.git 4 | [submodule "port-scanner"] 5 | path = port-scanner 6 | url = https://github.com/tfslabs/port-scanner.git 7 | [submodule "PortProxyGUI"] 8 | path = PortProxyGUI 9 | url = https://github.com/tfslabs/PortProxyGUI.git 10 | [submodule "license-manager"] 11 | path = vlmcsd-repos/license-manager 12 | url = https://github.com/tfslabs/license-manager.git 13 | [submodule "vlmcsd-db"] 14 | path = vlmcsd-repos/vlmcsd-db 15 | url = https://github.com/tfslabs/vlmcsd-db.git 16 | [submodule "vlmcsd-quick-deployments"] 17 | path = vlmcsd-repos/vlmcsd-quick-deployments 18 | url = https://github.com/tfslabs/vlmcsd-quick-deployments.git 19 | [submodule "vlmcsd"] 20 | path = vlmcsd-repos/vlmcsd 21 | url = https://github.com/tfslabs/vlmcsd.git 22 | -------------------------------------------------------------------------------- /.wiki/GPO Checker.md: -------------------------------------------------------------------------------- 1 | # GPO Checker 2 | 3 | GPO Checker is a vulnerabilities scanner, to check the misconfigurations in the Group Policies within the Active Directory domain. 4 | 5 | ## Contributors 6 | 7 | | Contributor | Description | 8 | |--|--| 9 | | [@georgeatgrayson](https://github.com/georgeatgrayson) | Original developers of GPO Checker | 10 | | [@TheFlightSimsOfficial](https://github.com/TheFlightSimsOfficial) | Contributor | 11 | | [@shiroinekotfs](https://github.com/shiroinekotfs) | Contributor | 12 | 13 | ## Use GPO Checker 14 | 15 | > Note: Always run GPO Checker with Administrator privilege 16 | 17 | ![Alt text](images/gpo-01.png) 18 | 19 | Once it's running, click `Go` then wait for a minute for the GPO Checker scan all policies. 20 | 21 | > If you're not running the application on the computer not joined into a domain, nor the domain cannot be contacted, GPO Checker won't check the policies, and return the error. 22 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a report to help us improve 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Describe the bug** 11 | A clear and concise description of what the bug is. 12 | 13 | **To Reproduce** 14 | Steps to reproduce the behavior: 15 | 1. Go to '...' 16 | 2. Click on '....' 17 | 3. Scroll down to '....' 18 | 4. See error 19 | 20 | **Expected behavior** 21 | A clear and concise description of what you expected to happen. 22 | 23 | **Screenshots** 24 | If applicable, add screenshots to help explain your problem. 25 | 26 | **Desktop (please complete the following information):** 27 | - OS: [e.g. iOS] 28 | - Browser [e.g. chrome, safari] 29 | - Version [e.g. 22] 30 | 31 | **Smartphone (please complete the following information):** 32 | - Device: [e.g. iPhone6] 33 | - OS: [e.g. iOS8.1] 34 | - Browser [e.g. stock browser, safari] 35 | - Version [e.g. 22] 36 | 37 | **Additional context** 38 | Add any other context about the problem here. 39 | -------------------------------------------------------------------------------- /.wiki/Home.md: -------------------------------------------------------------------------------- 1 | ![Windows Server Management Tools - Banner](https://github.com/TheFlightSims/windowsserver-mgmttools/blob/master/banner.png?raw=true) 2 | 3 | ## Some introductions in this project 4 | 5 | Windows Server management tools are the collection of various projects by many developers. Mainly this repository only contains high-quality projects, then we move them under our support. 6 | 7 | ## What are tools supported by TheFlightSims? 8 | 9 | It depends on the way contributors react to our projects. Currently, this repo only supports these tools: 10 | 11 | * [GPO Checker](https://github.com/TheFlightSims/windowsserver-mgmttools/wiki/GPO-Checker) 12 | * [Hyper-V Device Passthrough](https://github.com/TheFlightSims/windowsserver-mgmttools/wiki/Hyper-V-Passthrough-Device) 13 | * [PortProxyGUI](https://github.com/TheFlightSims/windowsserver-mgmttools/wiki/PortProxyGUI) 14 | * [Port Scanner](https://github.com/TheFlightSims/windowsserver-mgmttools/wiki/Port-Scanner) 15 | * [VLMCSD & License Manager](https://github.com/TheFlightSims/windowsserver-mgmttools/wiki/VLMCSD-&-License-Manager) 16 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2023 TheFlightSims 4 | 5 | Linked with embedded TFS-OSSH license. 6 | 7 | View the license more at https://github.com/TheFlightSims/.github/blob/main/guides/oss/Licenses%2C%20Credits%20and%20Attributions.md 8 | 9 | Permission is hereby granted, free of charge, to any person obtaining a copy 10 | of this software and associated documentation files (the "Software"), to deal 11 | in the Software without restriction, including without limitation the rights 12 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 13 | copies of the Software, and to permit persons to whom the Software is 14 | furnished to do so, subject to the following conditions: 15 | 16 | The above copyright notice and this permission notice shall be included in all 17 | copies or substantial portions of the Software. 18 | 19 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 20 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 21 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 22 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 23 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 24 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 25 | SOFTWARE. 26 | -------------------------------------------------------------------------------- /.wiki/PortProxyGUI.md: -------------------------------------------------------------------------------- 1 | # PortProxyGUI 2 | 3 | PortProxyGUI is a port export and proxy director for Windows and Windows Server, especially for forwarding applications and between web servers within the network, or LDAP. 4 | 5 | ## Contributors 6 | 7 | | Contributor | Description | 8 | | -- | -- | 9 | | @[zmjack](https://github.com/zmjack) | Original developer of PortProxyGUI | 10 | | @[shiroinekotfs](https://github.com/shiroinekotfs) | Contributor | 11 | 12 | ## Use PortProxyGUI 13 | 14 | > Note: Please always run this software with Administrator privilege 15 | 16 | ### Getting started 17 | 18 | ![alt text](images/ppg1.png) 19 | 20 | Once you're in, you will see the main interface as shown above. Right-click to display and configure your proxy settings 21 | 22 | * Click "New (N)" to add a new rule, then you can set the Rule Name and listen on the IP address with its port and forwarding port. After that click "Set", the application will make the proxy between the requested port and the real application port. 23 | 24 | ![alt text](images/ppg2.png) 25 | 26 | * Disabling or Enabling a rule will stop or start the corresponding port forwarding process on your computer. 27 | 28 | ![alt text](images/pp3.png) 29 | 30 | Backing up and Restoring rules are performed by exporting and importing `.db` files, which contain all the information about the connection and port forwarding. 31 | 32 | ![alt text](images/ppg4.png) 33 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | # Security 2 | 3 | TheFlightSims takes the security responsibilities of our software products and services seriously, including all open-source software and closed-source software 4 | 5 | ## Reporting Security Issues 6 | 7 | **Note:** You shouldn't report the security vulnerabilities on the Issue or the public place. Any attackers can use these vulnerabilities to exploit non-public data - which causes security vulnerability. 8 | 9 | You can report security issues on these platforms: 10 | 11 | * The repository security page (Preferred) 12 | * [Email](mailto:welcome.tfs@outlook.com) 13 | 14 | Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue: 15 | 16 | * Type of issue (e.g., buffer overflow, SQL injection, cross-site scripting) 17 | * Full paths of the source file(s) related to the manifestation of the issue 18 | * The location of the affected source code (tag/branch/commit or direct URL) 19 | * Any special configuration required to reproduce the issue 20 | * Step-by-step instructions to reproduce the issue 21 | * Proof-of-concept or exploit code (if possible) 22 | * Impact of the case, including how an attacker might control the issue 23 | 24 | This information will help us triage your report more quickly. 25 | 26 | ## Preferred Languages 27 | 28 | You can use all human-valid languages. However, you may consider using English (US) to prevent misunderstanding. 29 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing & Feedback 2 | 3 | ## Contributing to the source 4 | 5 | Windows Server Management Tools repo uses Git submodules. It can reduce the load of non-essential projects you don't want to load. That means you can clone each repo of a part of a submodule, instead of cloning the whole project repo. 6 | 7 | To contribute, you may need [Visual Studio 2022](https://visualstudio.microsoft.com/vs/). Required Visual Studio 2022 SDKs: 8 | 9 | 1. .NET 4.8 SDK and targeting pack 10 | 2. C++ Windows XP Support for VS 2017 (v141) Tools 11 | 3. Windows 10 SDK (10.0.18362.0) 12 | 4. Windows Universal C Runtime 13 | 14 | ### GitHub Desktop 15 | 16 | In GitHub Desktop, consider using `Clone Repository\URL`, then enter this URL of git repo 17 | 18 | ```url 19 | https://github.com/TheFlightSims/windowsserver-mgmttools.git 20 | ``` 21 | 22 | All submodules will be updated automatically. You don't need to use Git CLI. 23 | 24 | ### Git CLI 25 | 26 | To clone this project using the Git command line, you need to clone all its base and submodules, following these commands: 27 | 28 | ```bash 29 | git clone https://github.com/TheFlightSims/windowsserver-mgmttools.git 30 | cd windowsserver-mgmttools # Make sure the repo is cloned successfully 31 | git submodule update --init --recursive 32 | ``` 33 | 34 | ## Other ways to contribute & feedback 35 | 36 | Otherwise, you can do other ways: 37 | 38 | * [Review Wiki Page](https://github.com/TheFlightSims/windowsserver-mgmttools/wiki) 39 | * Submit bugs and feature requests in [GitHub](https://github.com/TheFlightSims/windowsserver-mgmttools/issues) 40 | * [Review source codes](https://github.com/TheFlightSims/windowsserver-mgmttools) 41 | * [Review and commit pull requests](https://github.com/TheFlightSims/windowsserver-mgmttools/pulls) 42 | -------------------------------------------------------------------------------- /.wiki/Hyper-V Device Passthrough.md: -------------------------------------------------------------------------------- 1 | # Hyper-V Device Passthrough 2 | 3 | Hyper-V Device Passthrough allows Hyper-V virtual machines can use hardware directly, without using software bridge. 4 | 5 | ## Contributors 6 | 7 | | Contributor | Description | 8 | |--|--| 9 | | [@chanket](https://github.com/chanket) | Original developers of GPO Checker | 10 | | [@TheFlightSimsOfficial](https://github.com/TheFlightSimsOfficial) | Contributor | 11 | | [@shiroinekotfs](https://github.com/shiroinekotfs) | Contributor | 12 | 13 | ## Use Hyper-V Device Passthrough 14 | 15 | > Note: Please always run this software with Administrator privilege 16 | 17 | ### Getting started 18 | 19 | ![Picture 01](images/hyperv-passth-01.png) 20 | 21 | Once you run the Hyper-V Device Passthrough application, the app will appear with pre-created virtual machines, with its name and state. 22 | 23 | In each virtual machine, the row below shows all mounted devices, its type and address. 24 | 25 | ### Mount a device 26 | 27 | > Note: Make sure your selected virtual machine state is `Off`. If not, shut down this virtual machine. Also, the target device must be in idle state to prevent BSOD while passing. 28 | 29 | Right-click on the selected machine, then select `Add device`. A windows will appear to let you select your device 30 | 31 | ![Picture 02](images/hyperv-passth-02.png) 32 | 33 | > You can try to search for a device name, or device type using `Find by string` 34 | 35 | Select your target, click add, confirm, and you're done! 36 | 37 | ![Alt text](images/hyperv-passth-03.png) 38 | 39 | > Note: For GPU, the process requires accepting the risk of mounting your GPU into (DDA procedure). Read the instruction carefully. 40 | 41 | ### Unmount a device 42 | 43 | If you've mounted a device into a virtual machine, and you want to unmount/delete that device, right-click the select device, then click `Remove device` 44 | 45 | > Note: Make sure your selected virtual machine state is `Off`. If not, shut down this virtual machine. Also, the target device must be in idle state to prevent BSOD while passing. 46 | 47 | ![Alt text](images/hyperv-passth-04.png) 48 | 49 | ### (Advanced) Set High-space memory 50 | 51 | In DDA procedure, it's required that the high-space memory must be configured properly. 52 | 53 | ![Alt text](images/hyperv-passth-05.png) 54 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ![Windows Server Management Tools Banner](https://repository-images.githubusercontent.com/589945469/63740ef9-7624-4fbf-b1f6-6b7bd4905361) 2 | 3 | ![GitHub Downloads (all assets, all releases)](https://img.shields.io/github/downloads/TheFlightSims/windowsserver-mgmttools/total) 4 | ![Docker Tracker](https://img.shields.io/docker/pulls/theflightsims/vlmcsd) 5 | ![GitHub language count](https://img.shields.io/github/languages/count/TheFlightSims/windowsserver-mgmttools) 6 | ![GitHub repo size](https://img.shields.io/github/repo-size/TheFlightSims/windowsserver-mgmttools) 7 | ![GitHub Repo stars](https://img.shields.io/github/stars/TheFlightSims/windowsserver-mgmttools) 8 | 9 | # The Repository 10 | 11 | ***This repository presents to you a collection of server management tools for various purposes:*** 12 | 13 | * *Proxy port from another computer into target computer* 14 | * *Passthrough physical device into the virtual machine* 15 | * *Activation services for the server* 16 | * *Scanning open ports on the target* 17 | 18 | For better understanding, you can see the [wiki page](https://github.com/TheFlightSims/windowsserver-mgmttools/wiki). 19 | 20 | ## Use and install 21 | 22 | ***To run and use applications in this project, make sure your computer is installed with the features:*** 23 | 24 | * .NET 4.8 (built-in with modern Windows Server). These are built-in features and can be enabled. You can see the document [here](https://learn.microsoft.com/en-us/dotnet/framework/install/dotnet-35-windows) 25 | * Visual C++ 2015 and all versions later. You can download it [here](https://learn.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist?view=msvc-170) 26 | 27 | ## Contributing & Feedback 28 | 29 | For contributing guidelines, see [CONTRIBUTING.md](CONTRIBUTING.md) 30 | 31 | ### Feedback 32 | 33 | To feedback on this repository, go to [**feedback**](https://github.com/TheFlightSims/windowsserver-mgmttools/issues) 34 | 35 | ## License & Original Contributors 36 | 37 | ### License 38 | 39 | This repo uses [**MIT License**](https://opensource.org/licenses/MIT) for all contributors to have free, no limit to 40 | 41 | * Use (for both private and commercial uses) 42 | * Modify (including editing the source files) 43 | * Distribution without permission directly from TheFlightSims, except emergency revokes permission. In that case, this repo will be moved to private and cannot be accessed by the public. 44 | -------------------------------------------------------------------------------- /.wiki/Port Scanner.md: -------------------------------------------------------------------------------- 1 | # Port Scanner 2 | 3 | PortScanner is used to scan any opening ports of the target computer. 4 | 5 | ## Contributors 6 | 7 | | Contributor | Description | 8 | |--|--| 9 | | [@IceMoonHSV](https://github.com/IceMoonHSV) | Original developers of Port Scanner | 10 | | [@TheFlightSimsOfficial](https://github.com/TheFlightSimsOfficial) | Contributor | 11 | | [@shiroinekotfs](https://github.com/shiroinekotfs) | Contributor | 12 | 13 | ## Use Port Scanner 14 | 15 | Try to run `PortScanner.exe` and you'll get this help screen. 16 | 17 | ```bash 18 | PortScanner is a part of Windows Server Management Tools 19 | Currently maintained by TheFlightSims 20 | 21 | See more at: https://github.com/TheFlightSims/windowsserver-mgmttools 22 | 23 | PortScanner.exe {hosts} {ports} [timeout] [outfile] 24 | 25 | DESCRIPTION: 26 | PortScanner is used to scan any opening ports of the target computer 27 | The commands are depend on how you use, but general mapping are still 28 | can be seen above. 29 | 30 | GENERAL COMMANDS: 31 | hosts - Target computers. Can use FQDN or IP. Seperate by comma 32 | 33 | ports - Ports that needs to be scanned. Seperate by comma. 34 | You can use defined ports. See below for more info. 35 | Port range is not supported in this version 36 | 37 | timeout - Maximum scanning time per port. Useful when scanning on 38 | large number of ports 39 | 40 | outfile - Export results to a file. R/W is required on the target 41 | directory 42 | 43 | DEFINED PORTS: 44 | 45 | Defined ports are the ports containing specific roles, providing specific 46 | features on computer. The list below shows all defined ports on PortScanner 47 | 48 | admin - 135, 139, 445, 3389, 5985, 5986, 8000, 8080. 49 | 50 | web - 21, 23, 25, 80, 443, 8080. 51 | 52 | top20 - 21, 22, 23, 25, 53, 80, 110, 111, 135, 139, 53 | 143, 443, 445, 993, 995, 1723, 3306, 3389, 54 | 5900, 8080. 55 | 56 | server-common - 7, 9, 13, 17, 19, 25, 42, 80, 88, 110, 111, 57 | 119, 135, 149, 389, 443, 445, 465, 563, 587, 58 | 636, 808, 993, 995, 1433, 1688, 1801, 3268, 59 | 3269, 3387, 3388, 3389, 4044, 6516, 6881, 60 | 8000, 8080, 8800, 8391, 8443, 8530, 8531, 61 | 9389 62 | 63 | all-ports - All ports in range 1, 65535 64 | 65 | SAMPLES: 66 | PortScanner.exe hosts=127.0.0.1,google.com ports=21,22,23 timeout=5000 outfile=C:\scans.txt 67 | PortScanner.exe hosts=localhost ports=admin 68 | ``` 69 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Community Guidelines 2 | 3 | At TheFlightSims, we recognize and celebrate the creativity and collaboration of open 4 | source contributors and the diversity of skills, experiences, cultures, and 5 | opinions they bring to the projects and communities they participate in. 6 | 7 | Everyone of the communities are inclusive environments, based on treating 8 | all individuals respectfully, regardless of 9 | gender identity and expression, sexual orientation, disabilities, 10 | neurodiversity, physical appearance, body size, ethnicity, nationality, race, 11 | age, religion, or similar personal characteristic. 12 | 13 | We value diverse opinions, but we value respectful behavior more. 14 | 15 | Respectful behavior includes: 16 | 17 | * Being considerate, kind, constructive, and helpful. 18 | * Not engaging in demeaning, discriminatory, harassing, hateful, sexualized, or 19 | physically threatening behavior, speech, and imagery. 20 | * Not engaging in unwanted physical contact. 21 | 22 | Some TheFlightSims open source projects may adopt an explicit project code of 23 | conduct, which may have additional detailed expectations for participants. Most 24 | of those projects will use our modified Contributor Covenant. 25 | 26 | ## Resolve peacefully 27 | 28 | We do not believe that all conflict is necessarily bad; healthy debate and 29 | disagreement often yields positive results. However, it is never okay to be 30 | disrespectful. 31 | 32 | If you see someone behaving disrespectfully, you are encouraged to address the 33 | behavior directly with those involved. Many issues can be resolved quickly and 34 | easily, and this gives people more control over the outcome of their dispute. 35 | If you are unable to resolve the matter for any reason, or if the behavior is 36 | threatening or harassing, report it. We are dedicated to providing an 37 | environment where participants feel welcome and safe. 38 | 39 | ## Reporting problems 40 | 41 | Some TheFlightSims open source projects may adopt a project-specific code of conduct. 42 | In those cases, a TheFlightSims employee will be identified as the Project Steward, 43 | who will receive and handle reports of code of conduct violations. In the event 44 | that a project hasn’t identified a Project Steward, you can report problems by 45 | emailing to welcome.tfs@outlook.com. 46 | 47 | We will investigate every complaint, but you may not receive a direct response. 48 | We will use our discretion in determining when and how to follow up on reported 49 | incidents, which may range from not taking action to permanent expulsion from 50 | the project and project-sponsored spaces. We will notify the accused of the 51 | report and provide them an opportunity to discuss it before any action is 52 | taken. The identity of the reporter will be omitted from the details of the 53 | report supplied to the accused. In potentially harmful situations, such as 54 | ongoing harassment or threats to anyone's safety, we may take action without 55 | notice. 56 | -------------------------------------------------------------------------------- /vlmcsd-repos/README.md: -------------------------------------------------------------------------------- 1 | # VLMCSD & License Manager 2 | 3 | ![Docker Tracker](https://img.shields.io/docker/pulls/theflightsims/vlmcsd) 4 | 5 | ***VLMCSD*** is a free, open-source software to provide an activation service (KMS) for any computer using Office and Windows products 6 | 7 | ***License Manager*** is a free, open-source software to manage licenses of local or remote computers 8 | 9 | **For detailed information (written by the original developers), see [here](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/vlmcsd/man)** 10 | 11 | ## Original Contributors 12 | 13 | | Contributor | Description | 14 | |--|--| 15 | | [Linus Torvalds](https://github.com/torvalds) | Original developer of Linux kernel, used in VLMCSD on Floppy | 16 | | Hotbird64 | Original developer of VLMCSD, License Manager, VLMCSD on Floppy, VLMCSD on WSL | 17 | | Erik Andersen | Original developer of VLMCSD | 18 | | Waldemar Brodkorb | Original developer of VLMCSD | 19 | | Denys Vlasenko | Original developer of VLMCSD | 20 | | H. Peter Anvin | Original developer of VLMCSD | 21 | | [Wind4](https://github.com/Wind4/vlmcsd) | Contributor of VLMCSD | 22 | | [kkkgo](https://github.com/kkkgo) | Contributor of VLMCSD, VLMCSD on Floppy | 23 | | [HarukaMa](https://github.com/HarukaMa) | Contributor of VLMCSD, VLMCSD on Floppy | 24 | | Nang | Contributor of VLMCSD database 25 | | [shiroineko](https://github.com/shiroinekotfs) | Contributor of VLMCSD, License Manager, VLMCSD on Floppy, VLMCSD on WSL, VLMCSD Database | 26 | 27 | ## The Files and Folders 28 | 29 | | Folder Name | Description | 30 | |--|--| 31 | | [database-config](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/database-config) | Database for `vlmcsd`, License Manager, and MSSQL 2022. It also contains `getkey.py` and Microsoft SQL Server 2022 key management notebook | 32 | | [license-manager](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/license-manager) | License Manager source folder | 33 | | [vlmcsd-docker](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/vlmcsd-docker) | Binary file for Docker container | 34 | | [vlmcsd-floppy](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/vlmcsd-floppy) | `vlmcsd` floppy disk | 35 | | [vlmcsd-wsl](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/vlmcsd-wsl) | `vlmcsd` WSL distro | 36 | | [vlmcsd](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/vlmcsd) | `vlmcsd` source code | 37 | 38 | ## Build and Run 39 | 40 | Check out this wiki to build VLMCSD, License Manager, vlmcsd on floppy, and vlmcsd on WSL. 41 | 42 | ## List of activation keys 43 | Click to see the list of [product keys](https://github.com/TheFlightSims/windowsserver-mgmttools/blob/master/vlmcsd-beta/database-config/tables/Product%20Keys.csv) and the [list of keys available](https://github.com/TheFlightSims/windowsserver-mgmttools/blob/master/vlmcsd-beta/database-config/tables/Total%20Keys.csv). Note that each product can only see 5 public keys. 44 | 45 | To see the complete list of product keys, you can check out the Wiki to learn how to import and list from SQL Database. 46 | -------------------------------------------------------------------------------- /.github/workflows/codeql.yml: -------------------------------------------------------------------------------- 1 | # For most projects, this workflow file will not need changing; you simply need 2 | # to commit it to your repository. 3 | # 4 | # You may wish to alter this file to override the set of languages analyzed, 5 | # or to provide custom queries or build logic. 6 | # 7 | # ******** NOTE ******** 8 | # We have attempted to detect the languages in your repository. Please check 9 | # the `language` matrix defined below to confirm you have the correct set of 10 | # supported CodeQL languages. 11 | # 12 | name: "CodeQL" 13 | 14 | on: 15 | push: 16 | branches: [ "master" ] 17 | pull_request: 18 | branches: [ "master" ] 19 | schedule: 20 | - cron: '17 15 * * 6' 21 | 22 | jobs: 23 | analyze: 24 | name: Analyze 25 | # Runner size impacts CodeQL analysis time. To learn more, please see: 26 | # - https://gh.io/recommended-hardware-resources-for-running-codeql 27 | # - https://gh.io/supported-runners-and-hardware-resources 28 | # - https://gh.io/using-larger-runners 29 | # Consider using larger runners for possible analysis time improvements. 30 | runs-on: ${{ (matrix.language == 'swift' && 'macos-latest') || 'ubuntu-latest' }} 31 | timeout-minutes: ${{ (matrix.language == 'swift' && 120) || 360 }} 32 | permissions: 33 | actions: read 34 | contents: read 35 | security-events: write 36 | 37 | strategy: 38 | fail-fast: false 39 | matrix: 40 | language: [ 'c-cpp', 'csharp' ] 41 | # CodeQL supports [ 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'swift' ] 42 | # Use only 'java-kotlin' to analyze code written in Java, Kotlin or both 43 | # Use only 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both 44 | # Learn more about CodeQL language support at https://aka.ms/codeql-docs/language-support 45 | 46 | steps: 47 | - name: Checkout repository 48 | uses: actions/checkout@v4 49 | 50 | # Initializes the CodeQL tools for scanning. 51 | - name: Initialize CodeQL 52 | uses: github/codeql-action/init@v3 53 | with: 54 | languages: ${{ matrix.language }} 55 | # If you wish to specify custom queries, you can do so here or in a config file. 56 | # By default, queries listed here will override any specified in a config file. 57 | # Prefix the list here with "+" to use these queries and those in the config file. 58 | 59 | # For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs 60 | # queries: security-extended,security-and-quality 61 | 62 | 63 | # Autobuild attempts to build any compiled languages (C/C++, C#, Go, Java, or Swift). 64 | # If this step fails, then you should remove it and run the build manually (see below) 65 | - name: Autobuild 66 | uses: github/codeql-action/autobuild@v3 67 | 68 | # ℹ️ Command-line programs to run using the OS shell. 69 | # 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun 70 | 71 | # If the Autobuild fails above, remove it and uncomment the following three lines. 72 | # modify them (or add more) to build your code if your project, please refer to the EXAMPLE below for guidance. 73 | 74 | # - run: | 75 | # echo "Run, Build Application using script" 76 | # ./location_of_script_within_repo/buildscript.sh 77 | 78 | - name: Perform CodeQL Analysis 79 | uses: github/codeql-action/analyze@v3 80 | with: 81 | category: "/language:${{matrix.language}}" 82 | -------------------------------------------------------------------------------- /Global.sln: -------------------------------------------------------------------------------- 1 | 2 | Microsoft Visual Studio Solution File, Format Version 12.00 3 | # Visual Studio Version 17 4 | VisualStudioVersion = 17.11.35312.102 5 | MinimumVisualStudioVersion = 10.0.40219.1 6 | Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "VLMCSD", "VLMCSD", "{38E806B8-F14E-45E3-AC77-5F6B39B56778}" 7 | EndProject 8 | Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Hyper-V Passthrough Tool", "hyperv-passthrough\Hyper-V Passthrough Tool.csproj", "{F2A2FC53-F5E9-4350-8D9B-98269DF4C9B1}" 9 | EndProject 10 | Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "Port Proxy GUI", "PortProxyGUI\Port Proxy GUI.csproj", "{F8C3B324-87BA-4DCB-B0D5-A28356094A9C}" 11 | EndProject 12 | Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Port Scanner", "port-scanner\Port Scanner.csproj", "{B124BC1F-CCFB-49F0-B082-F13644F66069}" 13 | EndProject 14 | Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "License Manager", "vlmcsd-repos\license-manager\License Manager.csproj", "{C147A441-64DE-4773-948C-105CC3BBCA07}" 15 | EndProject 16 | Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "libkms-Windows", "vlmcsd-repos\vlmcsd\VisualStudio\libkms\libkms.vcxproj", "{2A0FC04D-C3C0-43E2-8812-53AE901C5395}" 17 | EndProject 18 | Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "vlmcs-Windows", "vlmcsd-repos\vlmcsd\VisualStudio\vlmcs\vlmcs.vcxproj", "{2B3F305D-6351-4F4A-A7F2-1F9B1988CDEE}" 19 | EndProject 20 | Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "vlmcsd-Windows", "vlmcsd-repos\vlmcsd\VisualStudio\vlmcsd\vlmcsd.vcxproj", "{918B4F5B-6356-451E-998C-5FCB29988170}" 21 | EndProject 22 | Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "vlmcsdmulti-Windows", "vlmcsd-repos\vlmcsd\VisualStudio\vlmcsdmulti\vlmcsdmulti.vcxproj", "{7F07671D-1432-43E9-9D72-08435F216B5E}" 23 | EndProject 24 | Global 25 | GlobalSection(SolutionConfigurationPlatforms) = preSolution 26 | Debug|x64 = Debug|x64 27 | Debug|x86 = Debug|x86 28 | Release|x64 = Release|x64 29 | Release|x86 = Release|x86 30 | EndGlobalSection 31 | GlobalSection(ProjectConfigurationPlatforms) = postSolution 32 | {F2A2FC53-F5E9-4350-8D9B-98269DF4C9B1}.Debug|x64.ActiveCfg = Debug|x64 33 | {F2A2FC53-F5E9-4350-8D9B-98269DF4C9B1}.Debug|x64.Build.0 = Debug|x64 34 | {F2A2FC53-F5E9-4350-8D9B-98269DF4C9B1}.Debug|x86.ActiveCfg = Debug|x86 35 | {F2A2FC53-F5E9-4350-8D9B-98269DF4C9B1}.Debug|x86.Build.0 = Debug|x86 36 | {F2A2FC53-F5E9-4350-8D9B-98269DF4C9B1}.Release|x64.ActiveCfg = Release|x64 37 | {F2A2FC53-F5E9-4350-8D9B-98269DF4C9B1}.Release|x64.Build.0 = Release|x64 38 | {F2A2FC53-F5E9-4350-8D9B-98269DF4C9B1}.Release|x86.ActiveCfg = Release|x86 39 | {F2A2FC53-F5E9-4350-8D9B-98269DF4C9B1}.Release|x86.Build.0 = Release|x86 40 | {F8C3B324-87BA-4DCB-B0D5-A28356094A9C}.Debug|x64.ActiveCfg = Debug|x64 41 | {F8C3B324-87BA-4DCB-B0D5-A28356094A9C}.Debug|x64.Build.0 = Debug|x64 42 | {F8C3B324-87BA-4DCB-B0D5-A28356094A9C}.Debug|x86.ActiveCfg = Debug|x86 43 | {F8C3B324-87BA-4DCB-B0D5-A28356094A9C}.Debug|x86.Build.0 = Debug|x86 44 | {F8C3B324-87BA-4DCB-B0D5-A28356094A9C}.Release|x64.ActiveCfg = Release|x64 45 | {F8C3B324-87BA-4DCB-B0D5-A28356094A9C}.Release|x64.Build.0 = Release|x64 46 | {F8C3B324-87BA-4DCB-B0D5-A28356094A9C}.Release|x86.ActiveCfg = Release|x86 47 | {F8C3B324-87BA-4DCB-B0D5-A28356094A9C}.Release|x86.Build.0 = Release|x86 48 | {B124BC1F-CCFB-49F0-B082-F13644F66069}.Debug|x64.ActiveCfg = Debug|x64 49 | {B124BC1F-CCFB-49F0-B082-F13644F66069}.Debug|x64.Build.0 = Debug|x64 50 | {B124BC1F-CCFB-49F0-B082-F13644F66069}.Debug|x86.ActiveCfg = Debug|x86 51 | {B124BC1F-CCFB-49F0-B082-F13644F66069}.Debug|x86.Build.0 = Debug|x86 52 | {B124BC1F-CCFB-49F0-B082-F13644F66069}.Release|x64.ActiveCfg = Release|x64 53 | {B124BC1F-CCFB-49F0-B082-F13644F66069}.Release|x64.Build.0 = Release|x64 54 | {B124BC1F-CCFB-49F0-B082-F13644F66069}.Release|x86.ActiveCfg = Release|x86 55 | {B124BC1F-CCFB-49F0-B082-F13644F66069}.Release|x86.Build.0 = Release|x86 56 | {C147A441-64DE-4773-948C-105CC3BBCA07}.Debug|x64.ActiveCfg = Debug|x64 57 | {C147A441-64DE-4773-948C-105CC3BBCA07}.Debug|x64.Build.0 = Debug|x64 58 | {C147A441-64DE-4773-948C-105CC3BBCA07}.Debug|x86.ActiveCfg = Debug|x86 59 | {C147A441-64DE-4773-948C-105CC3BBCA07}.Debug|x86.Build.0 = Debug|x86 60 | {C147A441-64DE-4773-948C-105CC3BBCA07}.Release|x64.ActiveCfg = Release|x64 61 | {C147A441-64DE-4773-948C-105CC3BBCA07}.Release|x64.Build.0 = Release|x64 62 | {C147A441-64DE-4773-948C-105CC3BBCA07}.Release|x86.ActiveCfg = Release|x86 63 | {C147A441-64DE-4773-948C-105CC3BBCA07}.Release|x86.Build.0 = Release|x86 64 | {2A0FC04D-C3C0-43E2-8812-53AE901C5395}.Debug|x64.ActiveCfg = Debug|x64 65 | {2A0FC04D-C3C0-43E2-8812-53AE901C5395}.Debug|x64.Build.0 = Debug|x64 66 | {2A0FC04D-C3C0-43E2-8812-53AE901C5395}.Debug|x86.ActiveCfg = Debug|Win32 67 | {2A0FC04D-C3C0-43E2-8812-53AE901C5395}.Debug|x86.Build.0 = Debug|Win32 68 | {2A0FC04D-C3C0-43E2-8812-53AE901C5395}.Release|x64.ActiveCfg = Release|x64 69 | {2A0FC04D-C3C0-43E2-8812-53AE901C5395}.Release|x64.Build.0 = Release|x64 70 | {2A0FC04D-C3C0-43E2-8812-53AE901C5395}.Release|x86.ActiveCfg = Release|Win32 71 | {2A0FC04D-C3C0-43E2-8812-53AE901C5395}.Release|x86.Build.0 = Release|Win32 72 | {2B3F305D-6351-4F4A-A7F2-1F9B1988CDEE}.Debug|x64.ActiveCfg = Debug|x64 73 | {2B3F305D-6351-4F4A-A7F2-1F9B1988CDEE}.Debug|x64.Build.0 = Debug|x64 74 | {2B3F305D-6351-4F4A-A7F2-1F9B1988CDEE}.Debug|x86.ActiveCfg = Debug|Win32 75 | {2B3F305D-6351-4F4A-A7F2-1F9B1988CDEE}.Debug|x86.Build.0 = Debug|Win32 76 | {2B3F305D-6351-4F4A-A7F2-1F9B1988CDEE}.Release|x64.ActiveCfg = Release|x64 77 | {2B3F305D-6351-4F4A-A7F2-1F9B1988CDEE}.Release|x64.Build.0 = Release|x64 78 | {2B3F305D-6351-4F4A-A7F2-1F9B1988CDEE}.Release|x86.ActiveCfg = Release|Win32 79 | {2B3F305D-6351-4F4A-A7F2-1F9B1988CDEE}.Release|x86.Build.0 = Release|Win32 80 | {918B4F5B-6356-451E-998C-5FCB29988170}.Debug|x64.ActiveCfg = Debug|x64 81 | {918B4F5B-6356-451E-998C-5FCB29988170}.Debug|x64.Build.0 = Debug|x64 82 | {918B4F5B-6356-451E-998C-5FCB29988170}.Debug|x86.ActiveCfg = Debug|Win32 83 | {918B4F5B-6356-451E-998C-5FCB29988170}.Debug|x86.Build.0 = Debug|Win32 84 | {918B4F5B-6356-451E-998C-5FCB29988170}.Release|x64.ActiveCfg = Release|x64 85 | {918B4F5B-6356-451E-998C-5FCB29988170}.Release|x64.Build.0 = Release|x64 86 | {918B4F5B-6356-451E-998C-5FCB29988170}.Release|x86.ActiveCfg = Release|Win32 87 | {918B4F5B-6356-451E-998C-5FCB29988170}.Release|x86.Build.0 = Release|Win32 88 | {7F07671D-1432-43E9-9D72-08435F216B5E}.Debug|x64.ActiveCfg = Debug|x64 89 | {7F07671D-1432-43E9-9D72-08435F216B5E}.Debug|x64.Build.0 = Debug|x64 90 | {7F07671D-1432-43E9-9D72-08435F216B5E}.Debug|x86.ActiveCfg = Debug|Win32 91 | {7F07671D-1432-43E9-9D72-08435F216B5E}.Debug|x86.Build.0 = Debug|Win32 92 | {7F07671D-1432-43E9-9D72-08435F216B5E}.Release|x64.ActiveCfg = Release|x64 93 | {7F07671D-1432-43E9-9D72-08435F216B5E}.Release|x64.Build.0 = Release|x64 94 | {7F07671D-1432-43E9-9D72-08435F216B5E}.Release|x86.ActiveCfg = Release|Win32 95 | {7F07671D-1432-43E9-9D72-08435F216B5E}.Release|x86.Build.0 = Release|Win32 96 | EndGlobalSection 97 | GlobalSection(SolutionProperties) = preSolution 98 | HideSolutionNode = FALSE 99 | EndGlobalSection 100 | GlobalSection(NestedProjects) = preSolution 101 | {2A0FC04D-C3C0-43E2-8812-53AE901C5395} = {38E806B8-F14E-45E3-AC77-5F6B39B56778} 102 | {2B3F305D-6351-4F4A-A7F2-1F9B1988CDEE} = {38E806B8-F14E-45E3-AC77-5F6B39B56778} 103 | {918B4F5B-6356-451E-998C-5FCB29988170} = {38E806B8-F14E-45E3-AC77-5F6B39B56778} 104 | {7F07671D-1432-43E9-9D72-08435F216B5E} = {38E806B8-F14E-45E3-AC77-5F6B39B56778} 105 | EndGlobalSection 106 | GlobalSection(ExtensibilityGlobals) = postSolution 107 | SolutionGuid = {CEE8A90F-FC19-4D00-8D55-E35A74C3A237} 108 | EndGlobalSection 109 | EndGlobal 110 | -------------------------------------------------------------------------------- /vlmcsd-repos/ListProductKeys.md: -------------------------------------------------------------------------------- 1 | ## Valid Microsoft applications that can be acitvated using vlmcsd 2 | 3 | To see all vaild product keys for Windows and Office, see [here](https://github.com/TheFlightSimulationsOfficial/windowsserver-mgmttools/blob/master/vlmcsd-beta/db/getkeysonline/table/Keys.csv), and the list of vaild keys, check [there](https://github.com/TheFlightSimulationsOfficial/windowsserver-mgmttools/blob/master/vlmcsd-beta/db/getkeysonline/table/List%20Vaild%20Keys.csv) 4 | 5 | ### OR 6 | 7 | You may use these product names or numbers(vlmcs -x): 8 | 9 | ### Windows Server (2008 - 2022) 10 | 11 | Product 12 | :-| 13 | Windows Server 2008 Web 14 | Windows Server 2008 Compute Cluster 15 | Windows Server 2008 Standard 16 | Windows Server 2008 Standard without Hyper-V 17 | Windows Server 2008 Enterprise 18 | Windows Server 2008 Enterprise without Hyper-V 19 | Windows Server 2008 Datacenter 20 | Windows Server 2008 Datacenter without Hyper-V 21 | Windows Server 2008 for Itanium 22 | Windows MultiPoint Server 2010 23 | Windows Server 2008 R2 Web 24 | Windows Server 2008 R2 HPC Edition 25 | Windows Server 2008 R2 Standard 26 | Windows Server 2008 R2 Enterprise 27 | Windows Server 2008 R2 Datacenter 28 | Windows Server 2008 R2 for Itanium Enterprise 29 | Windows Server 2012 Datacenter 30 | Windows Server 2012 MultiPoint Premium 31 | Windows Server 2012 MultiPoint Standard 32 | Windows Server 2012 Standard 33 | Windows Server 2012 R2 Cloud Storage 34 | Windows Server 2012 R2 Datacenter 35 | Windows Server 2012 R2 Essentials 36 | Windows Server 2012 R2 Standard 37 | Windows Server 2016 Azure Core 38 | Windows Server 2016 Cloud Storage 39 | Windows Server 2016 Datacenter 40 | Windows Server 2016 Essentials 41 | Windows Server 2016 Standard 42 | Windows Server 2016 ARM64 43 | Windows Server 2016 Datacenter (Semi-Annual Channel) 44 | Windows Server 2016 Standard (Semi-Annual Channel) 45 | Windows Server 2016 Datacenter Preview 46 | Windows Server 2019 ARM64 47 | Windows Server 2019 Azure Core 48 | Windows Server 2019 Datacenter 49 | Windows Server 2019 Essentials 50 | Windows Server 2019 Standard 51 | Windows Server 2019 Datacenter (Semi-Annual Channel) 52 | Windows Server 2019 Standard (Semi-Annual Channel) 53 | Windows Server 2021 Datacenter (Semi-Annual Channel) 54 | Windows Server 2021 Standard (Semi-Annual Channel) 55 | Windows Server 2022 Azure Core 56 | Windows Server 2022 Datacenter 57 | Windows Server 2022 Standard 58 | 59 | ### Windows Client (6.0 - 10.0.22500) 60 | 61 | Product 62 | :-| 63 | Windows 10/11 Enterprise LTSC 2019 64 | Windows 10/11 Enterprise LTSC 2019 N 65 | Windows 10/11 Enterprise G 66 | Windows 10/11 Enterprise GN 67 | Windows 10/11 Enterprise 2016 LTSB 68 | Windows 10/11 Enterprise 2016 LTSB N 69 | Windows 10/11 Home 70 | Windows 10/11 Home Country Specific 71 | Windows 10/11 Home N 72 | Windows 10/11 Home Single Language 73 | Windows 10/11 Education 74 | Windows 10/11 Education N 75 | Windows 10/11 Enterprise 76 | Windows 10/11 Enterprise 2015 LTSB 77 | Windows 10/11 Enterprise 2015 LTSB N 78 | Windows 10/11 Enterprise N 79 | Windows 10/11 Professional Workstation 80 | Windows 10/11 Professional Workstation N 81 | Windows 10/11 Professional 82 | Windows 10/11 Professional Education 83 | Windows 10/11 Professional Education N 84 | Windows 10/11 Professional N 85 | Windows 10/11 Professional Preview 86 | Windows 10/11 Enterprise Preview 87 | Windows 10/11 Enterprise for Virtual Desktops 88 | Windows 10/11 Remote Server 89 | Windows 10/11 S (Lean) 90 | Windows 10/11 Enterprise Preview 91 | Windows 10/11 Professional Preview 92 | Windows 10/11 Professional WMC Preview 93 | Windows 7 Enterprise 94 | Windows 7 Enterprise E 95 | Windows 7 Enterprise N 96 | Windows 7 Professional 97 | Windows 7 Professional E 98 | Windows 7 Professional N 99 | Windows 7 Embedded POSReady 100 | Windows 7 Embedded Standard 101 | Windows 7 ThinPC 102 | Windows 8 Core 103 | Windows 8 Core Country Specific 104 | Windows 8 Core N 105 | Windows 8 Core Single Language 106 | Windows 8 Professional WMC 107 | Windows 8 Embedded Industry Professional 108 | Windows 8 Embedded Industry Enterprise 109 | Windows 8 Enterprise 110 | Windows 8 Enterprise N 111 | Windows 8 Professional 112 | Windows 8 Professional N 113 | Windows 8.1 Core 114 | Windows 8.1 Core ARM 115 | Windows 8.1 Core Country Specific 116 | Windows 8.1 Core N 117 | Windows 8.1 Core Single Language 118 | Windows 8.1 Professional Student 119 | Windows 8.1 Professional Student N 120 | Windows 8.1 Professional WMC 121 | Windows 8.1 Core Connected 122 | Windows 8.1 Core Connected Country Specific 123 | Windows 8.1 Core Connected N 124 | Windows 8.1 Core Connected Single Language 125 | Windows 8.1 Enterprise 126 | Windows 8.1 Enterprise N 127 | Windows 8.1 Professional 128 | Windows 8.1 Professional N 129 | Windows 8.1 Embedded Industry Professional 130 | Windows 8.1 Embedded Industry Automotive 131 | Windows 8.1 Embedded Industry Enterprise 132 | Windows 8.x Preview 133 | Windows 8.x Preview ARM 134 | Windows Vista Business 135 | Windows Vista Business N 136 | Windows Vista Enterprise 137 | Windows Vista Enterprise N 138 | 139 | ### Office (2010 - 2021) 140 | 141 | Product 142 | :-| 143 | Office Access 2010 144 | Office Excel 2010 145 | Office Groove 2010 146 | Office InfoPath 2010 147 | Office Mondo 2010 148 | Office Mondo 2 2010 149 | Office OneNote 2010 150 | Office OutLook 2010 151 | Office PowerPoint 2010 152 | Office Professional Plus 2010 153 | Office Project Pro 2010 154 | Office Project Standard 2010 155 | Office Publisher 2010 156 | Office Small Business Basics 2010 157 | Office Standard 2010 158 | Office Visio Premium 2010 159 | Office Visio Pro 2010 160 | Office Visio Standard 2010 161 | Office Word 2010 162 | Office Access 2013 163 | Office Excel 2013 164 | Office InfoPath 2013 165 | Office Lync 2013 166 | Office Mondo 2013 167 | Office OneNote 2013 168 | Office OutLook 2013 169 | Office PowerPoint 2013 170 | Office Professional Plus 2013 171 | Office Project Pro 2013 172 | Office Project Standard 2013 173 | Office Publisher 2013 174 | Office Standard 2013 175 | Office Visio Pro 2013 176 | Office Visio Standard 2013 177 | Office Word 2013 178 | Office Access 2013 (Pre-Release) 179 | Office Excel 2013 (Pre-Release) 180 | Office Groove 2013 (Pre-Release) 181 | Office InfoPath 2013 (Pre-Release) 182 | Office Lync 2013 (Pre-Release) 183 | Office Mondo 2013 (Pre-Release) 184 | Office OneNote 2013 (Pre-Release) 185 | Office Outlook 2013 (Pre-Release) 186 | Office PowerPoint 2013 (Pre-Release) 187 | Office Professional Plus 2013 (Pre-Release) 188 | Office Project Pro 2013 (Pre-Release) 189 | Office Project Standard 2013 (Pre-Release) 190 | Office Publisher 2013 (Pre-Release) 191 | Office Visio Pro 2013 (Pre-Release) 192 | Office Visio Standard 2013 (Pre-Release) 193 | Office Word 2013 (Pre-Release) 194 | Office Access 2016 195 | Office Excel 2016 196 | Office Mondo 2016 197 | Office Mondo R 2016 198 | Office OneNote 2016 199 | Office Outlook 2016 200 | Office Powerpoint 2016 201 | Office Professional Plus 2016 202 | Office Project Pro 2016 203 | Office Project Pro 2016 C2R 204 | Office Project Standard 2016 205 | Office Project Standard 2016 C2R 206 | Office Publisher 2016 207 | Office Skype for Business 2016 208 | Office Standard 2016 209 | Office Visio Pro 2016 210 | Office Visio Pro 2016 C2R 211 | Office Visio Standard 2016 212 | Office Visio Standard 2016 C2R 213 | Office Word 2016 214 | Office Professional Plus 2019 C2R Preview 215 | Office Project Pro 2019 C2R Preview 216 | Office Visio Pro 2019 C2R Preview 217 | Office Access 2019 218 | Office Excel 2019 219 | Office Outlook 2019 220 | Office Powerpoint 2019 221 | Office Professional Plus 2019 222 | Office Project Pro 2019 223 | Office Project Standard 2019 224 | Office Publisher 2019 225 | Office Skype for Business 2019 226 | Office Standard 2019 227 | Office Visio Pro 2019 228 | Office Visio Standard 2019 229 | Office Word 2019 230 | Office Access LTSC 2021 231 | Office Excel LTSC 2021 232 | Office LTSC Professional Plus 2021 233 | Office LTSC Standard 2021 234 | Office Outlook LTSC 2021 235 | Office Powerpoint LTSC 2021 236 | Office Project Pro 2021 237 | Office Project Standard 2021 238 | Office Publisher LTSC 2021 239 | Office Skype for Business LTSC 2021 240 | Office Visio LTSC Pro 2021 241 | Office Visio LTSC Standard 2021 242 | Office Word LTSC 2021 243 | -------------------------------------------------------------------------------- /.wiki/VLMCSD & License Manager.md: -------------------------------------------------------------------------------- 1 | # VLMCSD & License Manager 2 | 3 | ![GitHub Downloads (all assets, all releases)](https://img.shields.io/github/downloads/TheFlightSims/windowsserver-mgmttools/total) 4 | ![Docker Tracker](https://img.shields.io/docker/pulls/theflightsims/vlmcsd) 5 | ![GitHub language count](https://img.shields.io/github/languages/count/TheFlightSims/windowsserver-mgmttools) 6 | ![GitHub repo size](https://img.shields.io/github/repo-size/TheFlightSims/windowsserver-mgmttools) 7 | ![GitHub Repo stars](https://img.shields.io/github/stars/TheFlightSims/windowsserver-mgmttools) 8 | 9 | ***VLMCSD*** is a free, open-source software to provide an activation service (KMS) for any computer using Office and Windows products 10 | 11 | ***License Manager*** is a free, open-source software to manage licenses of local or remote computers 12 | 13 | **For detailed information (written by the original developers), see [here](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/vlmcsd/man)** 14 | 15 | ## Original Contributors 16 | 17 | | Contributor | Description | 18 | |--|--| 19 | | [Linus Torvalds](https://github.com/torvalds) | Original developer of Linux kernel, used in VLMCSD on Floppy | 20 | | Hotbird64 | Original developer of VLMCSD, License Manager, VLMCSD on Floppy, VLMCSD on WSL | 21 | | Erik Andersen | Original developer of VLMCSD | 22 | | Waldemar Brodkorb | Original developer of VLMCSD | 23 | | Denys Vlasenko | Original developer of VLMCSD | 24 | | H. Peter Anvin | Original developer of VLMCSD | 25 | | [Wind4](https://github.com/Wind4/vlmcsd) | Contributor of VLMCSD | 26 | | [kkkgo](https://github.com/kkkgo) | Contributor of VLMCSD, VLMCSD on Floppy | 27 | | [HarukaMa](https://github.com/HarukaMa) | Contributor of VLMCSD, VLMCSD on Floppy | 28 | | Nang | Contributor of VLMCSD database 29 | | [shiroinekotfs](https://github.com/shiroinekotfs) | Contributor of VLMCSD, License Manager, VLMCSD on Floppy, VLMCSD on WSL, VLMCSD Database | 30 | 31 | ## The Files and Folders 32 | 33 | | Folder Name | Description | 34 | |--|--| 35 | | [database-config](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/database-config) | Database for `vlmcsd`, License Manager, and MSSQL 2022. It also contains `getkey.py` and Microsoft SQL Server 2022 key management notebook | 36 | | [license-manager](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/license-manager) | License Manager source folder | 37 | | [vlmcsd-floppy](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/vlmcsd-floppy) | `vlmcsd` on floppy disk | 38 | | [vlmcsd-wsl](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/vlmcsd-wsl) | `vlmcsd` for Windows Subsystem for Linux | 39 | | [vlmcsd](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/vlmcsd) | `vlmcsd` base source code | 40 | 41 | ## Use VLMCSD & License Manager 42 | 43 | ### Use the VLMCSD command line 44 | 45 | | VLMCSD App | Description | Command line | 46 | | -- | -- | -- | 47 | | `vlmcs` | `vlmcs` is a program that can be used to test a KMS server that provides activation for Microsoft products. It supports KMS 4, KMS 5, and KMS 6 protocol. | [See the document](https://github.com/TheFlightSims/windowsserver-mgmttools/blob/master/vlmcsd-beta/vlmcsd/man/vlmcs.1.unix.txt) 48 | | `vlmcsd` | `vlmcsd` is a fully Microsoft-compatible KMS server that provides product activation services to clients. It is a drop-in replacement for a Microsoft KMS server. It supports KMS 4, KMS 5, and KMS 6 protocol. | [See the document](https://github.com/TheFlightSims/windowsserver-mgmttools/blob/master/vlmcsd-beta/vlmcsd/man/vlmcsd.8.unix.txt) | 49 | | `vlmcsdmulti` | `vlmcsdmulti` is a multi-call binary that contains `vlmcs` and `vlmcsd` in a single binary. Since both programs share much code and data, the combined binary is significantly smaller than the sum of both files. | [See the document](https://github.com/TheFlightSims/windowsserver-mgmttools/blob/master/vlmcsd-beta/vlmcsd/man/vlmcsdmulti.1.dos.txt) 50 | 51 | ### Use VLMCSD on Docker 52 | 53 | On a system having too many applications running, using `docker` is the better way to deploy, maintain, and retire `vlmcsd` 54 | 55 | Containerized `vlmcsd` for both Linux and Windows are available on [Docker Hub](https://hub.docker.com/r/theflightsims/vlmcsd). By default, the container will expose port 1688. 56 | 57 | * For Windows Server editions, these images are available for Windows Server 2016 and up. You can try to run these images by using these following command lines 58 | 59 | ```cmd 60 | :: Windows Server 2016 container 61 | docker run -p 1688:1688 theflightsims/vlmcsd:ltsc2016-amd64 62 | 63 | :: Windows Server 2019 container 64 | docker run -p 1688:1688 theflightsims/vlmcsd:ltsc2019-amd64 65 | 66 | :: Windows Server 2022 container 67 | docker run -p 1688:1688 theflightsims/vlmcsd:ltsc2022-amd64 68 | ``` 69 | 70 | * For Linux, containerized images are available for **supporting architectures**. You can try these available architectures by using following command lines 71 | 72 | ```bash 73 | # AMD64 74 | docker run -p 1688:1688 theflightsims/vlmcsd:linux-amd64 75 | 76 | # ARM64 77 | docker run -p 1688:1688 theflightsims/vlmcsd:linux-arm64 78 | 79 | # S390X 80 | docker run -p 1688:1688 theflightsims/vlmcsd:linux-s390x 81 | 82 | # PPC64LE 83 | docker run -p 1688:1688 theflightsims/vlmcsd:linux-ppc64le 84 | 85 | # RISCv64 86 | docker run -p 1688:1688 theflightsims/vlmcsd:linux-riscv64 87 | 88 | # MIPS64LE 89 | docker run -p 1688:1688 theflightsims/vlmcsd:linux-mips64le 90 | ``` 91 | 92 | ### Use the VLMCSD on Floppy 93 | 94 | Typically, VLMCSD can be installed and running as an activation service, but in some cases, VLMCSD on Floppy provides a light-weight activation service for the lab to test; or provide an internal activation for the host (the error `0x8007000D` prevents Windows from activating locally) 95 | 96 | > Note: 97 | > 98 | > * When creating a VM on Hyper-V that uses VLMCSD floppy, make sure that you choose Generation 1 because of the incompatible with the Hyper-V Generation 2. 99 | > * When creating a VM on VMWare or Virtual Box, you must configure your boot OS as Linux (x86) to sync the VM BIOS with the OS 100 | 101 | #### 1. Disk-less System 102 | 103 | The VLMCSD on Floppy is a disk-less system that works entirely on RAM. The file system is a RAM disk created from the `initrd` file on the floppy image. That means anything you have made from inside the virtual machine will be lost when you reboot the machine. 104 | 105 | #### 2. System startup 106 | 107 | The kernel boots up while the init script (`/sbin/init`) waits 5 seconds. While this, you can: 108 | 109 | ```text 110 | Press m to enter IPv4 & timezone configuration 111 | Press t to start configure timezone configuration only 112 | Press s to enter pre—vlmcsd—service shell. 113 | ``` 114 | 115 | You can skip waiting for 5 seconds by pressing any other key. You also will see the IP addresses and a table containing user names and passwords. 116 | 117 | #### 3. Logging into the system 118 | 119 | 5 local login shells are provided on `/dev/tty2` to `/dev/tty6`. To switch between the logins, you can press `ALT` and `F2` to `F6`, or return to the service logs by pressing `ALT-F1`. This allows users can use multiple terminals at once. 120 | 121 | The floppy image only provides basic Unix commands—type busybox or /bin to get a list. The only editor available is `vi`. If you don't like `vi`, you may transfer config files via FTP to edit them with the editor of your choice and transfer them back. 122 | 123 | #### 4. The menu system 124 | 125 | You may need some just-in-time commands by pressing `ALT-F8`. 126 | 127 | ```text 128 | 1. Restart vlmcsd service 129 | 2. Stop vlmcsd service 130 | 3. Restart network service (includes telnet and ftp) 131 | 4. Stop network service (includes telnet and ftp) 132 | 5. Change the timezone 133 | 6. Show all kernel boot parameters 134 | 7. Show boot log 135 | 8. Show TCP/IP configuration 136 | 9. Show running processes 137 | 138 | k. Change keyboard layout 139 | 140 | s. Shutdown the computer 141 | r. Reboot the computer 142 | ``` 143 | 144 | ### Use the VLMCSD on WSL 145 | 146 | VLMCSD on WSL is recommended for multi-system on Windows. To see how WSL works, see [here](https://aka.ms/wsl) 147 | 148 | > You can use VLMCSD on WSL as you do on Floppy. However, the changes you have made on the WSL distro are permanent. 149 | 150 | To use VLMCSD on WSL, import it into the WSL database. To do this, change your active directory on the terminal to the folder [(project path)/vlmcsd-beta/wsl](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/vlmcsd-wsl) 151 | 152 | ```cmd 153 | wsl --import vlmcsd.tar 154 | ``` 155 | 156 | ### Use the License Manager 157 | 158 | > This guide only applies to License Manager, version 5.5.0, built and released by TheFlightSims. If you use your own copy of License Manager, or repack by others, the guide may differ. 159 | 160 | #### 1. The User Interface 161 | 162 | ![image](https://user-images.githubusercontent.com/99700363/225807709-d048e0cd-db62-497d-85e5-d3f8c8ada8e3.png) 163 | 164 | `(1)` License Manager tools (stores in tabs and quick access tools) 165 | 166 | `(2)` Connection credential and selected edition 167 | 168 | `(3)` Verbose license information 169 | 170 | `(4)` Verbose machine information 171 | 172 | `(5)` Progress bar 173 | 174 | #### 2. Install a Generic Key for the local computer 175 | 176 | ![image](https://user-images.githubusercontent.com/99700363/225810410-8003e36e-cb60-4c90-8e87-bce2586c53d3.png) 177 | 178 | Click on **Install a Generic Key**, and select the key that you want to install. You can copy-n-paste the key, or click **Check** and then click **Install** on the Product Finder window. 179 | 180 | > For Microsoft Visual Studio, Microsoft SQL Server, and Microsoft SCCM, you need to copy-n-paste in the product key box. License Manager cannot install these keys on your machine 181 | 182 | #### 3. Activate your Windows or Office using KMS Server 183 | 184 | > To activate using KMS Server, your destination computer needs a Generic Volume License Key (GVLK) installed. See [this document](https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys) to know how. Normally, the product keys stores in the License Manager that you can install are public GVLKs, so you will not need to find it on the Internet! 185 | 186 | ![image](https://user-images.githubusercontent.com/99700363/225835744-c7ae792e-adaa-4bb7-86b8-3e63a1b22183.png) 187 | 188 | You will need to determine which server responds to your request by entering the field Override KMS Host data with the IP Address or DNS Name, or you just need to determine the KMS Domain. Don't forget to save the settings! 189 | 190 | > Pro tip: if you use the Server edition, License Manager can verify whether the server can respond with your product activation in "Start a KMS Client" 191 | > 192 | >![image](https://user-images.githubusercontent.com/99700363/225837594-879e4761-0129-4dd4-af4f-75b0d81e4e4b.png) 193 | 194 | #### 4. Install or verify a product key 195 | 196 | ![image](https://user-images.githubusercontent.com/99700363/225839967-4452368e-b911-486e-9b85-8fc890be052a.png) 197 | 198 | You can just simply click on Product Finder and paste your product key: you will see your product key details, including its EPID and Complete PID. 199 | 200 | You can choose to Install it or Check the availability online. 201 | 202 | > Note that you can only verify Microsoft Office, Microsoft Windows, and Microsoft Visual Studio. However, Microsoft Visual Studio cannot be installed - you must enter the product key manually. 203 | 204 | #### 5. Export to Database 205 | 206 | You can export to these specific files in License Manager: 207 | |Export format| File extension | Description | 208 | |--|--|--| 209 | | VLMCSD | `.kmd` | This format used by vlmcsd, as the external (add-on) database | 210 | | py-kms classic | `.txt` | This format used by py-kms (KMS for Python 2) | 211 | | Generic C/C++/C# | `.txt`, `.c`, `.cpp`, `.h`, `.hpp`, `.cs` | This format helps developers to modify the vlmcsd source code | 212 | | License Manager database, py-kms | `.xml` | This format used by License Manager 213 | 214 | ## Build VLMCSD, License Manager & Edit Database 215 | 216 | ### Build VLMCSD on Visual Studio (recommended) 217 | 218 | * 1. Open **winser-mgmttools.sln**, then click on **vlmcsd.sln** and open with Visual Studio 219 | 220 | ![image](https://user-images.githubusercontent.com/99700363/225601211-38d78847-3421-40d5-8bbb-1e4ad0d793c3.png) 221 | 222 | > If the VS 2022 selection isn't in Open With, you can add VS2022 within the Add Program 223 | > 224 | > ![image](https://user-images.githubusercontent.com/99700363/225601991-c4a7b0a6-2fd2-4ce0-87cc-4ae7eeb091ca.png) 225 | 226 | * 2. After opening this, you can build VLMCSD 227 | 228 | ![image](https://user-images.githubusercontent.com/99700363/225604558-90a9c712-6d66-4c2f-aac8-671288741637.png) 229 | 230 | The Final build locates in the `!bin!` 231 | 232 | ### Build VLMCSD on Floppy 233 | 234 | You must know to edit the Floppy. 235 | 236 | > Note that the floppy does NOT contain `mkinitrd.guide` file. It helps our developers in rebuilding the initrd 237 | 238 | | File in floppy | Description | 239 | | -- | -- | 240 | |[bzImage](https://en.wikipedia.org/wiki/Vmlinux)| Linux kernel, version 3.12 241 | |[initrd](https://docs.kernel.org/admin-guide/initrd.html) | initial RAM disk, compressed as CPIO + LZMA 242 | | ldlinux.sys | Linux bootloader for floppy | 243 | | [syslinux.cfg](https://wiki.syslinux.org/wiki/index.php?title=Config) | Linux System Configuration | 244 | 245 | > Note: We sort by zero which means you have to follow these instructions in order, do it in order of sections. 246 | 247 | 1. Configure and rebuild initrd 248 | 249 | > To follow more straightforward, we use the default path [(project path)/vlmcsd-beta/vlmcsd-floppy/vlmcsd-floppy-content](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/vlmcsd-floppy/vlmcsd-floppy-content). You must configure your terminal to this path to this path to follow this guide easier 250 | 251 | * Configure initrd 252 | 253 | The list of files below helps you to determine each purpose of the files in initrd in floppy disk 254 | > In here, we use the Linux root path, which is extracted in the folder [(project path)/vlmcsd-beta/vlmcsd-floppy/vlmcsd-floppy-content/initrd](https://github.com/TheFlightSims/windowsserver-mgmttools/blob/master/vlmcsd-beta/vlmcsd-floppy/vlmcsd-floppy-content/initrd) 255 | 256 | * Rebuild the initrd by using these commands in WSL (recommend Debian or Ubuntu) or run them in Linux 257 | 258 | ```shell 259 | #You must configure your terminal to (project path)/vlmcsd-beta/floppy/vlmcsd-floppy-content 260 | rm initrd 261 | cd initrd-sources 262 | find . | cpio -o -H newc > ../initrd~ 263 | cd .. 264 | lzma initrd~ 265 | mv initrd~.lzma initrd 266 | ``` 267 | 268 | > You still can change the behavior of the compression model (e.g., compress with a smaller packet size), but you must know what you do. 269 | > To understand how to use WSL, you can see [here](https://aka.ms/wsl). Although WSL1 and WSL2 can do the same, we recommend WSL2 because more stable and secure for your device 270 | 271 | 2. Edit the virtual floppy disk 272 | 273 | You may need to use [OSFMount](https://www.osforensics.com/tools/mount-disk-images.html) to mount the formatted-FAT16-[floppy disk](https://github.com/TheFlightSims/windowsserver-mgmttools/blob/master/vlmcsd-beta/vlmcsd-floppy/vlmcsd-beta-floppy.vfd). 274 | 275 | After mounting the floppy disk, copy-n-paste the files you have already edited. 276 | 277 | ### Build License Manager 278 | 279 | * 1. Open **winser-mgmttools.sln**, then click on **LicenseManager.sln** and open with Visual Studio 280 | ![image](https://user-images.githubusercontent.com/99700363/225634845-54651f8d-62da-4de1-a146-292722d64643.png) 281 | 282 | > If the VS 2022 selection isn't in Open With, you can add VS2022 within the Add Program 283 | > 284 | > ![image](https://user-images.githubusercontent.com/99700363/225601991-c4a7b0a6-2fd2-4ce0-87cc-4ae7eeb091ca.png) 285 | 286 | * 2. After opening this, you can build License Manager 287 | 288 | ![image](https://user-images.githubusercontent.com/99700363/225635348-5dd4ad70-754b-4d56-97bf-387cf0ec9af4.png) 289 | 290 | ### Build & Manage Database 291 | 292 | * License Manager database 293 | 294 | Since the [PR #37](https://github.com/TheFlightSims/windowsserver-mgmttools/pull/37), we have merged external LMDB within the application. That means, you're no longer can use external database. 295 | 296 | * [VLMCSD database](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/database-config/vlmcsdb) 297 | 298 | VLMCSD Service configuration (or known as [vlmcsd.ini](https://github.com/TheFlightSims/windowsserver-mgmttools/blob/master/vlmcsd-beta/database-config/vlmcsdb/vlmcsd.ini)) is as vlmcsd service configuration. 299 | 300 | VLMCSD Database (or known as [vlmcsd.kmd](https://github.com/TheFlightSims/windowsserver-mgmttools/blob/master/vlmcsd-beta/database-config/vlmcsdb/vlmcsd.kmd)) is the binary, external `vlmcsd` database. You can configure it in [vlmcsd.ini](https://github.com/TheFlightSims/windowsserver-mgmttools/blob/master/vlmcsd-beta/database-config/vlmcsdb/vlmcsd.ini), or you can use on the command line interface. 301 | 302 | * [Product Key database on Microsoft SQL Server 2022](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/database-config/sql) 303 | 304 | To use the database, [restore](https://learn.microsoft.com/en-us/sql/relational-databases/backup-restore/quickstart-backup-restore-database?view=sql-server-ver16) the database from the file [`PDKDB.bak`](https://github.com/TheFlightSims/windowsserver-mgmttools/blob/master/vlmcsd-beta/database-config/mssql/PDKDB.bak) 305 | 306 | > The database is only readable on [Microsoft SQL Server 2022](https://www.microsoft.com/en-us/sql-server/sql-server-2022). Consider to upgrade your own SQL Server to use it. 307 | 308 | To manage the Product Key database, use the [Azure Data Studio](https://azure.microsoft.com/en-us/products/data-studio) to open [Product Key Notebook.ipynb](https://github.com/TheFlightSims/windowsserver-mgmttools/blob/master/vlmcsd-beta/database-config/mssql/Product%20Key%20Notebook.ipynb), and use it to connect and manage the Product Key database. 309 | 310 | * [Product Key tables](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/database-config/tables) are the `.csv` portable file that can open on Microsoft Excel, or WPS Excel. 311 | 312 | ## Activation Error Codes & Limitations 313 | 314 | ### Limitation 315 | 316 | Check the list of [product keys](https://github.com/TheFlightSims/windowsserver-mgmttools/tree/master/vlmcsd-beta/database-config/tables/Product%20Keys.csv) that VLMCSD can activate 317 | 318 | ### Error codes 319 | 320 | |Error code |Error message |Activation type| 321 | |-----------|--------------|----------------| 322 | |0x8007000D | The KMS host you are using cannot handle your product. It only supports legacy versions. | KMS client | 323 | |0x8004FE21|This computer is not running genuine Windows. |MAK/KMS client | 324 | |0x80070005 |Access denied. The requested action requires elevated privileges. |MAK/KMS client/KMS host | 325 | |0x8007007b| DNS name does not exist. |KMS client | 326 | |0x80070490|The product key you entered didn't work. Check the product key and try again, or enter a different one. |MAK | 327 | |0x800706BA |The RPC server is unavailable. |KMS client | 328 | |0x8007232A|DNS server failure. |KMS host | 329 | |0x8007232B|DNS name does not exist. |KMS client | 330 | |0x8007251D|No records found for DNS query. |KMS client | 331 | |0x80092328|DNS name does not exist. |KMS client | 332 | |0xC004B100 |The activation server determined that the computer could not be activated. |MAK | 333 | |0xC004C001|The activation server determined the specified product key is invalid |MAK| 334 | |0xC004C003 |The activation server determined the specified product key is blocked |MAK | 335 | |0xC004C008 |The activation server determined that the specified product key could not be used. |KMS | 336 | |0xC004C020|The activation server reported that the Multiple Activation Key has exceeded its limit. |MAK | 337 | |0xC004C021|The activation server reported that the Multiple Activation Key extension limit has been exceeded. |MAK | 338 | |0xC004F009 |The Software Protection Service reported that the grace period expired. |MAK | 339 | |0xC004F00F|The Software Licensing Server reported that the hardware ID binding is beyond level of tolerance. |MAK/KMS client/KMS host | 340 | |0xC004F014|The Software Protection Service reported that the product key is not available |MAK/KMS client | 341 | |0xC004F02C|The Software Protection Service reported that the format for the offline activation data is incorrect. |MAK/KMS client | 342 | |0xC004F035|The Software Protection Service reported that the computer could not be activated with a Volume license product key. |KMS client/KMS host | 343 | |0xC004F038 |The Software Protection 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. |KMS client | 344 | |0xC004F039|The Software Protection Service reported that the computer could not be activated. The Key Management Service (KMS) is not enabled. |KMS client | 345 | |0xC004F041|The Software Protection Service determined that the Key Management Server (KMS) is not activated. KMS needs to be activated. |KMS client | 346 | |0xC004F042 |The Software Protection Service determined that the specified Key Management Service (KMS) cannot be used. |KMS client | 347 | |0xC004F050|The Software Protection Service reported that the product key is invalid. |MAK/KMS/KMS client | 348 | |0xC004F051|The Software Protection Service reported that the product key is blocked. |MAK/KMS | 349 | |0xC004F064|The Software Protection Service reported that the non-genuine grace period expired. |MAK | 350 | |0xC004F065|The Software Protection Service reported that the application is running within the valid non-genuine period. |MAK/KMS client | 351 | |0xC004F06C|The Software Protection Service reported that the computer could not be activated. The Key Management Service (KMS) determined that the request timestamp is invalid. |KMS client | 352 | |0xC004F074|The Software Protection Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information. |KMS client | 353 | 354 | ## List of activation keys 355 | 356 | Click to see the list of [product keys](https://github.com/TheFlightSims/windowsserver-mgmttools/blob/master/vlmcsd-beta/database-config/tables/Product%20Keys.csv) and the [list of keys available](https://github.com/TheFlightSims/windowsserver-mgmttools/blob/master/vlmcsd-beta/database-config/tables/Product%20Keys.csv). Note that each product can only see 5 public keys. 357 | 358 | To see the complete list of product keys, you can check out the Wiki to learn how to import and list from SQL Database. 359 | --------------------------------------------------------------------------------