The Allow prompt and view-only sessions

RemoteAccessApp never connects to a PC behind someone's back. Unless the PC has unattended access for your console, the person at the PC decides.

What the person at the PC sees

When you connect, a window asks Allow remote access? It shows who wants to connect, and whether it's a Console or a Browser, with its ID. It says you'll be able to see the screen and control the PC. They click Allow or Don't allow. An AI assistant connecting through MCP gets the same prompt, with its own name in it.

• If nobody answers in 45 seconds, the answer is no.
• When you connect from a browser, they can choose how long to remember that browser, from 1 hour to Until I turn it off.
• The prompt is hidden from the picture you see, so you can't click it for them. While it's open, your mouse, keyboard and command prompt are paused.

While you're connected, a Remote session active notice stays on their screen. Small chips on it show what you're using, such as the screen, control, the clipboard, sound or a terminal.

Waiting for the PC to allow this

The Console shows Waiting for (the PC) to allow this until someone clicks Allow. The session opens as soon as they do. Let them know you're about to connect, so they're ready.

The PC declined the connection

The person clicked Don't allow, closed the prompt, or didn't answer in time. Check with them, then choose Ask again.

If it's your own PC and nobody is there, nobody can click Allow. Set up unattended access the next time you're at that PC. Or, at that PC, set a permanent password, so you can reach it from your Recent PCs with nobody there to click Allow.

Commands without a live session

From Devices, Run a command… and Open command prompt work without opening a live session. The PC decides the same way it does for a session:

• If unattended access lets your console in, the command runs straight away.
• Otherwise the person at the PC sees Allow this command? with who's asking and the exact command, or Allow a command prompt? for an interactive prompt. Nothing runs until they click Allow. If nobody answers in 45 seconds, the answer is no.

While it waits, the Console shows Waiting for the person at the PC to allow it…. If they say no, you see The person at the PC said no.

Nobody sees the screen, but the Remote session active notice shows on the PC while the command runs, and the PC's activity history lists it. It stops when you close it or disconnect, or when the person at the PC turns off Allow remote control. A PC with an older RemoteAccessApp says Update RemoteAccessApp on (the PC) to run commands without opening a session.

Run a command… can also run a VBScript. The PC needs VBScript turned on in Windows, and Windows 11 can remove it.

It can also run a batch file: choose Batch (.bat) and type or paste several lines. Labels, goto, setlocal and %~dp0 work, because the PC saves it as a .bat file and runs it. Batch files run on Windows PCs only.

Run a file from your PC

To run a script you already have, click Run a file… in the Run a command window, or drop the file on it. You can pick a .ps1, .bat, .cmd or .vbs file for Windows PCs, or a .sh file for Linux PCs. You don't have to save it anywhere first. To copy a file to a PC without running it, send files to the PC instead.

• The window shows the file's name, type, size and text. Check it, then click Run. It runs once on every PC you picked.
• Nothing runs on your own PC. Each PC gets the text and runs it as a file in a private folder, which is deleted afterwards.
• The Allow this command? prompt shows the file's name and all of its text, so the person at the PC sees exactly what will run.
• A PC that can't run that kind of file says why. For example, a Linux PC says Batch files run on Windows PCs only.
• Files can be up to 1 MB. A PC with an older RemoteAccessApp says Update RemoteAccessApp on (the PC) to run script files (or batch files).
• Afterwards, click Save to Scripts to keep it for next time.

View only

A View only pill means control is turned off on that PC. You can watch, but your mouse and keyboard aren't sent, and commands, Windows tools and serial ports can't be used. In a browser, a view-only PC doesn't share its files either, as copy, paste and send files from your phone explains. This is the PC's choice:

• Allow mouse & keyboard control was left off when the PC was set up (it's one of the choices in connect to your first PC), or
• the person at the PC turned off Allow remote control in the menu of the RemoteAccessApp icon, next to the clock.

Ask them to turn Allow remote control back on. If the PC allows control but nothing happens when you type, check that Control is on in the session toolbar. If clicks only stop working while a program that runs as administrator is in front, see an admin window is blocking my clicks.