Merge pull request #261767 from Farha-Bano/Doc_updates_scvmm_Dec21

Doc updates

Author: v-regandowner

articles/azure-arc/system-center-virtual-machine-manager/disaster-recovery.md

@@ -3,7 +3,7 @@ title: Recover from accidental deletion of resource bridge VM
 description: Learn how to perform recovery operations for the Azure Arc resource bridge VM in Azure Arc-enabled System Center Virtual Machine Manager disaster scenarios.
 ms.topic: how-to 
 ms.custom:
-ms.date: 12/06/2023
+ms.date: 12/28/2023
 ms.services: azure-arc
 ms.subservice: azure-arc-scvmm
 author: Farha-Bano
@@ -27,12 +27,14 @@ To recover from Arc resource bridge VM deletion, you need to deploy a new resour
 > DHCP-based Arc Resource Bridge deployment is no longer supported.<br><br>
 If you had deployed Arc Resource Bridge earlier using DHCP, you must clean up your deployment by removing your resources from Azure and do a [fresh onboarding](./quickstart-connect-system-center-virtual-machine-manager-to-arc.md).
 
-1. Copy the Azure region and resource IDs of the Arc resource bridge, custom location, and SCVMM Azure resources.
+### Recover Arc resource bridge from a Windows machine
 
-2. Download the [onboarding script](/azure/azure-arc/system-center-virtual-machine-manager/quickstart-connect-system-center-virtual-machine-manager-to-arc#download-the-onboarding-script) from the Azure portal and update the following section in the script, using the same information as the original resources in Azure.
+1.	Copy the Azure region and resource IDs of the Arc resource bridge, custom location, and SCVMM management server Azure resources.
+
+2.	Download [this script](https://download.microsoft.com/download/a/a/8/aa8687e4-1a30-485f-9de4-4f15fc576724/arcvmm-windows-dr.ps1) and update the following section in the script using the same information as the original resources in Azure. 
 
     ```powershell
-    $location = <Azure region of the resources>
+    $location = <Azure region of the original Arc resource bridge>
     $applianceSubscriptionId = <subscription-id>
     $applianceResourceGroupName = <resource-group-name>
     $applianceName = <resource-bridge-name>
@@ -45,20 +47,10 @@ If you had deployed Arc Resource Bridge earlier using DHCP, you must clean up yo
     $vmmserverResourceGroupName = <resource-group-name>
     $vmmserverName= <SCVMM-name-in-azure>
     ```
+ 
+3.	Run the updated script from the same location where the config YAML files are stored after the initial onboarding. This is most likely the same folder from where you ran the initial onboarding script unless the config files were moved later to a different location. [Provide the inputs](quickstart-connect-system-center-virtual-machine-manager-to-arc.md#script-runtime) as prompted. 
 
-3. [Run the onboarding script](/azure/azure-arc/system-center-virtual-machine-manager/quickstart-connect-system-center-virtual-machine-manager-to-arc#download-the-onboarding-script) again with the `-Force` parameter.
-
-    ``` powershell-interactive
-    ./resource-bridge-onboarding-script.ps1 -Force
-    ```
-
-4. [Provide the inputs](/azure/azure-arc/system-center-virtual-machine-manager/quickstart-connect-system-center-virtual-machine-manager-to-arc#script-runtime) as prompted.
-
-5. In the same machine, run the following scripts, as applicable:
-     - [Download the script](https://download.microsoft.com/download/6/b/4/6b4a5009-fed8-46c2-b22b-b24a4d0a06e3/arcvmm-appliance-dr.ps1) if you're running the script from a Windows machine
-     - [Download the script](https://download.microsoft.com/download/0/5/c/05c2bcb8-87f8-4ead-9757-a87a0759071c/arcvmm-appliance-dr.sh) if you're running the script from a Linux machine
-
-6. Once the script is run successfully, the old Resource Bridge is recovered and the connection is re-established to the existing Azure-enabled SCVMM resources.
+4.	Once the script is run successfully, the old Resource Bridge is recovered, and the connection is re-established to the existing Azure-enabled SCVMM resources.
 
 ## Next steps