edit pass: site-recovery-deprecation-upgrade

Author: ShawnJackson

articles/site-recovery/upgrade-2012R2-to-2016.md

@@ -1,5 +1,5 @@
 ---
-title: Upgrade Windows Server and System Center Virtual Machine Manager 2012 R2 to 2016 
+title: Upgrade Windows Server and System Center VMM 2012 R2 to 2016 
 description: Learn how to upgrade Windows Server 2012 R2 hosts and System Center Virtual Machine Manager 2012 R2 configured with Azure Site Recovery to Windows Server 2016 and Virtual Machine Manager 2016.
 services: site-recovery
 author: ankitaduttaMSFT
@@ -10,9 +10,9 @@ ms.date: 12/03/2018
 ms.author: ankitadutta
 ---
 
-# Upgrade Windows Server and System Center Virtual Machine Manager 2012 R2 to 2016
+# Upgrade Windows Server and System Center VMM 2012 R2 to 2016
 
-This article shows you how to upgrade Windows Server 2012 R2 hosts and System Center Virtual Machine Manager 2012 R2 configured with Azure Site Recovery to Windows Server 2016 and Virtual Machine Manager 2016.
+This article shows you how to upgrade Windows Server 2012 R2 hosts and System Center Virtual Machine Manager (VMM) 2012 R2 configured with Azure Site Recovery to Windows Server 2016 and VMM 2016.
 
 Site Recovery contributes to your business continuity and disaster recovery (BCDR) strategy. The service ensures that your virtual machine (VM) workloads remain available when expected and unexpected outages occur.
 
