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
Copy file name to clipboardExpand all lines: articles/migrate/troubleshoot-appliance-diagnostic.md
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,15 +6,15 @@ ms.author: vibansa
6
6
ms.manager: abhemraj
7
7
ms.service: azure-migrate
8
8
ms.topic: troubleshooting
9
-
ms.date: 07/11/2023
10
-
ms.custom: engagement-fy24
9
+
ms.date: 10/11/2023
10
+
ms.custom: engagement-fy25
11
11
---
12
12
13
13
# Diagnose and solve issues with Azure Migrate appliance
14
14
15
15
The **Diagnose and solve** capability on Azure Migrate appliance helps users identify and self-assess any issues with the appliance configuration that might be blocking the initiation of discovery or issues with an ongoing Migrate operation like discovery, assessment and/or replication (*in case of VMware appliance*) from the appliance.
16
16
17
-
You can run **Diagnose and solve** at any time from the appliance configuration manager to generate a diagnostics report. The report provides information about the checks performed, their status, the issues identified and recommendation steps to solve the issues.
17
+
You can run **Diagnose and solve** at any time from the appliance configuration manager to generate a diagnostics report. The report provides information about the checks performed, their status, the issues identified, and recommendation steps to solve the issues.
18
18
19
19
> [!IMPORTANT]
20
20
> **Diagnose and solve** capability is currently in preview for Azure Migrate appliance.
@@ -24,30 +24,30 @@ You can run **Diagnose and solve** at any time from the appliance configuration
24
24
25
25
## Diagnostic checks
26
26
27
-
*Diagnose and solve* runs some pre-validations to see if the required configuration files aren't missing or blocked by an anti-virus software on the appliance and then performs the following checks:
27
+
*Diagnose and solve* runs some prevalidations to see if the required configuration files aren't missing or blocked by an anti-virus software on the appliance and then performs the following checks:
**Prerequisite checks** | Connectivity checks | Checks if the appliance has connectivity to Azure either directly or via proxy.
32
32
|| Time sync check | Checks if the appliance server time is in sync with network time.
33
-
|| Auto update check | Checks if auto-update is enabled and if all agents running on the appliance are up to date.
34
-
||VDDK check | Checks if the required VDDK files have been downloaded and copied at the required location on the appliance server.
35
-
**Service health checks** |Operational status |Checks if the agents on the appliance are in running state. <br>*If not, appliance will auto-resolve by restarting the agents.*
33
+
|| Auto update check | Checks if autoupdate is enabled and if all agents running on the appliance are up to date.
34
+
||VDDK check | Checks if the required VDDK files are downloaded and copied at the required location on the appliance server.
35
+
**Service health checks** |Operational status |Checks if the agents on the appliance are in running state. <br>*If not, appliance autoresolves by restarting the agents.*
36
36
||Service endpoint connectivity |Checks if the agents can communicate to their respective services on Azure either directly or via proxy.
37
37
**Azure-specific checks** |Microsoft Entra App availability* | Checks if the Microsoft Entra App created during the appliance registration is available and is accessible from the appliance.
38
-
||Migrate project availability* | Checks if the Migrate project to which the appliance has been registered still exists and is accessible from the appliance.
38
+
||Migrate project availability* | Checks if the Migrate project to which the appliance is registered still exists and is accessible from the appliance.
39
39
||Essential resources availability*| Checks if the Migrate resources created during appliance registration still exist and are accessible from the appliance.
40
-
**Appliance-specific checks** | Key Vault certificate availability* | Checks if the certificate downloaded from Key Vault during appliance registration is still available on the appliance server. <br> *If not, appliance will auto-resolve by downloading the certificate again, provided the Key Vault is available and accessible*.
41
-
|| Credential store availability | Checks if the Credential store resources on the appliance server haven't been moved/deleted/edited.
42
-
|| Replication appliance/ASR components | Checks if the same server has also been used to install any ASR/replication appliance components. *It is currently not supported to install both Azure Migrate and replication appliance (for agent-based migration) on the same server.*
40
+
**Appliance-specific checks** | Key Vault certificate availability* | Checks if the certificate downloaded from Key Vault during appliance registration is still available on the appliance server. <br> *If not, appliance autoresolves by downloading the certificate again, provided the Key Vault is available and accessible*.
41
+
|| Credential store availability | Checks if the Credential store resources on the appliance server aren't moved/deleted/edited.
42
+
|| Replication appliance/Azure Site Recovery components | Checks if the same server is also used to install any Azure Site Recovery/replication appliance components. *Installation of both Azure Migrate and replication appliance (for agent-based migration) on the same server is not supported.*
43
43
|| OS license availability | Checks if the evaluation license on the appliance server created from OVA/VHD is still valid. *The Windows Server 2022 evaluation license is valid for 180 days.*
44
44
|| CPU & memory utilization | Checks the CPU and memory utilized by the Migrate agents on the appliance server.
45
45
46
-
**checked and reported only if the appliance has already been registered. These checks are run in the context of the current Azure user logged in the appliance*.
46
+
**checked and reported only if the appliance is already registered. These checks are run in the context of the current Azure user logged in the appliance*.
47
47
48
48
## Running diagnostic checks
49
49
50
-
If you're getting any issues with the appliance during its configuration or seeing issues with the ongoing Migrate operations like discovery, assessment and/or replication (*in case of VMware appliance*) on the portal, you can go to the appliance configuration manager and run diagnostics.
50
+
If you're getting any issues with the appliance during its configuration or seeing issues with the ongoing Migrate operations like discovery, assessment, and/or replication (*for VMware appliance*) on the portal, you can go to the appliance configuration manager and run diagnostics.
51
51
52
52
> [!NOTE]
53
53
> Currently **Diagnose and solve** can perform checks related to appliance connectivity to Azure, availability of required resources on appliance server and/or Azure. The connectivity or discovery issues with the source environment like vCenter Server/ESXi hosts/Hyper-V hosts/VMs/physical servers are currently not covered under **Diagnose and solve**.
@@ -56,12 +56,12 @@ If you're getting any issues with the appliance during its configuration or seei
56
56
57
57
58
58
59
-
After selecting **Diagnose and solve**, the appliance automatically starts running the diagnostic checks. This may take around 5 minutes to complete.
59
+
After selecting **Diagnose and solve**, the appliance automatically starts running the diagnostic checks. This can take around 5 minutes to complete.
60
60
*You would see the timestamp of the last diagnostics report, if you ran the checks before.*
1. Once diagnostic checks have completed, you can either view the report in another tab where you can choose it save it in a PDF format or you can go to this location **C:\Users\Public\Desktop\DiagnosticsReport** on the appliance server where the report gets auto-saved in an HTML format.
64
+
1. Once diagnostic checks complete, you can either view the report in another tab where you can choose it save it in a PDF format or you can go to this location **C:\Users\Public\Desktop\DiagnosticsReport** on the appliance server where the report gets autosaved in an HTML format.
Copy file name to clipboardExpand all lines: articles/migrate/troubleshoot-upgrade.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,8 +5,8 @@ author: AnuragMehrotra
5
5
ms.author: anuragm
6
6
ms.service: azure-migrate
7
7
ms.topic: conceptual
8
-
ms.date: 07/11/2023
9
-
ms.custom: engagement-fy24
8
+
ms.date: 09/07/2023
9
+
ms.custom: engagement-fy25
10
10
---
11
11
12
12
# Troubleshoot Windows OS upgrade issues
@@ -15,7 +15,7 @@ This article describes some common issues that you might encounter when you up
15
15
16
16
## Cannot attach the OS setup disk as VM reached maximum disk allowed
17
17
18
-
The Test Migration and Migration will fail in the prerequisite stage if the VM already has the maximum number of data disks based on its SKU. Since the workflow creates an additional data disk temporarily, it's mandatory to have n-1 (n represents maximum number of disks supported for the respective SKU of the VM) disks to complete the upgrade successfully.
18
+
The Test Migration and Migration fails in the prerequisite stage if the VM already has the maximum number of data disks based on its SKU. Since the workflow creates an additional data disk temporarily, it's mandatory to have n-1 (n represents maximum number of disks supported for the respective SKU of the VM) disks to complete the upgrade successfully.
19
19
20
20
### Recommended action
21
21
@@ -36,17 +36,17 @@ Select a different target Azure VM SKU that can attach more data disks and retry
36
36
37
37
## Migration fails for Private endpoint enabled Azure Migrate projects
38
38
39
-
The migration fails if the storage account that you select for replicating VMs doesn't have the Firewall settings of the target VNET.
39
+
The migration fails if the storage account that you select for replicating VMs doesn't have the Firewall settings of the target virtual network.
40
40
41
41
### Recommended action
42
42
43
-
Add the target VNET into the firewall in the storage account that you select in the above step for replicating VMs:
43
+
Add the target virtual network into the firewall in the storage account that you select in the above step for replicating VMs:
44
44
45
-
1. Go to **Networking** > **Firewall and Virtual Networks** > **Public Network Access – Enabled from selected Virtual Network and IP address** > **Virtual Network** > Add existing Virtual Network and add your target VNET. Then proceed with the Test Migration/Migration.
45
+
1. Go to **Networking** > **Firewall and Virtual Networks** > **Public Network Access – Enabled from selected Virtual Network and IP address** > **Virtual Network** > Add existing Virtual Network and add your target virtual network. Then proceed with the Test Migration/Migration.
46
46
47
47
2. Perform the initial replication by following [these](migrate-servers-to-azure-using-private-link.md?pivots=agentlessvmware#replicate-vms) steps.
48
48
49
-
## Server is migrated without OS upgrade with status “Completed with errors”
49
+
## Server is migrated without OS upgrade with status "Completed with errors"
50
50
51
51
If the source OS version and the OS version to be upgraded are the same, the server migrates without an OS upgrade with the status **Completed with errors**. For example, if the source OS version is Windows 2019 and the upgrade option selected is Windows 2019, then the server is migrated without an OS upgrade with the status **Completed with errors**.
0 commit comments