이 문서에서는 Windows 특별 관리 콘솔(SAC)에 연결하는 방법을 설명합니다.
SAC는 Windows 가상 머신(VM) 인스턴스에 대한 직렬 포트 연결을 사용하며 네트워크 연결을 사용하지 않으므로, Windows VM 인스턴스 문제 해결 또는 복구에 도움됩니다. VM의 직렬 콘솔에 연결하고 SAC를 사용해서 VM'의 부팅 프로세스를 중단하거나 문제 해결을 수행하기 위해 CMD 또는 PowerShell 터미널 액세스 권한을 얻을 수 있습니다. 문제 해결 이외의 범용 원격 데스크톱 환경을 위해서는 RDP를 사용해서 Windows VM에 연결합니다.
시작하기 전에
대화형 직렬 콘솔을 사용하여 VM의 SAC에 연결하려면 먼저 VM에 대화형 액세스를 사용 설정합니다. 자세한 내용은 직렬 콘솔에서 대화형 액세스 사용 설정을 참조하세요.
아직 인증을 설정하지 않았다면 설정합니다.
인증은 Google Cloud 서비스 및 API에 액세스하기 위해 ID를 확인하는 프로세스입니다.
로컬 개발 환경에서 코드 또는 샘플을 실행하려면 다음 옵션 중 하나를 선택하여 Compute Engine에 인증하면 됩니다.
Select the tab for how you plan to use the samples on this page:
Console
When you use the Google Cloud console to access Google Cloud services and
APIs, you don't need to set up authentication.
gcloud
After installing the Google Cloud CLI,
initialize it by running the following command:
Computer is booting, SAC started and initialized.
Use the "ch -?" command for information about using channels.
Use the "?" command for general help.
SAC>
대화형 직렬 콘솔이 빈 화면으로 표시되고 커서가 깜박이면 긴급 관리 서비스가 해제되어 있기 때문일 수 있습니다. 이 문제를 해결하는 방법은 대화형 직렬 콘솔 문제 해결을 참조하세요.
Computer is booting, SAC started and initialized.
Use the "ch -?" command for information about using channels.
Use the "?" command for general help.
SAC>
대화형 직렬 콘솔이 빈 화면으로 표시되고 커서가 깜박이면 긴급 관리 서비스가 해제되어 있기 때문일 수 있습니다. 이 문제를 해결하는 방법은 대화형 직렬 콘솔 문제 해결을 참조하세요.
대화형 직렬 콘솔을 사용하는 방법에 대한 자세한 내용은 Microsoft SAC 명령 문서를 참조하세요.
Windows SAC에서 명령 프롬프트 열기
SAC에서 명령 프롬프트를 열려면 다음을 수행합니다.
cmd를 입력하고 Enter 키를 누릅니다. 다음과 같이 출력이 표시됩니다.
SAC>cmd
The Command Prompt session was successfully launched.
SAC>
EVENT: A new channel has been created. Use "ch -?" for channel help.
Channel: Cmd0001
SAC>
ch -sn CHANNEL_NAME 명령어를 사용한 후 Enter 키를 누릅니다.
ch -sn CHANNEL_NAME
CHANNEL_NAME을 이전 단계에서 만든 채널의 이름으로 바꿉니다.
출력은 다음과 비슷합니다.
Name: Cmd0001
Description: Command
Type: VT-UTF8
Channel GUID: 28de7392-5413-11ea-bb03-c9656a2ed613
Application Type GUID: 63d02271-8aa4-11d5-bccf-00b0d014a2d0
Press <esc><tab> for next channel.
Press <esc><tab>0 to return to the SAC channel.
Use any other key to view this channel.
스페이스바를 누른 다음 시스템에 등록된 로컬 사용자 인증 정보로 로그인합니다.
Please enter login credentials.
Username: USERNAME
Domain: DOMAIN (leave blank if no domain)
Password: PASSWORD
연결되면 명령 프롬프트 셸에 액세스할 수 있습니다.
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\Windows\system32>
선택사항: Powershell 프롬프트에 입력하려면 powershell.exe를 입력한 다음 Enter를 누릅니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-07-30(UTC)"],[[["\u003cp\u003eThis document details how to connect to the Windows Special Administrative Console (SAC) via a serial port, enabling troubleshooting and recovery of Windows virtual machine (VM) instances without network reliance.\u003c/p\u003e\n"],["\u003cp\u003eBefore connecting, ensure you enable interactive access for your VM and set up authentication as required for access to Google Cloud services and APIs.\u003c/p\u003e\n"],["\u003cp\u003eYou can connect to the serial console through the Google Cloud console or using the \u003ccode\u003egcloud\u003c/code\u003e command-line tool, both of which will display a prompt if successfully connected.\u003c/p\u003e\n"],["\u003cp\u003eWithin the SAC, you can access a Command Prompt by typing \u003ccode\u003ecmd\u003c/code\u003e and then use channel commands to interact, or optionally access a PowerShell prompt by typing \u003ccode\u003epowershell.exe\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe SAC is a valuable tool for accessing a CMD or PowerShell terminal for troubleshooting, or interrupting a VM's boot process, but it does not support IP based access restrictions.\u003c/p\u003e\n"]]],[],null,["Windows\n\n*** ** * ** ***\n\nThis document describes how to connect to the\n[Windows Special Administrative Console](https://technet.microsoft.com/en-us/library/cc787940) (SAC).\nThe SAC uses a serial port connection to a Windows virtual machine (VM) instance\nand doesn't rely on network connectivity, which can help troubleshoot or recover\na Windows VM instance. By connecting to the VM's serial console and using the SAC,\nyou can interrupt the VM's boot process or gain access to a CMD or PowerShell\nterminal to perform troubleshooting. For a general purpose remote desktop\nexperience other than troubleshooting,\n[connect to Windows VMs using RDP](/compute/docs/instances/connecting-to-windows).\n\nBefore you begin\n\n- Before you can connect to your VM's SAC by using the interactive serial console, enable interactive access for your VM. For more information, see [Enabling interactive access on the serial console](/compute/docs/troubleshooting/troubleshooting-using-serial-console#enabling_interactive_access_on_the_serial_console).\n- If you haven't already, set up [authentication](/compute/docs/authentication). Authentication verifies your identity for access to Google Cloud services and APIs. To run code or samples from a local development environment, you can authenticate to Compute Engine by selecting one of the following options:\n\n Select the tab for how you plan to use the samples on this page: \n\n Console\n\n\n When you use the Google Cloud console to access Google Cloud services and\n APIs, you don't need to set up authentication.\n\n gcloud\n 1.\n [Install](/sdk/docs/install) the Google Cloud CLI.\n\n After installation,\n [initialize](/sdk/docs/initializing) the Google Cloud CLI by running the following command:\n\n ```bash\n gcloud init\n ```\n\n\n If you're using an external identity provider (IdP), you must first\n [sign in to the gcloud CLI with your federated identity](/iam/docs/workforce-log-in-gcloud).\n | **Note:** If you installed the gcloud CLI previously, make sure you have the latest version by running `gcloud components update`.\n 2. [Set a default region and zone](/compute/docs/gcloud-compute#set_default_zone_and_region_in_your_local_client).\n\n| **Caution:** The interactive serial console does not support IP-based access restrictions such as IP-based include lists or exclude lists. If you enable the interactive serial console on an instance, anyone from any IP address is able to connect if they know a local username, project ID, zone, and instance name.\n\nConnect to the Serial Console\n\nTo connect to your Windows instance using an interactive serial console,\ncomplete the steps in one of the following tabs.\n\nPermissions required for this task\n\nTo perform this task, you must have the following\n[permissions](/iam/docs/overview#permissions):\n\n\n- `compute.instances.setMetadata` on the VM if enabling interactive access on a specific VM\n- `compute.projects.setCommonInstanceMetadata` on the project, if enabling interactive access for all VMs in the project\n- `iam.serviceAccountUser` role on the instance's service account \n\nConsole\n\n1. In the Google Cloud console, go to the **VM instances** page.\n\n [Go to VM instances](https://console.cloud.google.com/compute/instances)\n2. Click the name of the VM you want to connect to.\n\n3. Click **Connect to serial console** to open the interactive\n console.\n\nThe interactive serial console opens. It's ready to use when you see the\nfollowing output: \n\n```\nComputer is booting, SAC started and initialized.\n\nUse the \"ch -?\" command for information about using channels.\nUse the \"?\" command for general help.\n\nSAC\u003e\n```\n\nIf the interactive serial console is a blank screen with a blinking cursor,\nit is likely because the [Emergency Management Services](https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/boot-parameters-to-enable-ems-redirection)\nare off.\nSee [troubleshooting interactive serial console](/compute/docs/troubleshooting/troubleshooting-windows#troubleshooting-interactive-serial-console)\nto learn how to resolve this issue.\n\ngcloud\n\nUse the [`gcloud compute connect-to-serial-port`\ncommand](/sdk/gcloud/reference/compute/connect-to-serial-port) to connect to\nVM instances that have serial port access enabled: \n\n```\ngcloud compute connect-to-serial-port VM_NAME \\\n --port=2 \\\n --zone=ZONE \\\n --project=PROJECT_ID\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the ID of the project that contains the VM\n- \u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e: the name of the zone in which the VM is located\n- \u003cvar translate=\"no\"\u003eVM_NAME\u003c/var\u003e: the name of the VM\n\nThe interactive serial console opens. It is ready to use when you see the\nfollowing output: \n\n```\nComputer is booting, SAC started and initialized.\n\nUse the \"ch -?\" command for information about using channels.\nUse the \"?\" command for general help.\n\nSAC\u003e\n```\n\nIf the interactive serial console is a blank screen with a blinking cursor,\nit is likely because the [Emergency Management Services](https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/boot-parameters-to-enable-ems-redirection)\nare off.\nSee [troubleshooting interactive serial console](/compute/docs/troubleshooting/troubleshooting-windows#troubleshooting-interactive-serial-console)\nto learn how to resolve this issue.\n\nFor information about using the interactive serial console, see the Microsoft\n[SAC Commands documentation](https://technet.microsoft.com/en-us/library/cc787940#sac-commands).\n\nOpen Command Prompt in Windows SAC\n\nTo open Command Prompt in the SAC, do the following:\n\n1. Type `cmd`, then press **Enter**. You see the following output:\n\n ```\n SAC\u003ecmd\n The Command Prompt session was successfully launched.\n SAC\u003e\n EVENT: A new channel has been created. Use \"ch -?\" for channel help.\n Channel: Cmd0001\n SAC\u003e\n ```\n2. Use the `ch -sn `\u003cvar translate=\"no\"\u003eCHANNEL_NAME\u003c/var\u003e command, then press\n **Enter**.\n\n ```\n ch -sn CHANNEL_NAME\n ```\n\n Replace \u003cvar translate=\"no\"\u003eCHANNEL_NAME\u003c/var\u003e with the name of the\n channel you created in the previous step.\n\n The output is similar to the following: \n\n ```\n Name: Cmd0001\n Description: Command\n Type: VT-UTF8\n Channel GUID: 28de7392-5413-11ea-bb03-c9656a2ed613\n Application Type GUID: 63d02271-8aa4-11d5-bccf-00b0d014a2d0\n\n Press \u003cesc\u003e\u003ctab\u003e for next channel.\n Press \u003cesc\u003e\u003ctab\u003e0 to return to the SAC channel.\n Use any other key to view this channel.\n ```\n3. Press **Space**, then login with the local credentials registered on the\n system.\n\n ```\n Please enter login credentials.\n Username: USERNAME\n Domain: DOMAIN (leave blank if no domain)\n Password: PASSWORD\n ```\n | **Note:** If you are unsure of the credentials, you might be able to [create or\n | reset the password](/compute/docs/instances/windows/creating-passwords-for-windows-instances).\n\n Once connected, you have access to a Command Prompt shell. \n\n ```\n Microsoft Windows [Version 10.0.14393]\n (c) 2016 Microsoft Corporation. All rights reserved.\n\n C:\\Windows\\system32\u003e\n ```\n4. Optional: To enter a Powershell prompt, type `powershell.exe`, then press\n **Enter**.\n\n | **Note:** Pasting into the SAC Powershell terminal might result in repeated characters in the pasted text. You can prevent this on a per-session basis by issuing the `Remove-Module PSReadLine` command in your terminal.\n\nWhat's next\n\n- Learn how to [connect to Windows VMs using RDP](/compute/docs/instances/connecting-to-windows)\n- Learn how to [troubleshoot Interactive Serial Console](/compute/docs/troubleshooting/troubleshooting-windows#troubleshooting-interactive-serial-console)."]]