Windows tip of the day for Admins
Windows tip of the day for Admins
I never knew this was possible so I thought I would pass it along to my fellow Windows Admins on this board.
Using Terminal Server Client to connect to the Console Session of the server (only works with W2k3 server)
How to Connect to the Console Session
To connect to the remote Windows Server 2003-based computer, open a command prompt, and then type the following command:
mstsc -v:servername /F -console
where mstsc is the Remote Desktop connection executable file, -v indicates a server to connect to, /F indicates full screen mode, and -console is the instruction to connect to the console session.
When you use this command, you open the Remote Desktop session, and when the logon is authenticated, you are connected to the console session that is running on the Windows Server 2003-based server. If a user is currently working on the console session at the computer, you receive the following error message:
The user domain\username is logged locally on to this computer. The user has been idled for number minutes. The desktop is unlocked. If you continue, this user`s session will end and any unsaved data will be lost. Do you want to continue?
The user of the current console session is then logged off, and you receive a message that states that the computer is currently locked and only an administrator can unlock it.
Note: If the console session user and the Terminal Services session user are the same, you can connect without any problems.
Using Terminal Server Client to connect to the Console Session of the server (only works with W2k3 server)
How to Connect to the Console Session
To connect to the remote Windows Server 2003-based computer, open a command prompt, and then type the following command:
mstsc -v:servername /F -console
where mstsc is the Remote Desktop connection executable file, -v indicates a server to connect to, /F indicates full screen mode, and -console is the instruction to connect to the console session.
When you use this command, you open the Remote Desktop session, and when the logon is authenticated, you are connected to the console session that is running on the Windows Server 2003-based server. If a user is currently working on the console session at the computer, you receive the following error message:
The user domain\username is logged locally on to this computer. The user has been idled for number minutes. The desktop is unlocked. If you continue, this user`s session will end and any unsaved data will be lost. Do you want to continue?
The user of the current console session is then logged off, and you receive a message that states that the computer is currently locked and only an administrator can unlock it.
Note: If the console session user and the Terminal Services session user are the same, you can connect without any problems.
Thread
Thread Starter
Forum
Replies
Last Post
TLDude876
Car Talk
134
Dec 28, 2016 03:18 PM
ahsm
3G TL Problems & Fixes
3
Sep 9, 2015 08:35 AM






