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/common-questions-discovery-assessment.md
+19-14Lines changed: 19 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,18 +27,18 @@ You can discover up to 10,000 VMware VMs, up to 5,000 Hyper-V VMs, and up to 250
27
27
28
28
The Azure Migrate appliance continuously collects information about on-premises machines, and an assessment is a point-in-time snapshot. If you change the settings on a VM that you want to assess, use the recalculate option to update the assessment with the latest changes.
29
29
30
-
###How do I discover VMs in a multitenant environment?
30
+
## How do I discover VMs in a multitenant environment?
31
31
32
32
-**VMware**: If an environment is shared across tenants, and you don't want to discover a tenant's VMs in another tenant's subscription, create vCenter Server credentials that can access only the VMs you want to discover. Then, use those credentials when you start discovery in the Azure Migrate appliance.
33
33
-**Hyper-v**: Discovery uses Hyper-V host credentials. If VMs share the same Hyper-V host, there's currently no way to separate the discovery.
34
34
35
35
36
-
###Do I need vCenter Server for VMWare VM discovery?
36
+
## Do I need vCenter Server?
37
37
38
38
Yes, Azure Migrate needs vCenter Server to perform discovery in a VMware environment. It doesn't support discovery of ESXi hosts that aren't managed by vCenter Server.
39
39
40
40
41
-
## What's the difference sizing options?
41
+
## What's are the sizing options?
42
42
43
43
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.
44
44
@@ -72,7 +72,9 @@ Use dependency visualization to assess groups of VMs for migration with greater
72
72
> [!NOTE]
73
73
> Dependency visualization isn't available in Azure Government.
74
74
75
-
## What's the difference between agent-based and agentless visualization?
75
+
## What's the difference between agent-based and agentless?
76
+
77
+
The differences between agentless visualization and agent-based visualization are summarized in the table.
- If you have machines with no internet connectivity, you need to download and install Log Analytics gateway on them.
102
104
103
-
You don't need these agents unless you're using dependency visualization.
105
+
You don't need these agents unless you're using agent-based dependency visualization.
104
106
105
107
## Can I use an existing workspace?
106
108
107
-
Yes, you can attach an existing workspace to the migration project and use it for dependency visualization.
109
+
Yes, for agent-based dependency visualization you can attach an existing workspace to the migration project and use it for dependency visualization.
108
110
109
111
## Can I export the dependency visualization report?
110
112
111
-
No, the dependency visualization can't be exported. However, Azure Migrate uses Service Map, and you can use the [Service Map REST API](https://docs.microsoft.com/rest/api/servicemap/machines/listconnections) to retrieve the dependencies in JSON format.
112
-
113
-
## Can I automate MMA/Dependency agent installation?
113
+
No, the dependency visualization report in agent-based visualization can't be exported. However, Azure Migrate uses Service Map, and you can use the [Service Map REST API](https://docs.microsoft.com/rest/api/servicemap/machines/listconnections) to retrieve the dependencies in JSON format.
114
114
115
-
Use this [script to install the Dependency agent](../azure-monitor/insights/vminsights-enable-hybrid-cloud.md#installation-script-examples). Follow these [instructions to install MMA](../azure-monitor/platform/log-analytics-agent.md#installation-and-configuration) by using the command line or automation. For
116
-
MMA, use [this script](https://gallery.technet.microsoft.com/scriptcenter/Install-OMS-Agent-with-2c9c99ab).
115
+
## Can I automate agent installation?
116
+
For agent-based dependency visualization, automate as follows:
117
117
118
-
In addition to scripts, you can also use deployment tools like Microsoft Endpoint Configuration Manager and [Intigua](https://www.intigua.com/getting-started-intigua-for-azure-migration) to deploy the agents.
118
+
- Use this [script to install the Dependency agent](../azure-monitor/insights/vminsights-enable-hybrid-cloud.md#installation-script-examples).
119
+
- For MMA, follow these [instructions](../azure-monitor/platform/log-analytics-agent.md#installation-and-configuration) to use the command line or automation, or use [this script](https://gallery.technet.microsoft.com/scriptcenter/Install-OMS-Agent-with-2c9c99ab).
120
+
- In addition to scripts, you can also use deployment tools like Microsoft Endpoint Configuration Manager and [Intigua](https://www.intigua.com/getting-started-intigua-for-azure-migration) to deploy the agents.
119
121
120
122
121
123
## What operating systems does MMA support?
@@ -124,7 +126,10 @@ In addition to scripts, you can also use deployment tools like Microsoft Endpoin
124
126
- View the list of [Linux operating systems supported by MMA](https://docs.microsoft.com/azure/log-analytics/log-analytics-concept-hybrid#supported-linux-operating-systems).
125
127
126
128
## Can I visualize dependencies for more than an hour?
127
-
No. You can visualize dependencies for up to an hour. You can go back to a particular date in history, as far back as a month, but the maximum duration for visualization is an hour. For example, you can use the time duration in the dependency map to view dependencies for yesterday, but you can view dependencies for a one-hour window only. However, you can use Azure Monitor logs to [query dependency data](https://docs.microsoft.com/azure/migrate/how-to-create-group-machine-dependencies) over a longer duration.
129
+
For agent-based visualization, you can visualize dependencies for up to an hour. You can go back to a particular date in history, as far back as a month, but the maximum duration for visualization is an hour. For example, you can use the time duration in the dependency map to view dependencies for yesterday, but you can view dependencies for a one-hour window only. However, you can use Azure Monitor logs to [query dependency data](https://docs.microsoft.com/azure/migrate/how-to-create-group-machine-dependencies) over a longer duration.
130
+
131
+
For agentless visualization, you can view the dependency map of a single server from a duration of one hour to 30 days.
132
+
128
133
129
134
## Can visualize dependencies for groups of more than 10 VMs?
130
135
You can [visualize dependencies](https://docs.microsoft.com/azure/migrate/how-to-create-group-dependencies) for groups containing up to 10 VMs. If you have a group with more than 10 VMs, we recommend that you split the group into smaller groups, and then visualize the dependencies.
0 commit comments