Connect to the console session with mstsc /admin

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 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 your VPS provider's control panel. Every example uses 203.0.113.10:3389.

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 VPS provider's control panel.
• Remote Desktop sessions are created when someone connects over RDP on port 3389. 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 session

The 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:3389 /admin

The 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 /admin connection 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. /admin connects you much like a normal session. You still share the same limit of two simultaneous remote sessions.

When /admin is worth using

• Fixing a Session Host server: when users cannot connect because of licensing or broker errors, /admin lets an administrator in to repair it.
• Skipping a broker redirect: in a farm, /admin keeps 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 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:

1. Connect normally and accept the prompt to disconnect one of the other users, if you are allowed to.
2. Or open the browser console from your VPS provider's control panel. It uses the console session, which works even when both RDP sessions are taken.
3. From either place, list and close the old sessions:

   quser
   logoff 3

Replace 3 with the ID of the session you want to end.

Make an admin shortcut

To keep a one-click admin connection:

1. Open Remote Desktop Connection (mstsc), enter 203.0.113.10:3389 and click Show Options → Save As.
2. Save it as server-admin.rdp.
3. Open the file in Notepad and add this line:

   administrative session:i:1

1. Save. Double-clicking the file now connects in admin mode.

Check it works

1. Connect with mstsc /v:203.0.113.10:3389 /admin.
2. In the session, open Command Prompt and run query session.
3. 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 :3389 and that the port answers. See Fix "Remote Desktop can't connect to the remote computer".

Next steps

• Every switch mstsc accepts: Remote Desktop mstsc command-line options explained.
• Close sessions people leave behind: Sign out a stuck or disconnected RDP session.