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/how-to-create-group-machine-dependencies-agentless.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,13 +83,13 @@ On reviewing the **Dependencies** column for any server, you see one of the foll
83
83
84
84
1.**Credentials not available:** when no server credentials provided on the appliance configuration manager can be used to perform dependency analysis
85
85
2.**Validation in progress:** when the prerequisite validation checks have still not been completed on the server
86
-
3.**Validation failed:** when the validation checks on the server have failed. You can select the status to review error message which would mostly be related to missing prerequisites like insufficient credential permissions or invalid credentials etc.
86
+
3.**Validation failed:** when the validation checks on the server have failed. You can select the status to review error message which would mostly be related to missing prerequisites like insufficient credential permissions or invalid credentials etc.
87
87
88
88
After the validation succeeds, dependency analysis are auto-enabled and you see one of the following status:
89
89
90
-
4.**View dependencies:** when validation checks have passed and the dependency analysis has been enabled. You can select this to go to the new visualization and review dependencies for this server.
91
-
5.**Not initiated:** when dependency analysis couldn't be enabled as Azure Migrate has reached the scale limit of 1,000 servers per appliance for auto-enablement. If you want to perform dependency analysis on the specific servers, you can manually disable it on the other auto-enabled servers and enable for the ones you need by using the PowerShell module.
92
-
6.**Disabled:** when dependency analysis has been manually disabled by you on this server using the PowerShell module. You can re-enable it any-time using the same PowerShell module.
90
+
-**View dependencies:** when validation checks have passed and the dependency analysis has been enabled. You can select this to go to the new visualization and review dependencies for this server.
91
+
-**Not initiated:** when dependency analysis couldn't be enabled as Azure Migrate has reached the scale limit of 1,000 servers per appliance for auto-enablement. If you want to perform dependency analysis on the specific servers, you can manually disable it on the other auto-enabled servers and enable for the ones you need by using the PowerShell module.
92
+
-**Disabled:** when dependency analysis has been manually disabled by you on this server using the PowerShell module. You can re-enable it any-time using the same PowerShell module.
93
93
94
94
## Visualize dependencies
95
95
::: moniker range="migrate-classic"
@@ -196,7 +196,7 @@ If you're an existing user who has already set up an Azure Migrate project, perf
196
196
:::image type="content" source="./media/how-to-create-group-machine-dependencies-agentless/old-dep-view.png" alt-text="The screenshot shows the old dependency view." lightbox="./media/how-to-create-group-machine-dependencies-agentless/old-dep-view.png":::
197
197
198
198
3. On the dependency view, you see an information box prompting you to complete some prerequisites for switching to the new visualization.
199
-
4. As a prerequisite, you need to ensure that the discovery agent on the appliances registered with the project have been upgraded to version <> or above.
199
+
4. As a prerequisite, you need to ensure that the discovery agent on the appliances registered with the project have been upgraded to version or above.
200
200
5. Select proceed to create a new resource in the same Resource Group as the project. Ensure that you've atleast **Contributor** role on the Resource Group else this step isn't complete.
Copy file name to clipboardExpand all lines: articles/migrate/how-to-review-discovered-inventory.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
@@ -1,6 +1,6 @@
1
1
---
2
-
title: Review discovered inventory (preview) in Azure Migrate.
3
-
description: This article describes on how to review discovered inventory across All inventory, Infrastructure, Databases, and web application inventory views.
2
+
title: Review discovered inventory (preview) in Azure Migrate
3
+
description: This article describes how to review discovered inventory across All inventory, Infrastructure, Databases, and web application inventory views.
0 commit comments