Merge pull request #58080 from genlin/master105

troubleshoot-activation-problems.md

Author: PRMerger16

articles/virtual-machines/troubleshooting/troubleshoot-activation-problems.md

@@ -13,7 +13,7 @@ ms.workload: na
 ms.tgt_pltfrm: vm-windows
 ms.devlang: na
 ms.topic: troubleshooting
-ms.date: 10/31/2018
+ms.date: 11/15/2018
 ms.author: genli
 ---
 
@@ -25,7 +25,7 @@ If you have trouble when activating Azure Windows virtual machine (VM) that is c
 Azure uses different endpoints for KMS activation depending on the cloud region where the VM resides. When using this troubleshooting guide, use the appropriate KMS endpoint that applies to your region.
 
 * Azure public cloud regions: kms.core.windows.net:1688
-* Azure China national cloud regions: kms.core.chinacloudapi.cn:1688
+* Azure China 21Vianet national cloud regions: kms.core.chinacloudapi.cn:1688
 * Azure Germany national cloud regions: kms.core.cloudapi.de:1688
 * Azure US Gov national cloud regions: kms.core.usgovcloudapi.net:1688
 
@@ -80,8 +80,7 @@ This step does not apply to Windows 2012 or Windows 2008 R2. It uses the Automat
 3. Make sure that the VM is configured to use the correct Azure KMS server. To do this, run the following command:
   
     ```
-    iex “$env:windir\system32\cscript.exe $env:windir\system32\slmgr.vbs /skms
-    kms.core.windows.net:1688
+    iex "$env:windir\system32\cscript.exe $env:windir\system32\slmgr.vbs /skms kms.core.windows.net:1688"
     ```
     The command should return: Key Management Service machine name set to kms.core.windows.net:1688 successfully.
 

articles/virtual-machines/troubleshooting/troubleshoot-rdp-general-error.md

@@ -61,7 +61,7 @@ To resolve this problem, [back up the operating system disk](../windows/snapshot
 
 ### Serial Console
 
-#### Step 1: Turn on Remote Desktop
+#### Step 1: Open CMD instance in Serial console
 
 1. Access the [Serial Console](serial-console-windows.md) by selecting **Support & Troubleshooting** > **Serial console (Preview)**. If the feature is enabled on the VM, you can connect the VM successfully.
 

articles/virtual-machines/troubleshooting/troubleshoot-recovery-disks-windows.md

@@ -234,10 +234,10 @@ Stop-AzureRmVM -ResourceGroupName myResourceGroup -Name $vm.Name -Force
 $disk = Get-AzureRmDisk -ResourceGroupName myResourceGroup -Name newDisk
 
 # Set the VM configuration to point to the new disk  
-Set-AzureRmVMOSDisk -VM $vm -ManagedDiskId $disk.Id -Name $disk.Name 
+Set-AzureRmVMOSDisk -VM $vm -ManagedDiskId $disk.Id -Name $disk.Name  -sto
 
-# Update the VM with the new OS disk
-Update-AzureRmVM -ResourceGroupName myResourceGroup -VM $vm 
+# Update the VM with the new OS disk. Possible values of StorageAccountType include: 'Standard_LRS' and 'Premium_LRS'
+Update-AzureRmVM -ResourceGroupName myResourceGroup -VM $vm -StorageAccountType <Type of the storage account >
 
 # Start the VM
 Start-AzureRmVM -Name $vm.Name -ResourceGroupName myResourceGroup