![]() ![]() To get an unlimited amount of graphics-persistent sessions, you can run Remote Desktop and start terminal sessions from within the "main" session described above. And, of course, autohotkey works perfectly.īut, what if you need more than one persistent, graphics-enabled session? You can reconnect to it and it will become a terminal session again, and you can do this infinitely. This will disconnect you from the session, but it will still run with full graphical context. ![]() ![]() Luckily, we may "convert" a terminal session into a console session instead of disconnecting from Remote Desktop normally by running the following command from inside the terminal session: for /f "skip=1 tokens=3" %%s in ('query user %USERNAME%') do (tscon.exe %%s /dest:console) Programs will still run, but anything that depends on GUI interaction will break badly. RDP sessions will become "deactivated" when there is not a connection to them. Using "rdpwrap" on Github, you can have an unlimited number of terminal sessions. There are two types of sessions in Windows: The "console" session which is always active, and there can only be a max of one of, and "terminal" sessions, a la RDP.
0 Comments
Leave a Reply. |