Skip to content

Commit 053894f

Browse files
committed
Moved the note
1 parent ee90403 commit 053894f

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,10 @@ In this article, you learn how to recover the Azure Arc resource bridge connecti
1919

2020
To recover from Arc resource bridge VM deletion, you need to deploy a new resource bridge with the same resource ID as the current resource bridge using the following steps.
2121

22+
>[!Note]
23+
> This note is applicable only if you're performing this recovery operation to upgrade your Arc resource bridge.<br><br>
24+
> If you have VMs that are still in the older version, i.e., have *Enabled (Deprecated)* set under the *Virtual hardware operations* column in the Virtual Machines inventory of your SCVMM server in Azure, switch them to the new version by following the steps in [this article](./switch-to-the-new-version-scvmm.md#switch-to-the-new-version-existing-customer) before proceeding with the steps for resource bridge recovery.
25+
2226
1. Copy the Azure region and resource IDs of the Arc resource bridge, custom location, and SCVMM Azure resources.
2327

2428
2. Find and delete the old Arc resource bridge resource under the [Resource Bridges tab from the Azure Arc center](https://ms.portal.azure.com/#view/Microsoft_Azure_HybridCompute/AzureArcCenterBlade/~/resourceBridges).
@@ -54,10 +58,6 @@ To recover from Arc resource bridge VM deletion, you need to deploy a new resour
5458
5559
7. 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.
5660
57-
>[!Note]
58-
> This note is applicable only if you're performing this recovery operation to upgrade your Arc resource bridge.<br><br>
59-
> If you have VMs that are still in the older version, i.e., have *Enabled (Deprecated)* set under the *Virtual hardware operations* column in the Virtual Machines inventory of your SCVMM server in Azure, switch them to the new version by following the steps in [this article](./switch-to-the-new-version-scvmm.md#switch-to-the-new-version-existing-customer) before proceeding with the steps for resource bridge recovery.
60-
6161
## Next steps
6262
6363
[Troubleshoot Azure Arc resource bridge issues](../resource-bridge/troubleshoot-resource-bridge.md)

articles/azure-arc/system-center-virtual-machine-manager/install-arc-agents-using-script.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Ensure the following before you install Arc agents using a script for SCVMM VMs:
2929
- Is running a [supported operating system](/azure/azure-arc/servers/prerequisites#supported-operating-systems).
3030
- Is able to connect through the firewall to communicate over the Internet and [these URLs](/azure/azure-arc/servers/network-requirements?tabs=azure-cloud#urls) aren't blocked.
3131
- Has Azure CLI [installed](https://learn.microsoft.com/cli/azure/install-azure-cli).
32-
- Has the Arc agent installation downloaded from [here](https://download.microsoft.com/download/7/1/6/7164490e-6d8c-450c-8511-f8191f6ec110/arcscvmm-enable-guest-management.ps1) for a Windows VM or from [here](https://download.microsoft.com/download/0/9/b/09bd9ef4-a7af-49e5-ad5f-9e8f85fae75b/arcscvmm-enable-guest-management.sh) for a Linux VM.
32+
- Has the Arc agent installation script downloaded from [here](https://download.microsoft.com/download/7/1/6/7164490e-6d8c-450c-8511-f8191f6ec110/arcscvmm-enable-guest-management.ps1) for a Windows VM or from [here](https://download.microsoft.com/download/0/9/b/09bd9ef4-a7af-49e5-ad5f-9e8f85fae75b/arcscvmm-enable-guest-management.sh) for a Linux VM.
3333

3434
>[!NOTE]
3535
>- If you're using a Linux VM, the account must not prompt for login on sudo commands. To override the prompt, from a terminal, run `sudo visudo`, and `add <username> ALL=(ALL) NOPASSWD:ALL` at the end of the file. Ensure you replace `<username>`.

0 commit comments

Comments
 (0)