Connect to the console session with mstsc /admin
Learn what mstsc /admin really does on Windows Server, how the console session differs from an RDP session, and when the switch helps. It is not a licence bypass.
- Intermediate
- Windows VPS
- 4 min read
mstsc /admin is one of the most misunderstood Remote Desktop switches. Older guides call it a way to reach the "console" or to get an extra session, but that changed many Windows versions ago. This guide explains what the switch does today, how the console session fits in, and when it is actually useful on your server.
Before you start
- A RunRacks Windows VPS running Windows Server 2019, 2022 or 2025.
- An account in the local Administrators group. Only administrators can use
/admin. - Your server IP from the Dashboard. Every example uses
203.0.113.10:12230.
Console session vs RDP session
A Windows server can have two kinds of interactive session:
- The console session is the one shown on the server's own screen. On a VPS there is no physical monitor, so the console is what you see in the browser console in your Dashboard control panel.
- Remote Desktop sessions are created when someone connects over RDP on port 12230. Each one is a separate desktop with its own programs.
Since Windows Server 2008, services run in their own isolated session (session 0), and nobody signs in to it interactively. So "connecting to the console" no longer means reaching session 0, and old /console advice does not apply.
You can see all sessions with:
query sessionThe line named console is the console session. Lines named rdp-tcp#… are remote sessions.
What /admin does
Run it like this:
mstsc /v:203.0.113.10:12230 /adminThe switch tells Windows that you are connecting to administer the server, not to use it as a shared application desktop. In practice:
- On a server with the Remote Desktop Session Host role, an
/adminconnection is treated as an administrative session. It does not need an RDS client access licence (CAL) and is not routed through a Connection Broker, so you can log in to fix that specific server even when licensing or the broker is broken. - On a server without that role (the usual setup for a single VPS), the server is already in administration mode.
/adminconnects you much like a normal session. You still share the same limit of two simultaneous remote sessions.
/admin is not a way to get more users onto a server or to avoid buying RDS licences. Microsoft licenses administrative access separately from user access, and running a multi-user desktop still needs the Session Host role and CALs. Check Microsoft's current licensing documentation for details.
When /admin is worth using
- Fixing a Session Host server: when users cannot connect because of licensing or broker errors,
/adminlets an administrator in to repair it. - Skipping a broker redirect: in a farm,
/adminkeeps you on the exact server you named. - Scripts and shortcuts for admins: some teams use it in admin-only shortcuts as a reminder of what the connection is for.
On a single RunRacks Windows VPS without the Session Host role, you rarely need it. A normal connection does the same job.
When all sessions are busy
If both remote sessions are in use, /admin will not create a third. Instead:
- Connect normally and accept the prompt to disconnect one of the other users, if you are allowed to.
- Or open the browser console from the Dashboard. It uses the console session, which works even when both RDP sessions are taken.
- From either place, list and close the old sessions:
quser
logoff 3Replace 3 with the ID of the session you want to end.
logoff closes every program in that session without saving. Make sure you are ending the right one.
Make an admin shortcut
To keep a one-click admin connection:
- Open Remote Desktop Connection (
mstsc), enter203.0.113.10:12230and click Show Options → Save As. - Save it as
server-admin.rdp. - Open the file in Notepad and add this line:
administrative session:i:1- Save. Double-clicking the file now connects in admin mode.
Check it works
- Connect with
mstsc /v:203.0.113.10:12230 /admin. - In the session, open Command Prompt and run
query session. - Your account appears with an
rdp-tcp#…session name and the state Active. The line marked with>is yours.
Troubleshooting
- "The number of connections to this computer is limited": both remote sessions are in use, with or without
/admin. Close one as shown above, or use the browser console. - You land in an existing session: the single-session rule reconnects you to your own earlier session. That is expected. See Allow or block multiple RDP sessions for one user.
- "You must have administrator rights": your account is not in the local Administrators group.
- Connection fails entirely: check that you included
:12230and that the port answers. See Fix "Remote Desktop can't connect to the remote computer".
Next steps
- Every switch
mstscaccepts: Remote Desktop mstsc command-line options explained. - Close sessions people leave behind: Sign out a stuck or disconnected RDP session.
- Compare Windows VPS plans for more resources.
Was this guide helpful?
Still stuck?
Ask RunRacks AI for a quick answer, or open a ticket and our team will take a look at your server.
Related guides
Windows VPS & RDP
RunRacks RDP port 12230: how to connect to your Windows VPS and Admin RDP
RunRacks Windows VPS and Admin RDP servers accept Remote Desktop on port 12230, not 3389. Here is how to connect from every device and keep the port open.
- Beginner
- Windows VPS · Admin RDP
- 5 min read
Windows VPS & RDP
Allow or block multiple RDP sessions for one user
Understand why a new Remote Desktop login takes over your old session, how the single-session policy works on Windows Server, and which setting suits a team.
- Advanced
- Windows VPS
- 5 min read
Windows VPS & RDP
Create Windows users with Remote Desktop access
Give each person their own Windows login, add them to Remote Desktop Users, test the account and remove access cleanly later.
- Beginner
- Windows VPS · Admin RDP
- 2 min read