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/resources-faq.md
+2-8Lines changed: 2 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Get answers to common questions about the Azure Migrate service.
4
4
author: snehaamicrosoft
5
5
ms.service: azure-migrate
6
6
ms.topic: conceptual
7
-
ms.date: 11/19/2019
7
+
ms.date: 11/21/2019
8
8
ms.author: snehaa
9
9
---
10
10
@@ -113,17 +113,11 @@ Server Assessment provides assessment to help with migration readiness, and eval
113
113
114
114
### What's the difference between Server Assessment and the Site Recovery Deployment Planner?
115
115
116
-
Server Assessment is a migration planning tool. The Site Recovery Deployment Planner is a disaster recovery planning tool.
116
+
Server Assessment is a migration planning tool. The Site Recovery Deployment Planner is a disaster recovery planning tool.
117
117
118
118
-**Plan on-premises migration to Azure**: If you plan to migrate your on-premises servers to Azure, use Server Assessment for migration planning. It assesses on-premises workloads and provides guidance and tools to help you migrate. After the migration plan is in place, you can use tools, including Azure Migrate Server Migration, to migrate the machines to Azure.
119
119
-**Plan disaster recovery to Azure**: If you plan to set up disaster recovery from on-premises to Azure with Site Recovery, use the Site Recovery Deployment Planner. The Deployment Planner provides a deep, Site Recovery-specific assessment of your on-premises environment for the purpose of disaster recovery. It provides recommendations around disaster recovery, such as replication and failover.
120
120
121
-
### Does Azure Migrate estimate costs for the Enterprise Agreement (EA) program?
122
-
123
-
Azure Migrate Server Assessment currently doesn't support cost estimations for the [Enterprise Agreement program](https://azure.microsoft.com/offers/enterprise-agreement-support/). As a workaround, when you create an assessment, you can specify **Pay-As-You-Go** as the **Offer**, and manually add the discount percentage (applicable to the subscription) as the **Discount** in the assessment properties:
### What's the difference between as-on-premises and performance-based sizing?
128
122
129
123
With as-on-premises sizing, Azure Migrate doesn't consider VM performance data for assessment. It assesses VM sizes based on the on-premises configuration. With performance-based sizing, sizing is based on utilization data.
Copy file name to clipboardExpand all lines: articles/migrate/troubleshooting-general.md
+26-3Lines changed: 26 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: musa-57
5
5
ms.manager: abhemraj
6
6
ms.service: azure-migrate
7
7
ms.topic: conceptual
8
-
ms.date: 09/17/2019
8
+
ms.date: 11/21/2019
9
9
ms.author: hamusa
10
10
---
11
11
@@ -224,6 +224,31 @@ Error 50004: "Can't connect to a host or cluster because the server name can't b
224
224
4. Save and close the hosts file.
225
225
5. Check whether the appliance can connect to the hosts, using the appliance management app. After 30 minutes, you should see the latest information for these hosts in the Azure portal.
226
226
227
+
## Application discovery issues
228
+
229
+
Discovery of applications is currently only supported for VMware VMs. Support for Hyper-V VMs and physical servers will be enabled in future. The discovery of applications require you to provide VM credentials in the appliance. Learn more about the access privileges needed for vCenter Server and for VMware VMs. The discovery can fail due to one of the following issues, please review the recommended action as prescribed below to resolve the issue:
10000 | Unable to discover the applications installed on the server. | This could happen if the operating system running on the server is neither Windows nor Linux. | Discovery of installed applications is only supported for Windows and Linux servers.
234
+
10001 | Unable to retrieve the applications installed the server. | This is due to an internal error as there are some missing files in appliance. | Please contact Microsoft Support.
235
+
10002 | Unable to retrieve the applications installed the server. | This could happen if the discovery agent in the Azure Migrate appliance is not working properly. | The issue should automatically get resolved in 24 hours. If the issue still persists, please contact Microsoft Support.
236
+
10003 | Unable to retrieve the applications installed the server. | This could happen if the discovery agent is not working properly. | The issue should automatically get resolved in 24 hours. If the issue still persists, please contact Microsoft Support.
237
+
10004 | Unable to discover installed applications for <Windows/Linux> machines. | Credentials to access <Windows/Linux> machines were not provided in the Azure Migrate appliance | Please add a credential in the Azure Migrate appliance that has access to the <Windows/Linux> machines.
238
+
10005 | Unable to access the on-premises server. | This could happen if the credentials provided for machine to access the server is incorrect. | Please update the credentials provided in the appliance and ensure that the server is accessible using the credential.
239
+
10006 | Unable to access the on-premises server. | This could happen if the operating system running on the server is neither Windows nor Linux. | Discovery of installed applications is only supported for Windows and Linux servers.
240
+
9000 | Unable to discover the applications installed on the VM. | VMware tools might not be installed or is corrupted. | Install/Reinstall VMware tools in the VM and check if it is running.
241
+
9001 | Unable to discover the applications installed on the VM. | VMware tools might not be installed or is corrupted. | Install/Reinstall VMware tools in the VM and check if it is running.
242
+
9002 | Unable to discover the applications installed on the VM. | VMware tools might not be running. | Install/Reinstall VMware tools in the VM and check if it is running.
243
+
9003 | Unable to discover the applications installed on the server. | This could happen if the operating system running on the server is neither Windows nor Linux. | Discovery of installed applications is only supported for Windows and Linux servers.
244
+
9004 | Unable to discover the applications installed on the server. | This could happen if the VM is powered off. | To discover installed applications on the server, ensure that the VM is powered on.
245
+
9005 | Unable to discover the applications installed on the VM. | This could happen if the operating system running on the VM is neither Windows nor Linux. | Discovery of installed applications is only supported for Windows and Linux servers.
246
+
9006 | Unable to retrieve the applications installed the server. | This could happen if the discovery agent is not working properly. | The issue should automatically get resolved in 24 hours. If the issue still persists, please contact Microsoft Support.
247
+
9007 | Unable to retrieve the applications installed the server. | This could happen if the discovery agent is not working properly. | The issue should automatically get resolved in 24 hours. If the issue still persists, please contact Microsoft Support.
248
+
9008 | Unable to retrieve the applications installed the server. | The issue can occur due to an internal error. | The issue should automatically get resolved in 24 hours. If the issue still persists, please contact Microsoft Support.
249
+
9009 | Unable to retrieve the applications installed the server. | The issue can occur if the Windows User Account Control (UAC) settings on the server are restrictive and prevent discovery of installed applications. | Search for 'User Account Control' settings on the server and configure the UAC setting on the server to be at one of the lower two levels.
250
+
9010 | Unable to retrieve the applications installed the server. | The issue can occur due to an internal error. | The issue should automatically get resolved in 24 hours. If the issue still persists, please contact Microsoft Support.
251
+
8084 | Unable to discover applications due to VMware error: <ExceptionfromVMware> | The Azure Migrate appliance uses VMware APIs to discover applications. This issue can happen due to an exception thrown by vCenter Server while trying to discover applications. The fault message from VMware is displayed in the error message shown in portal. | Review the [VMware documentation](https://pubs.vmware.com/vsphere-51/topic/com.vmware.wssdk.apiref.doc/index-faults.html), search for the fault message and follow the troubleshooting steps in the VMware article to fix the issue. If you are still unable to fix the issue, reach out to Microsoft Support.
227
252
228
253
229
254
## Fix assessment readiness
@@ -316,14 +341,12 @@ Server Assessment continuously collects performance data of on-premises machines
316
341
- If you want to pick the peak usage for the period and don't want to miss any outliers, you should select the 99th percentile for percentile utilization.
317
342
318
343
319
-
320
344
## I can't find dependency visualization for Azure Government
321
345
322
346
Azure Migrate depends on Service Map for the dependency visualization functionality. Because Service Map is currently unavailable in Azure Government, this functionality is not available in Azure Government.
323
347
324
348
## Dependencies don't show after installing agents
325
349
326
-
327
350
After you've installed the dependency visualization agents on on-premises VMs, Azure Migrate typically takes 15-30 minutes to display the dependencies in the portal. If you've waited for more than 30 minutes, make sure that the Microsoft Monitoring Agent (MMA) can connect to the Log Analytics workspace.
0 commit comments