You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can install extensions from the **Capabilities** tab for your Azure Local Arc-enabled servers, as shown in the screenshot. You can use the capabilities tab to install most extensions.
43
+
You can use the **Capabilities** tab to install extensions for your Azure Local Arc-enabled servers, as shown in the screenshot. You can use this tab to install most extensions.
44
44
45
45
:::image type="content" source="media/arc-extension-management/arc-extension-overview.png" alt-text="Screenshot of the Capabilities tab and options in the Azure portal." lightbox="media/arc-extension-management/arc-extension-overview.png":::
46
46
@@ -149,7 +149,7 @@ Launch [Azure Cloud Shell](https://shell.azure.com/) and use Bash to install an
149
149
150
150
### [Azure PowerShell](#tab/azurepowershell)
151
151
152
-
Run Azure PowerShell in Azure Cloud Shell. This article details how to use PowerShell in Azure Cloud Shell. For more information, see [Quickstart for Azure Cloud Shell](/azure/cloud-shell/quickstart).
152
+
Run Azure PowerShell in Azure Cloud Shell. For more information, see [Quickstart for Azure Cloud Shell](/azure/cloud-shell/quickstart).
153
153
154
154
Launch [Azure Cloud Shell](https://shell.azure.com/) and use PowerShell to install an extension by following these steps:
155
155
@@ -308,7 +308,7 @@ Launch [Azure Cloud Shell](https://shell.azure.com/) and use Bash to check the s
308
308
309
309
### [Azure PowerShell](#tab/azurepowershell)
310
310
311
-
Azure PowerShell can be run in Azure Cloud Shell. This document details how to use PowerShell in Azure Cloud Shell. For more information, refer [Quickstart for Azure Cloud Shell](/azure/cloud-shell/quickstart).
311
+
Azure PowerShell can be run in Azure Cloud Shell. For more information, see [Quickstart for Azure Cloud Shell](/azure/cloud-shell/quickstart).
312
312
313
313
Launch [Azure Cloud Shell](https://shell.azure.com/) and use PowerShell to check the status of an extension by following these steps:
Copy file name to clipboardExpand all lines: azure-local/manage/get-remote-support.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ After you enable remote support, Microsoft support gets just-in-time (JIT) limit
25
25
26
26
## Remote support terms and conditions
27
27
28
-
The following are the data handling terms and conditions for remote access. Carefully read them before granting access. Everything under this section should remain as is without making any changes to the text.
28
+
The following are the data handling terms and conditions for remote access. Carefully read them before granting access. <!--Everything under this section should remain as is without making any changes to the text.-->
29
29
30
30
> By approving this request, the Microsoft support organization or the Azure engineering team supporting this feature ("Microsoft Support Engineer") will be given direct access to your device for troubleshooting purposes and/or resolving the technical issue described in the Microsoft support case.
Copy file name to clipboardExpand all lines: azure-local/migrate/migrate-hyperv-prerequisites.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Prerequisites for Hyper-V VM migration to Azure Local using Azure Migrate
3
3
description: Learn prerequisites for Hyper-V migration to Azure Local using Azure Migrate (preview).
4
4
author: alkohli
5
5
ms.topic: how-to
6
-
ms.date: 05/14/2025
6
+
ms.date: 07/25/2025
7
7
ms.author: alkohli
8
8
---
9
9
@@ -23,7 +23,7 @@ The following list contains the prerequisites that must be met to migrate Hyper-
23
23
|--|--|--|
24
24
|Open required firewall ports.|source, target|**3389** – Inbound connections on port 3389 to allow remote desktop connections to the appliance. <br> **44368** – Inbound connections on port 44368 to remotely access the appliance management app by using the URL: *https:\//\<appliance-ip-or-name\>:44368*. <br> **5985, 5986** – Inbound and outbound connections on port 5985 (WinRM) to communicate from appliance to host. <br> **445** – Inbound and outbound connections on port 445 (SMB) to communicate between source and target appliance.|
|Configure SAN policy on Windows VMs.|source|[Configure SAN policy](/azure/migrate/prepare-for-migration#configure-san-policy).|
26
+
|Configure SAN/disks policy on VMs.|source|[Configure SAN/disks policy](migrate-troubleshoot.md#disks-on-migrated-vms-are-offline).|
27
27
|Deploy, configure and register an Azure Local instance.|target|[Create and register an Azure Local instance](../deploy/deployment-introduction.md).|
28
28
| Verify a successful deployment. | target |[Verify a successful deployment](../deploy/deploy-via-portal.md#verify-a-successful-deployment). |
29
29
|Verify and make a note of the custom location created during deployment on Azure Local.|target|[Verify a successful deployment](../deploy/deploy-via-portal.md#verify-a-successful-deployment).|
C:\>Get-FileHash -Path <Path to downloaded VHD zip> -Algorithm SHA256
109
104
```
110
105
111
-
1. Verify the latest appliance versions and hash values for Azure public cloud:
112
-
106
+
1. Verify the latest appliance versions and hash values:
113
107
114
108
|**Scenario** |**Download** |**SHA256** |
115
109
|---------|---------|---------|
116
110
|Azure Local appliance |Latest version: `https://go.microsoft.com/fwlink/?linkid=2246416` |6ae1144b026efb2650f5e11c007a457c351a752f942c2db827dd2903f468dccb |
117
111
118
-
119
-
1. Extract the zip file to a folder.
112
+
1. Extract the zipped file to a folder.
120
113
121
114
Now you can install the appliance using the .VHD file.
122
115
123
-
1. On a Hyper-V server (this could be your source server), go to the Hyper-V Manager. Select **Hyper-V Manager > Connect to server**.
124
-
125
-
1. On the **Select Computer** dialog box, select **Another computer**. Browse to the Azure Local machine, and then select **OK**.
126
-
127
-
1. Map the drive on your Azure Local machine where you downloaded the VHD. Connect to this drive using File Explorer. Verify that you can access the location where the VHD was downloaded on your Azure Local machine.
128
-
129
-
1. On your Hyper-V server, from the **Actions** pane, select **Import Virtual Machine**. This starts a wizard. Go through the steps of the wizard. Accept the defaults except on the following:
116
+
1. Using local tools, such as Hyper-V Manager or Failover Cluster, install the target appliance from the downloaded .VHD file on your Azure Local instance.
130
117
131
-
1. On the **Locate Folder** page, point to the folder that has the VHD (folder name is AzureMigrateAppliance.zip) that you downloaded on your Azure Local machine.
132
-
1. On the **Connect Network** page, select a switch from the dropdown list for **Connection**. Create a VM using the VHD you downloaded, then start and sign into the VM. Make sure the VM has access to the internet.
133
-
1. Finally review the settings and select **Finish**.
134
-
135
-
1. In the Hyper-V Manager, under **Virtual Machines**, you see the VM your created. Select and start the VM.
136
-
137
-
1. Once the VM starts, accept the license terms and conditions. On the **Customize settings** page, provide and confirm a password for the administrator account and then select **Finish**.
138
-
139
-
1. After the VM has started up, sign in to the VM as an administrator. Enter the password you provided in the previous step.
140
-
141
-
1. Open **Azure Migrate Target Appliance Configuration Manager** shortcut from the desktop.
118
+
1. Once the VM has finished provisioning and has booted, open the **Azure Migrate Target Appliance Configuration Manager** shortcut from the desktop.
142
119
143
120
#### Install using a script (.zip file)
144
121
145
-
This step applies only if you downloaded the .zip file.
146
-
147
-
1. Using **Hyper-V Manager**, create a standalone (non-HA) VM on the target Azure Local machine running on Windows Server 2022 with 80 GB (min) disk storage, 16 GB (min) memory, and 8 virtual processors. Make sure that the VM has access to the internet.
122
+
This step applies to using a .zip file.
148
123
149
-
1. In **Hyper-V Manager**, select the host.
124
+
1. Create a VM in Azure Local with the following configuration:
125
+
- Operating system: Windows Server 2022
126
+
- vCPU: 8
127
+
- Disk: >80 GB
128
+
- Memory: 16 GB
150
129
151
-
1. Under **Hyper-V settings**, select **Enhanced Session Mode Policy** and ensure **Allow enhanced session mode** is enabled. For more information, see [Turn on enhanced session mode on a Hyper-V host](/windows-server/virtualization/hyper-v/learn-more/use-local-resources-on-hyper-v-virtual-machine-with-vmconnect#turn-on-enhanced-session-mode-on-a-hyper-v-host).
130
+
1. Once the VM is created, sign into the VM as an administrator.
152
131
153
-
1. Sign into the VM as an administrator.
132
+
1. You can download the appliance from a .zip file. Under **Step 2: Download and install the target appliance**, select **.zip**, and then select **Download**.
154
133
155
-
1. Copy and paste the downloaded .zip file to the VM virtual disk that you created and extract it as needed.
134
+
1. Copy the downloaded zip file to the new VM that you created on the Azure Local instance. Extract the zip to a folder and go where the `AzureMigrateInstaller.ps1` PowerShell script resides in the extracted folder.
156
135
157
-
1. As an administrator, run the following PowerShell script from the folder of the extracted files to install the target appliance:
136
+
1. Open a PowerShell window as an administrator and run the following:
158
137
159
-
```PowerShell
160
-
Set-ExecutionPolicy -ExecutionPolicy Unrestricted
138
+
```powershell
139
+
Set-ExecutionPolicy -ExecutionPolicy Unrestricted
161
140
.\AzureMigrateInstaller.ps1 -Scenario AzureStackHCI -Cloud Public -PrivateEndpoint:$false
162
-
```
141
+
```
163
142
164
-
1. Restart and sign into the VM.
143
+
1. Restart the VM after the installation is complete. Sign in to the VM.
Copy file name to clipboardExpand all lines: azure-local/migrate/migrate-troubleshoot.md
+22-6Lines changed: 22 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Troubleshoot issues when migrating VMs to Azure Local using Azure Migrate
3
3
description: Learn about how to troubleshoot issues when migrating Windows VMs to your Azure Local instance using Azure Migrate (preview).
4
4
author: alkohli
5
5
ms.topic: how-to
6
-
ms.date: 07/10/2025
6
+
ms.date: 07/25/2025
7
7
ms.author: alkohli
8
8
ms.reviewer: alkohli
9
9
ms.custom: linux-related-content
@@ -283,17 +283,33 @@ The component fails to fetch the disk properties from the source Hyper-V host. T
283
283
284
284
**Root cause**
285
285
286
-
The disks on the migrated Windows VMs may not come online.
286
+
The disks on the migrated Windows VMs and Linux VMs may not come online.
287
287
288
-
Migration creates a new VHD/VHDX, which results in a new disk for the Windows OS on the migrated VM. The OS sees this as a new drive and applies SAN policy. The OS will then not make the disk online as it is considered a shared disk.
288
+
Migration creates a new VHD/VHDX, which results in a new disk for the OS on the migrated VM.
289
+
290
+
For Windows VMs, the OS sees this as a new drive and applies storage area network (SAN) policy. The OS will then not make the disk online as it is considered a shared disk.
289
291
290
292
**Recommended resolution**
291
293
292
-
To work around this issue, choose one of the following options:
294
+
**For Windows VMs**
295
+
296
+
To ensure that all migrated disks come online, set the SAN policy to **OnlineAll**.
297
+
298
+
Configure this setting manually as follows:
299
+
300
+
1. On the on-premises virtual machine (not the host server) prior to migration, open an elevated command prompt.
301
+
302
+
1. Enter **diskpart**.
303
+
304
+
1. Enter **SAN**. If the drive letter of the guest operating system isn't maintained, **Offline All** or **Offline Shared** is returned.
305
+
306
+
1. At the **DISKPART** prompt, enter **SAN Policy=OnlineAll**. This setting ensures that disks are brought online, and it ensures that you can read and write to both disks.
307
+
308
+
1. During migration, you can verify that the disks are brought online.
293
309
294
-
- Set SAN policy as `OnlineAll` for migrated Windows VMs. Reboot the VMs. This should bring all the disks online. For detailed instructions, see how to [Configure a SAN policy to bring disks online](/azure/migrate/prepare-for-migration#configure-san-policy).
310
+
**For Linux VMs**
295
311
296
-
- Manually bring the drives online on migrated VMs.
312
+
Update **fstab** entries to use persistent volume identifiers prior to migration.
297
313
298
314
### Migration fails with unable to delete snapshot error
Copy file name to clipboardExpand all lines: azure-local/migrate/migrate-vmware-prerequisites.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Prerequisites for VMware VM migration to Azure Local using Azure Migrate
3
3
description: Learn prerequisites for VMware migration to Azure Local using Azure Migrate (preview).
4
4
author: alkohli
5
5
ms.topic: how-to
6
-
ms.date: 05/14/2025
6
+
ms.date: 07/25/2025
7
7
ms.author: alkohli
8
8
---
9
9
@@ -24,7 +24,7 @@ The following list contains the prerequisites that must be met to migrate VMware
24
24
|Open required VMware firewall ports.|source|**3389** – Inbound connections on port 3389 to allow remote desktop connections to the appliance. <br> **44368** – Inbound connections on port 44368 to remotely access the appliance management app by using the URL: *https:\//\<appliance-ip-or-name\>:44368*. <br> **443** – Inbound and outbound connections on port 443 to communicate with Azure Migrate services orchestrating replication and migration, and to allow the appliance to communicate with vCenter Server. <br> **902** – Inbound and outbound connections on port 902 for the appliance to replicate data from snapshots of ESXi hosts and send heartbeat traffic to vCenter. <br> **445** – Inbound and outbound connections on port 445 (SMB) to communicate between source and target appliance.|
25
25
|Open required Hyper-V firewall ports.|target|**3389** – Inbound connections on port 3389 to allow remote desktop connections to the appliance. <br> **44368** – Inbound connections on port 44368 to remotely access the appliance management app by using the URL: *https:\//\<appliance-ip-or-name\>:44368*. <br> **445** – Inbound and outbound connections on port 445 (SMB) to communicate between source and target appliance. <br> **5985, 5986** – Inbound and outbound connections on port 5985 (WinRM) to communicate from appliance to host.|
|Configure SAN policy on VMware VMs.|source|[Configure SAN policy](/azure/migrate/prepare-for-migration#configure-san-policy).|
27
+
|Configure SAN/disks policy on VMs.|source|[Configure SAN/disks policy](migrate-troubleshoot.md#disks-on-migrated-vms-are-offline).|
28
28
|Deploy, configure, and register an Azure Local instance.|target|[Create and register an Azure Local instance](../deploy/deployment-introduction.md).|
29
29
| Verify a successful deployment. | target |[Verify a successful deployment](../deploy/deploy-via-portal.md#verify-a-successful-deployment). |
30
30
|Verify and make a note of the custom location created during deployment on the Azure Local system.|target|[Verify a successful deployment](../deploy/deploy-via-portal.md#verify-a-successful-deployment).|
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments