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/migrate-appliance.md
+47-1Lines changed: 47 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,12 +35,58 @@ The appliance can be deployed using a couple of methods:
35
35
- If you don't want to use a template, you can deploy the appliance for VMware or Hyper-V environment using a [PowerShell installer script](deploy-appliance-script.md).
36
36
- In Azure Government, you should deploy the appliance using a PowerShell installer script. Refer to the steps of deployment [here](deploy-appliance-script-government.md).
37
37
- 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).
38
-
- Download links are available in the tables below.
38
+
39
39
40
40
> [!Note]
41
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
42
> - Federal Information Processing Standards (FIPS) mode is not supported for appliance deployment.
43
43
44
+
## Verify security
45
+
46
+
Before you use the OVA/VHD/Zip file to deploy appliance, verify that the file is secure:
47
+
48
+
1. On the server where you downloaded the file, open Command Prompt window by using **Run as administrator** option.
49
+
1. Run this command to create the hash for the OVA/VHD/Zip file:
0 commit comments