MultiDeskKore — End-User Guide

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 guide is for the person using a MultiDeskKore seat — the user connecting to a desktop on the shared host. If you administer the host, see the Administrator Guide instead.

1. What you get

Your administrator has created an account for you on a shared host computer. One seat is one user account on one licensed host: your seat is your account. When you connect, you get your own Windows desktop running on that host — your own apps, your own files, your own settings — while other users have their own separate desktops on the same host at the same time.

You need:

• A device with a display, keyboard, and mouse.
• A Remote Desktop client (Windows Remote Desktop Connection, or any compatible RDP client).
• The host address, your username, and your password — all from your administrator.

2. Connecting

From a Windows PC

1. Open Remote Desktop Connection (mstsc).
2. Computer: the host address your administrator gave you.
3. Click Connect, then sign in with the username and password your administrator created for you.
4. Your desktop opens. The first sign-in takes a little longer while Windows prepares your profile.

From a thin client

Use the thin client's Remote Desktop client the same way: host address, then your username and password. Your administrator will show you where those go on your device.

If the sign-in fails

• Check the username and password carefully — passwords are case-sensitive. If you are unsure, ask your administrator; they can reset your password from the console.
• If the host address does not respond at all, the host may be off or the network may be down — tell your administrator.
• If your account was created directly in Windows instead of in the console, sign-in is stopped — only accounts created through the console can sign in. Ask your administrator to create your account in the console.

3. What you see

• A normal Windows desktop, with the wallpaper your administrator chose. You cannot change the wallpaper.
• Your own files in your own workspace folder.
• The apps your administrator has made available to you. Some apps may be hidden from your Start Menu if your administrator has not allowed them for you — that is by design, not a fault.
• A Transfer folder: the place to put files you want to share with the administrator or another user. It is the only way to share files — see section 5.

4. Signing out vs disconnecting

This is the most important difference to understand.

⚠ Disconnecting does not free your seat — and neither does signing out.

Closing the Remote Desktop window only disconnects — your session keeps running on the host, with your apps open, until you sign out. Only Sign out (Start → your user icon → Sign out, inside your desktop) ends your session. Neither frees your seat: your seat belongs to your account, and only your administrator disabling or deleting your account frees it for someone else. If you cannot sign out yourself, ask your administrator: they can sign your disconnected session out (Kick) from the console, which ends the session at once.

Rule of thumb: disconnect when you are coming back later today and want your work waiting for you. Sign out when you are finished for the day, or when your administrator asks you to (for example, after they change your apps or wallpaper — those changes apply at your next sign-in, and signing out is what starts a fresh sign-in).

5. What you can and cannot do

You can:

• Use the apps your administrator has allowed for you.
• Save files in your own workspace folder.
• Share a file by putting it in your Transfer folder.
• Copy and paste between your session and your own device, if your administrator has left clipboard redirection on.
• Use your own device's drives inside the session, if your administrator has left drive redirection on.

You cannot:

• Open the host's full C: or D: drives. You can reach only your own folders, shared folders assigned to you, and your Transfer folder.
• Open another user's folders.
• Change the desktop wallpaper.
• Install software for everyone, or change settings that affect other users. (What you can install for yourself depends on how your administrator set up your account — ask them.)
• Create new user accounts. Accounts are created only by the administrator, in the console.

6. Sharing files — the Transfer folder

To share a file with the administrator or another user:

1. Put the file in your Transfer folder.
2. Tell the person it is there.

That is the only way to share files between users. Do not try to reach another user's folders directly — you cannot, and that is intentional.

7. Getting help

If something is not working — you cannot connect, an app will not open, a file is missing — tell your administrator. They can see your session in the console, and if they need to look at your screen to help you, they will ask your permission first: screen assistance always asks you before anyone can watch or control your desktop.

MultiDeskKore V1 · by TrimKore · trimkore.com

MultiDeskKore V1 · by TrimKore · trimkore.com · Tested configuration: Windows 10 Pro 22H2. The Markdown files in Docs/ are the canonical source for these pages.