One shared host.Separate user sessions.

Understand the setup before you start.

Applications run on the host. Users connect over the network with compatible Remote Desktop clients.

Guest device

MultiDeskKoreby TrimKore TK-HOST-01Local consoleAdmin

Sessions

One host. Every workspace.

Active sessions2

Memory used3.67 GB

Host statusOnline

Sessions (2) ↻ Refresh+ Add user

#	User	Status	Client
1	PilotAdmin	Active	—
2	Seat1	Active	BURAQDT

Illustrative preview.

Guest device

Host

Guest devices connect to the host over the network. Sessions share one host and are not separate virtual machines.

Check your setup

Confirm the host, applications and client devices are compatible.

Install and evaluate

Install on the host, create test users and evaluate your real workload.

Purchase and activate

Choose seats, complete payment verification and activate your licence.

What you need

Host computer	A supported and properly licensed Windows configuration.
Network	Reliable connectivity between host and clients.
Guest devices	A compatible device, display, keyboard and mouse for each user.
Applications	Licences and compatibility for shared-session use.

How many seats can my host handle?

One seat is one enabled user account on one licensed host — not a concurrent connection, and not a physical workstation. The host user (console admin) does not count as a seat. Example: a lab with 20 computers and 100 enabled student accounts needs 100 seats, even though only 20 students can be connected at once. Schools, colleges and training labs use a separate licensing system — see Licensing below.

Capacity depends on CPU, RAM, storage and the applications running. In the pilot test on 25 October 2026, 4 concurrent user sessions ran alongside the console administrator on a 12 GB virtual machine (Windows 10 Pro 22H2). That is the documented test — not a promise about classroom sizes. Test your workload before choosing a seat count.

Request a setup review →

Separate sessions share one operating system. They are not individual virtual machines.

System requirements

Tested configuration: Windows 10 Pro, version 22H2, as tested by TrimKore.

Ordinary support for Windows 10 ended on 14 October 2025. Confirm your Windows licensing and update position before deployment. Windows 11 has not been qualified yet — we do not claim Windows 11 compatibility.

Hardware and Microsoft licences are separate. Each user still needs a device, display and input peripherals. For the full requirements list, see the Documentation.

Licensing

MultiDeskKore runs on Windows 10/11 Pro (and Windows Server). One seat is one enabled user account on one licensed host. The MultiDeskKore licence covers the MultiDeskKore software only. The Windows operating-system licence for the host — and any Microsoft licences for the users — are your own responsibility and are separate from the MultiDeskKore licence. Make sure your Windows licensing covers your use, under your agreement with Microsoft.

School licensing (educational institutions). Schools, colleges and training labs have a separate licensing system. School licensing is per physical seat — a workstation in the lab — not per user account, and multiple students share one seat. School licensing is the MDK Fleet (Multi-Host) licensing model: a school runs more than one host, and MDK Solo (Single Host) is a single host, so Solo does not work for a school. MDK Fleet is in development (V2). School pricing is $15 per seat, flat, with a minimum of 25 seats per school licence, and a 10% annual support fee is mandatory. See the schools page and pricing for the full school model.

Compatibility matrix

The same matrix is used on the trial page and in the documentation, so the answer is the same wherever you read it.

Item	Status	Note
Host: Windows 10 Pro, version 22H2	Tested configuration	The configuration MultiDeskKore was tested on.
Host: Windows 11	Compatibility not yet verified	Not tested; no compatibility is claimed. If your host runs Windows 11, tell us in the trial form and we will advise on the next step.
Host: other Windows editions	Not tested	Not part of the tested configuration. Ask us before deploying.
Client: any compatible Remote Desktop client	Supported	Windows Remote Desktop Connection (mstsc) or any compatible RDP client, on the user’s own device.
Network: local network	Required	Version 1 is local-network use.
Network: internet	Not required for local operation	Sessions, licence validation, an activated trial and the console work offline. Only buying seats, support tickets, host-transfer requests and getting a trial key need the website.

Feature status — what is verified, what is available but still awaiting final verification, and what is planned — is on the roadmap.