기존에 Windows Server 2003, Windows XP의 원격 데스크탑 에서 콘솔 모드로 접속하려면

mstsc /console 명령어를 이용하였는데 언제 부턴가 콘솔 접속이 잘 안되는 문제가 발생했습니다.

처음에는 피씨 mstsc가 이상하다고 생각했는데 구글링을 해보니 그게 아니더군요~!!

Windows Server 2008이 나오면서 정확히는 RDC(Remote Desktop Connection)가 6.1로 버전업되면서

mstsc /console 이 아닌 mstsc /admin 으로 바뀌었습니다.

이는 아래 운영체제 일때 적용됩니다.

Windows Server 2008
Windows Vista Service Pack 1(SP1)
Windows XP Service Pack 3 (SP3)


다음은 Microsoft 홈페이지의 내용입니다.

Changes to remote administration in Windows Server 2008

In Windows Server 2003, you can start the RDC client (Mstsc.exe) by using the /console switch to remotely connect to the physical console session on the server (also known as session 0). In Windows Server 2008, the /console switch has been deprecated. For more information, see the “Why the /console switch is no longer needed” section. In Windows Server 2008, session 0 is a noninteractive session that is reserved for services.

You can use the new /admin switch to remotely connect to a Windows Server 2008-based server for administrative purposes. The /admin switch is introduced in RDC 6.1. RDC 6.1 is included in the following operating systems:
Windows Server 2008
Windows Vista Service Pack 1 (SP1)
Windows XP Service Pack 3 (SP3)

Note RDC 6.1 (6.0.6001) supports Remote Desktop Protocol (RDP) 6.1.

RDC 6.1 does not support the /console switch. However, for backward compatibility, you can use the /admin switch to connect to the physical console session on a Windows Server 2003-based server. For example, to connect from a Windows Vista SP1-based client to the physical console session of a Windows Server 2003-based server, run the mstsc.exe /admin command.

If you try to use the /console switch together with the RDC 6.1 client, the behavior is as follows.

Scenario Behavior
You type mstsc.exe /console at the command prompt, and then you connect to a remote server that does not have Terminal Server installed. The /console switch is silently ignored. You will be connected to a session to remotely administer the server.
For more information about the Windows Server 2008 behavior, see the "When you connect to a server that does not have Terminal Server installed" section.
You type mstsc.exe /console at the command prompt, and then you connect to a remote server that has Terminal Server installed. The /console switch is silently ignored. You will be connected to a standard Remote Desktop session that requires a Terminal Services client access license (TS CAL).
In the RDC client UI, you specify Computer_name /console in the Computer box, and then you click Connect.

Note Computer_name represents the name of the remote computer to which you want to connect.
You receive an “An unknown parameter was specified in computer name field" error message.
In the .rdp file, you specify /console in the full address property, and then you try to start the Remote Desktop connection. You receive an "An unknown parameter was specified in computer name field" error message.
In the .rdp file, you specify the connect to console property, and then you start the Remote Desktop connection. The property is silently ignored. You will be connected to a session that requires a TS CAL.
You programmatically call the put_ConnectToServerConsole function or the get_ConnectToServerConsole function of the IMsRdpClientAdvancedSettings interface. The function fails, and it returns an S_FALSE value.


http://serapian.pe.kr/trackback/245 관련글 쓰기
  • Jae Lee 2010/03/06 08:16

    콘솔 접속이 되지 않아서 모니터 붙여서 작업 할뻔 했습니다. 금요일 저녁 시간에 한시간 절약 해주셨습니다. 감사합니다. Jae.