@@ -22,33 +22,33 @@ Site Recovery contributes to your business continuity and disaster recovery (BCD
 In this article, you learn how to upgrade the following configurations in your environment:
 
 > [!div class="checklist"]
-> * Windows Server 2012 R2 hosts that Virtual Machine Manager doesn't manage
-> * Windows Server 2012 R2 hosts that a standalone Virtual Machine Manager 2012 R2 server manages
-> * Windows Server 2012 R2 hosts that a highly available Virtual Machine Manager 2012 R2 server manages
+> * Windows Server 2012 R2 hosts that VMM doesn't manage
+> * Windows Server 2012 R2 hosts that a standalone VMM 2012 R2 server manages
+> * Windows Server 2012 R2 hosts that a highly available VMM 2012 R2 server manages
 
 ## Prerequisites and factors to consider
 
 Before you upgrade, note the following:
 
-- If you have Windows Server 2012 R2 hosts that Virtual Machine Manager doesn't manage, and it's a standalone environment setup, there will be a break in replication if you try to perform the upgrade.
-- If you selected **Do not store my keys in Active Directory under Distributed Key Management** while installing Virtual Machine Manager 2012 R2, the upgrades won't finish successfully.
+- If you have Windows Server 2012 R2 hosts that VMM doesn't manage, and it's a standalone environment setup, there will be a break in replication if you try to perform the upgrade.
+- If you selected **Do not store my keys in Active Directory under Distributed Key Management** while installing VMM 2012 R2, the upgrades won't finish successfully.
 
-- If you're using System Center 2012 R2 Virtual Machine Manager:
+- If you're using System Center VMM 2012 R2:
 
-  - Check the database information on Virtual Machine Manager. You can find it by going to the Virtual Machine Manager console and selecting **Settings** > **General** > **Database connection**.
+  - Check the database information on VMM. You can find it by going to the VMM console and selecting **Settings** > **General** > **Database connection**.
   - Check the service accounts that you're using for the System Center Virtual Machine Manager Agent service.
-  - Make sure that you have a backup of the Virtual Machine Manager database.
-  - Note down the database names of the Virtual Machine Manager servers involved. You can find them by going to the Virtual Machine Manager console and selecting **Settings** > **General** > **Database connection**.
-  - Note down the Virtual Machine Manager IDs of the 2012 R2 primary and recovery Virtual Machine Manager servers. You can find the Virtual Machine Manager IDs in the registry: *HKLM:\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Setup*.
-  - Ensure that the new Virtual Machine Manager instances that you add to the cluster have the same names as before.
+  - Make sure that you have a backup of the VMM database.
+  - Note down the database names of the VMM servers involved. You can find them by going to the VMM console and selecting **Settings** > **General** > **Database connection**.
+  - Note down the VMM IDs of the 2012 R2 primary and recovery VMM servers. You can find the VMM IDs in the registry: *HKLM:\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Setup*.
+  - Ensure that the new VMM instances that you add to the cluster have the same names as before.
 
-- If you're replicating between two sites managed by Virtual Machine Manager on both sides, ensure that you upgrade the recovery side before you upgrade the primary side.
+- If you're replicating between two sites managed by VMM on both sides, ensure that you upgrade the recovery side before you upgrade the primary side.
   > [!WARNING]
-  > When you're upgrading Virtual Machine Manager 2012 R2, under **Distributed Key Management**, select **Store encryption keys in Active Directory**. Choose the settings for the service account and distributed key management carefully. Based on your selections, encrypted data such as passwords in templates might not be available after the upgrade and can potentially affect replication with Azure Site Recovery.
+  > When you're upgrading VMM 2012 R2, under **Distributed Key Management**, select **Store encryption keys in Active Directory**. Choose the settings for the service account and distributed key management carefully. Based on your selections, encrypted data such as passwords in templates might not be available after the upgrade and can potentially affect replication with Azure Site Recovery.
 
-For more information, see the detailed Virtual Machine Manager [documentation of prerequisites](/system-center/vmm/upgrade-vmm?view=sc-vmm-2016&preserve-view=true#requirements-and-limitations).
+For more information, see the detailed VMM [documentation of prerequisites](/system-center/vmm/upgrade-vmm?view=sc-vmm-2016&preserve-view=true#requirements-and-limitations).
 
-## Windows Server 2012 R2 hosts that Virtual Machine Manager doesn't manage
+## Windows Server 2012 R2 hosts that VMM doesn't manage
 
 The following steps apply to the user configuration from [Hyper-V hosts to Azure](./hyper-v-azure-architecture.md). You can complete this configuration by following [this tutorial](./hyper-v-prepare-on-premises-tutorial.md).
 
@@ -61,14 +61,14 @@ The following steps apply to the user configuration from [Hyper-V hosts to Azure
 4. [Use these steps](./hyper-v-azure-tutorial.md#source-settings) to register the new Windows Server 2016 host to Azure Site Recovery. Note that the Hyper-V site is already active and you just need to register the new host in the cluster.
 5. Go to the Azure portal and verify the replicated health status inside the Recovery Services vault.
 
-## Upgrade Windows Server 2012 R2 hosts that a standalone Virtual Machine Manager 2012 R2 server manages
+## Upgrade Windows Server 2012 R2 hosts that a standalone VMM 2012 R2 server manages
 
-Before you upgrade your Windows Server 2012 R2 hosts, you need to upgrade Virtual Machine Manager 2012 R2 to Virtual Machine Manager 2016. Use the following steps.
+Before you upgrade your Windows Server 2012 R2 hosts, you need to upgrade VMM 2012 R2 to VMM 2016. Use the following steps.
 
-### Upgrade standalone Virtual Machine Manager 2012 R2 to Virtual Machine Manager 2016
+### Upgrade standalone VMM 2012 R2 to VMM 2016
 
 1. Uninstall the Azure Site Recovery provider. Go to **Control Panel** > **Programs** > **Programs and Features** > **Microsoft Azure Site Recovery**, and then select **Uninstall**.
-2. [Retain the Virtual Machine Manager database and upgrade the operating system](/system-center/vmm/upgrade-vmm?view=sc-vmm-2016&preserve-view=true#back-up-and-upgrade-the-operating-system):
+2. [Retain the VMM database and upgrade the operating system](/system-center/vmm/upgrade-vmm?view=sc-vmm-2016&preserve-view=true#back-up-and-upgrade-the-operating-system):
 
    a. In **Add or remove programs**, select **VMM** > **Uninstall**. 
 
@@ -78,37 +78,37 @@ Before you upgrade your Windows Server 2012 R2 hosts, you need to upgrade Virtua
 
    d. Review the summary and select **Uninstall**.
 
-4. [Install Virtual Machine Manager 2016](/system-center/vmm/upgrade-vmm?view=sc-vmm-2016&preserve-view=true#install-vmm-2016).
-5. Open Virtual Machine Manager and check the status of each host under the **Fabrics** tab. Select **Refresh** to get the most recent status. You should see a status of **Needs Attention**.
-6. [Install the latest Azure Site Recovery provider (direct download)](https://aka.ms/downloaddra) on Virtual Machine Manager.
-7. Install the latest [Microsoft Azure Recovery Service (MARS) agent](https://aka.ms/latestmarsagent) on each host of the cluster. Refresh to ensure that Virtual Machine Manager can successfully query the hosts.
+4. [Install VMM 2016](/system-center/vmm/upgrade-vmm?view=sc-vmm-2016&preserve-view=true#install-vmm-2016).
+5. Open VMM and check the status of each host under the **Fabrics** tab. Select **Refresh** to get the most recent status. You should see a status of **Needs Attention**.
+6. [Install the latest Azure Site Recovery provider (direct download)](https://aka.ms/downloaddra) on VMM.
+7. Install the latest [Microsoft Azure Recovery Service (MARS) agent](https://aka.ms/latestmarsagent) on each host of the cluster. Refresh to ensure that VMM can successfully query the hosts.
 
 ## Upgrade Windows Server 2012 R2 hosts to Windows Server 2016
 
 1. Follow [these steps](/windows-server/failover-clustering/cluster-operating-system-rolling-upgrade#cluster-os-rolling-upgrade-process) to perform the rolling cluster upgrade.
-2. After you add the new host to the cluster, refresh the host from the Virtual Machine Manager console to install the Virtual Machine Manager agent on this updated host.
+2. After you add the new host to the cluster, refresh the host from the VMM console to install the VMM agent on this updated host.
 3. Run `Update-VMVersion` to update the versions of the virtual machines.
 4. Go to the Azure portal and verify the replicated health status of the virtual machines inside the Recovery Services vault.
 
-## Upgrade Windows Server 2012 R2 hosts that a highly available Virtual Machine Manager 2012 R2 server manages
+## Upgrade Windows Server 2012 R2 hosts that a highly available VMM 2012 R2 server manages
 
-Before you upgrade your Windows Server 2012 R2 hosts, you need to upgrade Virtual Machine Manager 2012 R2 to Virtual Machine Manager 2016. The following modes of upgrade are supported while you're upgrading Virtual Machine Manager 2012 R2 servers configured with:
+Before you upgrade your Windows Server 2012 R2 hosts, you need to upgrade VMM 2012 R2 to VMM 2016. The following modes of upgrade are supported while you're upgrading VMM 2012 R2 servers configured with:
 
-- Site Recovery mixed mode with no additional Virtual Machine Manager servers.
-- Site Recovery mixed mode with additional Virtual Machine Manager servers.
+- Site Recovery mixed mode with no additional VMM servers.
+- Site Recovery mixed mode with additional VMM servers.
 
-### Upgrade Virtual Machine Manager 2012 R2 to Virtual Machine Manager 2016
+### Upgrade VMM 2012 R2 to VMM 2016
 
 1. Uninstall the Azure Site Recovery provider. Go to **Control Panel** > **Programs** > **Programs and Features** > **Microsoft Azure Site Recovery**, and then select **Uninstall**.
 2. Follow [these steps](/system-center/vmm/upgrade-vmm?view=sc-vmm-2016&preserve-view=true#upgrade-a-standalone-vmm-server) based on the mode of upgrade that you want to execute.
-3. Open the Virtual Machine Manager console and check the status of each host under the **Fabrics** tab. Select **Refresh** to get the most recent status. You should see a status of **Needs Attention**.
-4. [Install the latest Azure Site Recovery provider (direct download)](https://aka.ms/downloaddra) on Virtual Machine Manager.
-5. Update the latest [Microsoft Azure Recovery Service (MARS) agent](https://aka.ms/latestmarsagent) on each host of the cluster. Refresh to ensure that Virtual Machine Manager can successfully query the hosts.
+3. Open the VMM console and check the status of each host under the **Fabrics** tab. Select **Refresh** to get the most recent status. You should see a status of **Needs Attention**.
+4. [Install the latest Azure Site Recovery provider (direct download)](https://aka.ms/downloaddra) on VMM.
+5. Update the latest [Microsoft Azure Recovery Service (MARS) agent](https://aka.ms/latestmarsagent) on each host of the cluster. Refresh to ensure that VMM can successfully query the hosts.
 
 ### Upgrade Windows Server 2012 R2 hosts to Windows Server 2016
 
 1. Follow [these steps](/windows-server/failover-clustering/cluster-operating-system-rolling-upgrade#cluster-os-rolling-upgrade-process) to perform the rolling cluster upgrade.
-2. After you add the new host to the cluster, refresh the host from the Virtual Machine Manager console to install the Virtual Machine Manager agent on this updated host.
+2. After you add the new host to the cluster, refresh the host from the VMM console to install the VMM agent on this updated host.
 3. Run `Update-VMVersion` to update the VM versions of the virtual machines.
 4. Go to the Azure portal and verify the replicated health status of the virtual machines inside the Recovery Services vault.