MultiDeskKore — Requirements Matrix
Version 1.0 · 25 October 2026 · Applies to MultiDeskKore Solo — the Single Host edition (MultiDeskKore V1) on Windows 10 Pro 22H2
Editions: these manuals cover MultiDeskKore Solo — the Single Host edition (MultiDeskKore V1/RC1, available now). MultiDeskKore Fleet (Multi-Host, V2) and MultiDeskKore Station (Same Machine, local multiseat) are in development and are not covered here.
This matrix states exactly what MultiDeskKore Solo (Single Host, V1) needs, what it does not need, and what is optional. Nothing is listed here that was not part of the tested product. Where a capability is implemented but its live behaviour has not yet been proven in a test, the matrix says so.
Required
| # | Requirement | Notes |
|---|---|---|
| R1 | A properly licensed Windows 10 Pro host, version 22H2 | The tested configuration. The host's Windows licence is separate from the MultiDeskKore licence and is the customer's responsibility. Windows 11 has not been tested. |
| R2 | Administrator rights on the host | The installer must run as administrator, and console administration needs the console admin account. |
| R3 | A compatible Remote Desktop client per user | Windows Remote Desktop Connection (mstsc) or any compatible RDP client, on the user's own device. |
| R4 | A device + display + keyboard/mouse per user | Each seat is a real workstation position: one device, one screen, one keyboard and mouse. |
| R5 | A reliable network between the host and each user's device | Remote Desktop sessions run over the network. The console itself is local to the host and needs no internet. |
| R6 | Enough host resources for the sessions you plan to run | Capacity depends on workload and host resources. The console Host page shows live CPU and memory use. No fixed seat count per gigabyte is promised. |
| R7 | A MultiDeskKore licence key — or the 3-day trial | Install without a key, then start the 3-day trial from the console Licence page (Get trial key). After the trial, a key is required for new users. |
Not required
| # | Not required | Notes |
|---|---|---|
| N1 | No extra server hardware | The host PC is the server. |
| N2 | No domain / Active Directory | Users are local accounts created and managed from the console. |
| N3 | No proprietary thin-client hardware | Any device with a compatible RDP client works as a seat. |
| N4 | No separate virtual machines | Sessions run directly on the host; no per-user VM is created. |
| N5 | No monthly subscription | Licences are one-time purchases. The first 12 months of upgrades and standard support are included; renewal after that is optional. |
| N6 | No customer login or customer account | The customer uses only the local console. The buy page asks only for an email address; the owner portal is TrimKore-only. |
| N7 | No internet connection for local operation | Sessions, licence validation, an activated trial, and the console all work with the website unreachable. Only Buy, support tickets, host-transfer requests, and getting a trial key need the website. |
Optional
| # | Optional | Notes |
|---|---|---|
| O1 | Thin clients | A thin client with an RDP client is a supported seat device, but an ordinary PC works the same way. |
| O2 | Wired network | Recommended where the host and seats are fixed in one place; not a requirement. |
| O3 | A backup routine | Recommended for the host. MultiDeskKore data lives under %ProgramData%\MultiDeskKore\ and in HKLM\SOFTWARE\MultiDeskKore. |
What is proven, and what is not yet proven
The product was verified in the pilot VM on 25 October 2026 (verification checks 0–12 all passing, including 4 concurrent RDP sessions plus the console administrator active at the same time, and the same session reinstated on re-login). The following are implemented in V1 but their live behaviour has not yet been proven by a recorded test. They are listed here so nobody mistakes a console setting for a proven guarantee:
- RAM-limit enforcement — per-session limits are set from the console and applied by the service, but no recorded test has yet shown a session actually being held to its cap.
- Disk quotas — quotas are set from the console with read-back verification, but no recorded test has yet shown a write beyond a quota being refused.
- Application restrictions — denied/allowed apps are set from the console (AppLocker deny-list plus Start Menu hiding), but enforcement on Windows 10 Pro 22H2 has not yet been proven live.
- Clipboard / drive redirection controls — the toggles are set from the console, but no recorded test has yet shown redirection actually blocked in a session.
- Administrator roles (Operator / Viewer) — roles are enforced by the service, but no recorded test has yet shown a role denial (for example, a Viewer being refused a user-creation attempt).
- Audit coverage — the console Audit Log records user, session, licence, admin, wallpaper, ticket, and transfer operations, but no recorded test has yet confirmed an entry for each operation.
- Consent-based screen assistance (shadowing) — the console gives the exact shadow commands and the policy requires user permission, but shadowing against the installed session layer has not yet been proven live.
- USB redirection (Increment 2) — the host-wide switch is set
(
fDisablePNPRedirabsent or 0, verify check 31) and the console records each client's peripherals, but no recorded test has yet shown a dedicated USB device actually appearing and working in a session on Windows 10 Pro 22H2, or a shared printer printing from a different seat's session. - Per-user audio (Increment 2, live check Q9) — the host-wide audio switch is set and the per-client toggle is written into the seat user's hive, but whether Windows 10 Pro 22H2 honours the per-user hive value has not yet been proven live. Until the live test runs, the host-wide switch is the proven control.
- Support-ticket round-trip — tickets are created in the console and sent to TrimKore, but the live round-trip (send, reply in the portal, reply appearing in the console) has never run; the pilot VM has no internet.
- Folder-permission negative test — seat and shared-folder permissions are in place and the service log shows no permission failures, but no recorded test has yet shown one seat user being refused another seat user's folder. That negative test is still to run.
Compatibility — what is NOT claimed
- Windows 11 — not tested; no compatibility is claimed.
- Any specific number of seats per gigabyte of RAM — no such figure is promised. Seat capacity is governed by the licence (one seat is one user account on one licensed host); how many sessions the host can run at once is governed by the host's resources and the workload in each session.
- Unlimited capacity during the trial — the trial is fully functional within the host's resources; it does not imply unlimited practical capacity. During the trial at most 2 remote seat accounts can be created, plus the host admin.
MultiDeskKore V1 · by TrimKore · trimkore.com Tested configuration: Windows 10 Pro 22H2.
MultiDeskKore V1 · by TrimKore · trimkore.com · Tested configuration: Windows 10 Pro 22H2. The Markdown files in Docs/ are the canonical source for these pages.