Skip to content

Commit 8a0dd17

Browse files
committed
move windows access section to top
1 parent 1e20cc9 commit 8a0dd17

File tree

1 file changed

+37
-38
lines changed

1 file changed

+37
-38
lines changed

articles/virtual-machines/windows/serial-console.md

Lines changed: 37 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,43 @@ Serial console for virtual machines is only accessible via [Azure portal](https:
4747

4848
![](../media/virtual-machines-serial-console/virtual-machine-windows-serial-console-connect.gif)
4949

50+
## Access Serial Console for Windows
51+
Newer Windows Server images on Azure will have [Special Administrative Console](https://technet.microsoft.com/library/cc787940(v=ws.10).aspx) (SAC) enabled by default. SAC is supported on server versions of Windows but is not available on client versions (for example, Windows 10, Windows 8, or Windows 7).
52+
To enable Serial console for Windows virtual machines created with using Feb2018 or lower images please use the following steps:
53+
54+
1. Connect to your Windows virtual machine via Remote Desktop
55+
2. From an Administrative command prompt, run the following commands
56+
* `bcdedit /ems {current} on`
57+
* `bcdedit /emssettings EMSPORT:1 EMSBAUDRATE:115200`
58+
3. Reboot the system for the SAC console to be enabled
59+
60+
![](../media/virtual-machines-serial-console/virtual-machine-windows-serial-console-connect.gif)
61+
62+
If needed SAC can be enabled offline as well,
63+
64+
1. Attach the windows disk you want SAC configured for as a data disk to existing VM.
65+
2. From an Administrative command prompt, run the following commands
66+
* `bcdedit /store <mountedvolume>\boot\bcd /ems {default} on`
67+
* `bcdedit /store <mountedvolume>\boot\bcd /emssettings EMSPORT:1 EMSBAUDRATE:115200`
68+
69+
### How do I know if SAC is enabled or not
70+
71+
If [SAC] (https://technet.microsoft.com/library/cc787940(v=ws.10).aspx) is not enabled the serial console will not show the SAC prompt. It can show a VM Health information in some cases or it would be blank.
72+
73+
### Enabling boot menu to show in the serial console
74+
75+
If you need to enable Windows boot loader prompts to show in the serial console, you can add the following additional options to Windows boot loader.
76+
77+
1. Connect to your Windows virtual machine via Remote Desktop
78+
2. From an Administrative command prompt run the following commands
79+
* `bcdedit /set {bootmgr} displaybootmenu yes`
80+
* `bcdedit /set {bootmgr} timeout 5`
81+
* `bcdedit /set {bootmgr} bootems yes`
82+
3. Reboot the system for the boot menu to be enabled
83+
84+
> [!NOTE]
85+
> At this point support for function keys is not enabled, if you require advanced boot options use bcdedit /set {current} onetimeadvancedoptions on, see [bcdedit](https://docs.microsoft.com/windows-hardware/drivers/devtest/bcdedit--set) for more details
86+
5087
## Disable Serial Console
5188
By default, all subscriptions have serial console access enabled for all VMs. You may disable serial console at either the subscription level or VM level.
5289

@@ -105,44 +142,6 @@ If a user is connected to serial console and another user successfully requests
105142
>[!CAUTION]
106143
This means that the user who gets disconnected will not be logged out! The ability to enforce a logout upon disconnect (via SIGHUP or similar mechanism) is still in the roadmap. For Windows, there is an automatic timeout enabled in SAC, however for Linux you can configure terminal timeout setting.
107144
108-
109-
## Access Serial Console for Windows
110-
Newer Windows Server images on Azure will have [Special Administrative Console](https://technet.microsoft.com/library/cc787940(v=ws.10).aspx) (SAC) enabled by default. SAC is supported on server versions of Windows but is not available on client versions (for example, Windows 10, Windows 8, or Windows 7).
111-
To enable Serial console for Windows virtual machines created with using Feb2018 or lower images please use the following steps:
112-
113-
1. Connect to your Windows virtual machine via Remote Desktop
114-
2. From an Administrative command prompt, run the following commands
115-
* `bcdedit /ems {current} on`
116-
* `bcdedit /emssettings EMSPORT:1 EMSBAUDRATE:115200`
117-
3. Reboot the system for the SAC console to be enabled
118-
119-
![](../media/virtual-machines-serial-console/virtual-machine-windows-serial-console-connect.gif)
120-
121-
If needed SAC can be enabled offline as well,
122-
123-
1. Attach the windows disk you want SAC configured for as a data disk to existing VM.
124-
2. From an Administrative command prompt, run the following commands
125-
* `bcdedit /store <mountedvolume>\boot\bcd /ems {default} on`
126-
* `bcdedit /store <mountedvolume>\boot\bcd /emssettings EMSPORT:1 EMSBAUDRATE:115200`
127-
128-
### How do I know if SAC is enabled or not
129-
130-
If [SAC] (https://technet.microsoft.com/library/cc787940(v=ws.10).aspx) is not enabled the serial console will not show the SAC prompt. It can show a VM Health information in some cases or it would be blank.
131-
132-
### Enabling boot menu to show in the serial console
133-
134-
If you need to enable Windows boot loader prompts to show in the serial console, you can add the following additional options to Windows boot loader.
135-
136-
1. Connect to your Windows virtual machine via Remote Desktop
137-
2. From an Administrative command prompt run the following commands
138-
* `bcdedit /set {bootmgr} displaybootmenu yes`
139-
* `bcdedit /set {bootmgr} timeout 5`
140-
* `bcdedit /set {bootmgr} bootems yes`
141-
3. Reboot the system for the boot menu to be enabled
142-
143-
> [!NOTE]
144-
> At this point support for function keys is not enabled, if you require advanced boot options use bcdedit /set {current} onetimeadvancedoptions on, see [bcdedit](https://docs.microsoft.com/windows-hardware/drivers/devtest/bcdedit--set) for more details
145-
146145
## Using Serial Console for NMI calls in Windows VMs
147146
A non-maskable interrupt (NMI) is designed to create a signal that software on a virtual machine will not ignore. Historically, NMIs have been used to monitor for hardware issues on systems that required specific response times. Today, programmers and system administrators often use NMI as a mechanism to debug or troubleshoot systems which are hung.
148147

0 commit comments

Comments
 (0)