update common scenarios

asinn826 · asinn826 · commit 8014157da2b4 · 2018-08-28T14:40:35.000-07:00
diff --git a/articles/virtual-machines/linux/serial-console.md b/articles/virtual-machines/linux/serial-console.md
@@ -35,7 +35,7 @@ For serial console documentation for Windows VMs, [click here](../windows/serial
 * Your virtual machine  MUST have [boot diagnostics](boot-diagnostics.md) enabled - see screenshot below.
 
     ![](../media/virtual-machines-serial-console/virtual-machine-serial-console-diagnostics-settings.png)
-    
+
 * The Azure account using the serial console must have [Contributor role](../../role-based-access-control/built-in-roles.md) for the VM and the [boot diagnostics](boot-diagnostics.md) storage account. 
 * The virtual machine for which you are acessing serial console must also have a password-based account. You can create one with the [reset password](https://docs.microsoft.com/azure/virtual-machines/extensions/vmaccess#reset-password) functionality of the VM access extension - see the screenshot below.
 
@@ -121,14 +121,14 @@ This means that the user who gets disconnected will not be logged out! The abili
 The serial console functionality can be deactivated for specific VMs by disabling that VM's boot diagnostics setting.
 
 ## Common scenarios for accessing serial console 
-Scenario          | Actions in serial console                |  OS Applicability 
-:------------------|:-----------------------------------------|:------------------
-Broken FSTAB file | `Enter` key to continue and fix fstab file using a text editor. You may need to be in single user mode for this. See [how to fix fstab issues](https://support.microsoft.com/help/3206699/azure-linux-vm-cannot-start-because-of-fstab-errors) and [Using Serial Console to access GRUB and Single User Mode](serial-console-grub-single-user-mode.md) to get started. | Linux 
-Incorrect firewall rules | Access serial console and fix iptables or Windows firewall rules. | Linux/Windows 
-Filesystem corruption/check | Access serial console and recover filesystem. | Linux/Windows 
-SSH/RDP configuration issues | Access serial console and change settings. | Linux/Windows 
-Network lock down system| Access serial console via portal to manage system. | Linux/Windows 
-Interacting with bootloader | Access GRUB/BCD via the serial console. Go to [Using Serial Console to access GRUB and Single User Mode](serial-console-grub-single-user-mode.md) to get started. | Linux/Windows 
+Scenario          | Actions in serial console                
+:------------------|:-----------------------------------------
+Broken FSTAB file | `Enter` key to continue and fix fstab file using a text editor. You may need to be in single user mode for this. See [how to fix fstab issues](https://support.microsoft.com/help/3206699/azure-linux-vm-cannot-start-because-of-fstab-errors) and [Using Serial Console to access GRUB and Single User Mode](serial-console-grub-single-user-mode.md) to get started.
+Incorrect firewall rules | Access serial console and fix iptables. 
+Filesystem corruption/check | Access serial console and recover filesystem. 
+SSH/RDP configuration issues | Access serial console and change settings. 
+Network lock down system| Access serial console via portal to manage system. 
+Interacting with bootloader | Access GRUB via the serial console. Go to [Using Serial Console to access GRUB and Single User Mode](serial-console-grub-single-user-mode.md) to get started. 
 
 ## Access Serial Console for Linux
 In order for serial console to function properly, the guest operating system must be configured to read and write console messages to the serial port. Most [Endorsed Azure Linux Distributions](https://docs.microsoft.com/azure/virtual-machines/linux/endorsed-distros) have the serial console configured by default. Simply clicking the Serial Console section in the Azure portal will provide access to the console. 
diff --git a/articles/virtual-machines/windows/serial-console.md b/articles/virtual-machines/windows/serial-console.md
@@ -36,7 +36,7 @@ For serial console documentation for Linux VMs, [click here](../linux/serial-con
 * Virtual machine  MUST have [boot diagnostics](boot-diagnostics.md) enabled 
 
     ![](../media/virtual-machines-serial-console/virtual-machine-serial-console-diagnostics-settings.png)
-    
+
 * The account using the serial console must have [Contributor role](../../role-based-access-control/built-in-roles.md) for VM and the [boot diagnostics](boot-diagnostics.md) storage account. 
 * The virtual machine for which you are acessing serial console must also have a password-based account. You can create one with the [reset password](https://docs.microsoft.com/azure/virtual-machines/extensions/vmaccess#reset-password) functionality of the VM access extension - see the screenshot below.
 
@@ -75,7 +75,7 @@ If needed SAC can be enabled offline as well,
 
 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.  
 
-### Enabling boot menu to show in the serial console 
+## Enabling boot menu to show in the serial console 
 
 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.
 
@@ -147,6 +147,15 @@ If a user is connected to serial console and another user successfully requests
 >[!CAUTION] 
 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. 
 
+## Common scenarios for accessing serial console 
+Scenario          | Actions in serial console                
+:------------------|:-----------------------------------------
+Incorrect firewall rules | Access serial console and fix Windows firewall rules. 
+Filesystem corruption/check | Access serial console and recover filesystem. 
+RDP configuration issues | Access serial console and change settings. Go to the [RDP documentation](https://docs.microsoft.com/windows-server/remote/remote-desktop-services/clients/remote-desktop-allow-access) to get started.
+Network lock down system| Access serial console via portal to manage system. Some network commands are listed in the [Serial Console CMD and PowerShell documentation](./serial-console-cmd-ps-commands.md). 
+Interacting with bootloader | Access BCD via the serial console. Go to [Enabling boot menu to show in the serial console](#enabling-boot-menu-to-show-in-the-serial-console) to get started. 
+
 ## Using Serial Console for NMI calls in Windows VMs
 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.
 
