Adding in 2012 specific steps

Author: cynthn

articles/virtual-machines/windows-in-place-upgrade.md

@@ -25,22 +25,22 @@ Before you begin an in-place upgrade:
 
    - Upgrade options for Windows Server 2022 from Windows Server 2016 or Windows Server 2019
 
-- Verify the operating system disk has enough [free space to perform the in-place upgrade](/windows-server/get-started/hardware-requirements#storage-controller-and-disk-space-requirements). If additional space is needed [follow these steps](./windows/expand-os-disk.md) to expand the operating system disk attached to the VM.  
+- Verify the operating system disk has enough [free space to perform the in-place upgrade](/windows-server/get-started/hardware-requirements#storage-controller-and-disk-space-requirements). If more space is needed [follow these steps](./windows/expand-os-disk.md) to expand the operating system disk attached to the VM.  
 
 - Disable antivirus and anti-spyware software and firewalls. These types of software can conflict with the upgrade process. Re-enable antivirus and anti-spyware software and firewalls after the upgrade is completed. 
 
 
-## Upgrade VM to volume license (KMS server activation) 
+## Upgrade VM to volume license (KMS server activation)
 
-The upgrade media provided by Azure requires the VM to be configured for Windows Server volume licensing. This is the default behavior for any Windows Server VM that was installed from a generalized image in Azure. If the VM was imported into Azure, then it may need to be converted to volume licensing to use the upgrade media provided by Azure. To confirm the VM is configured for volume license activation follow these steps to [configure the appropriate KMS client setup key](/troubleshoot/azure/virtual-machines/troubleshoot-activation-problems#step-1-configure-the-appropriate-kms-client-setup-key). If the activation configuration was changed, then follow these steps to [verify connectivity to Azure KMS service](/troubleshoot/azure/virtual-machines/troubleshoot-activation-problems#step-2-verify-the-connectivity-between-the-vm-and-azure-kms-service). 
+The upgrade media provided by Azure requires the VM to be configured for Windows Server volume licensing. This is the default behavior for any Windows Server VM that was installed from a generalized image in Azure. If the VM was imported into Azure, then it might need to be converted to volume licensing to use the upgrade media provided by Azure. To confirm the VM is configured for volume license activation follow these steps to [configure the appropriate KMS client setup key](/troubleshoot/azure/virtual-machines/troubleshoot-activation-problems#step-1-configure-the-appropriate-kms-client-setup-key). If the activation configuration was changed, then follow these steps to [verify connectivity to Azure KMS service](/troubleshoot/azure/virtual-machines/troubleshoot-activation-problems#step-2-verify-the-connectivity-between-the-vm-and-azure-kms-service). 
 
 
 
-## Upgrade to Managed Disks 
+## Upgrade to Managed Disks
 
 The in-place upgrade process requires the use of Managed Disks on the VM to be upgraded. Most VMs in Azure are using Managed Disks, and retirement for unmanaged disks support was announced in November of 2022. If the VM is currently using unmanaged disks, then follow these steps to [migrate to Managed Disks](./windows/migrate-to-managed-disks.md).
 
- ## Create snapshot of the operating system disk 
+ ## Create snapshot of the operating system disk
 
 We recommend that you create a snapshot of your operating system disk and any data disks before starting the in-place upgrade process. This enables you to revert to the previous state of the VM if anything fails during the in-place upgrade process. To create a snapshot on each disk, follow these steps to [create a snapshot of a disk](./snapshot-copy-managed-disk.md). 
 
@@ -154,7 +154,7 @@ Attach the upgrade media for the target Windows Server version to the VM which w
 
 
 
-## Perform in-place upgrade 
+## Perform in-place upgrade to Windows Server 2016, 2019, or 2022
 
 To initiate the in-place upgrade the VM must be in the `Running` state. Once the VM is in a running state use the following steps to perform the upgrade.
 
@@ -176,6 +176,33 @@ To initiate the in-place upgrade the VM must be in the `Running` state. Once the
 
 During the upgrade process the VM will automatically disconnect from the RDP session. After the VM is disconnected from the RDP session the progress of the upgrade can be monitored through the [screenshot functionality available in the Azure portal](/troubleshoot/azure/virtual-machines/boot-diagnostics#enable-boot-diagnostics-on-existing-virtual-machine).
 
+## Perform in-place upgrade to Windows Server 2012 only
+
+To initiate the in-place upgrade the VM must be in the `Running` state. Once the VM is in a running state use the following steps to perform the upgrade.
+
+1. Connect to the VM using [RDP](./windows/connect-rdp.md#connect-to-the-virtual-machine) or [RDP-Bastion](../bastion/bastion-connect-vm-rdp-windows.md#rdp).
+
+1. Determine the drive letter for the upgrade disk (typically E: or F: if there are no other data disks).
+
+1. Start Windows PowerShell.
+
+1. Change directory to the only directory on the upgrade disk.
+
+1. Execute the following command to start the upgrade:
+   
+   ```powershell
+   .\setup.exe 
+   ```
+
+1. When Windows Setup launches, select **Install now**.
+1. For **Get important updates for Windows Setup**, select **No thanks**.
+1. Select the correct Windows Server 2012 "Upgrade to" image based on the current version and configuration of the VM using the [Windows Server upgrade matrix](/windows-server/get-started/upgrade-overview).
+1. On the **License terms** page, select **I accept the license terms** and then select **Next**.
+1. For **What type of installation do you want?" select **Upgrade: Install Windows and keep files, settings, and applications**.
+1. Setup will product a **Compatibility report**, you can ignore any warnings and select **Next**.
+1. When complete, the machine will reboot and you will automatically be disconnected from the RDP session. After the VM is disconnected from the RDP session the progress of the upgrade can be monitored through the [screenshot functionality available in the Azure portal](/troubleshoot/azure/virtual-machines/boot-diagnostics#enable-boot-diagnostics-on-existing-virtual-machine).
+
+
 ## Post upgrade steps 
 
 Once the upgrade process has completed successfully the following steps should be taken to clean up any artifacts which were created during the upgrade process: