Skip to content

Commit e7a28b6

Browse files
Updated the note for deployments method.
1 parent 0e8ea9b commit e7a28b6

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

articles/migrate/migrate-appliance.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,8 +37,9 @@ The appliance can be deployed using a couple of methods:
3737
- For physical or virtualized servers on-premises or any other cloud, you always deploy the appliance using a PowerShell installer script.Refer to the steps of deployment [here](how-to-set-up-appliance-physical.md).
3838
- Download links are available in the tables below.
3939

40-
> [!Note]
41-
> Don't install any other components, such as the **Microsoft Monitoring Agent (MMA)** or **Replication appliance**, on the same server hosting the Azure Migrate appliance. If you install the MMA agent, you can face problems like **"Multiple custom attributes of the same type found"**. It's recommended to have a dedicated server to deploy the appliance.
40+
> [!Note]
41+
- Don't install any other components, such as the **Microsoft Monitoring Agent (MMA)** or **Replication appliance**, on the same server hosting the Azure Migrate appliance. If you install the MMA agent, you can face problems like **"Multiple custom attributes of the same type found"**. It's recommended to have a dedicated server to deploy the appliance.
42+
- Federal Information Processing Standards (FIPS) mode is not supported for appliance deployment.
4243

4344
## Appliance services
4445

0 commit comments

Comments
 (0)