Skip to content

Commit 59e0d8a

Browse files
committed
link updates
1 parent 48abdb4 commit 59e0d8a

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/migrate/tutorial-discover-aws.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -83,8 +83,8 @@ If you just created a free Azure account, you're the owner of your subscription.
8383

8484
Set up an account that the appliance can use to access AWS instances.
8585

86-
- For **Windows servers**, set up a local user account on all the Windows servers that you want to include in the discovery. Add the user account to the following groups: - Remote Management Users - Performance Monitor Users - Performance Log users.
87-
- For **Linux servers**, you need a root account on the Linux servers that you want to discover. Refer to the instructions in the [support matrix](migrate-support-matrix-physical.md#permissions-for-linux-server) for an alternative.
86+
- For **Windows servers**, set up a local user account on all the Windows servers that you want to include in the discovery. Add the user account to the following groups: - Remote Management Users - Performance Monitor Users - Performance Log users. Refer the [instructions](tutorial-discover-physical.md#prepare-windows-server).
87+
- For **Linux servers**, you need a root account on the Linux servers that you want to discover. Refer the [instructions](tutorial-discover-physical.md#prepare-linux-server).
8888
- Azure Migrate uses password authentication when discovering AWS instances. AWS instances don't support password authentication by default. Before you can discover instance, you need to enable password authentication.
8989
- For Windows servers, allow WinRM port 5985 (HTTP). This allows remote WMI calls.
9090
- For Linux servers:

articles/migrate/tutorial-discover-gcp.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -87,9 +87,9 @@ Set up an account that the appliance can use to access servers on GCP.
8787
* Set up a local user account on non-domain joined servers, and a domain account on domain joined servers that you want to include in the discovery. Add the user account to the following groups:
8888
* Remote Management Users
8989
* Performance Monitor Users
90-
* Performance Log users.
90+
* Performance Log users. Refer the [instructions](tutorial-discover-physical.md#prepare-windows-server).
9191
* For **Linux servers**:
92-
* You need a root account on the Linux servers that you want to discover. If you aren't able to provide a root account, refer to the instructions in the [support matrix](migrate-support-matrix-physical.md#permissions-for-linux-server) for an alternative.
92+
* You need a root account on the Linux servers that you want to discover. If you aren't able to provide a root account. Refer the [instructions](tutorial-discover-physical.md#prepare-linux-server).
9393
* Azure Migrate uses password authentication when discovering GCP instances. GCP instances don't support password authentication by default. Before you can discover instance, you need to enable password authentication.
9494
1. Sign into each Linux machine.
9595
2. Open the sshd_config file: vi /etc/ssh/sshd_config

0 commit comments

Comments
 (0)