Change to Hash values for scripts

Author: Vikram1988

articles/migrate/common-questions-appliance.md

@@ -16,7 +16,7 @@ This article answers common questions about the Azure Migrate appliance. If you
 
 ## What is the Azure Migrate appliance?
 
-The Azure Migrate appliance is a lightweight appliance that the Azure Migrate: Server Assessment tool uses to discover and assess on-premises servers. The Azure Migrate: Server Migration tool also uses the appliance for agentless migration of on-premises VMware VMs.
+The Azure Migrate appliance is a lightweight appliance that the Azure Migrate: Server Assessment tool uses to discover and assess physical or virtual servers from on-premises or any cloud. The Azure Migrate: Server Migration tool also uses the appliance for agentless migration of on-premises VMware VMs.
 
 Here's more information about the Azure Migrate appliance:
 
@@ -30,13 +30,14 @@ Here's more information about the Azure Migrate appliance:
 
 The appliance can be deployed as follows:
 
-- Using a template for VMware VMs and Hyper-V VMs (OVA template for VMware or VHD for Hyper-V).
-- If you don't want to use a template, or you're in Azure Government, you can deploy the appliance for VMware or Hyper-V using a PowerShell script.
-- For physical servers, you always deploy the appliance using a script.
+- Using a template for discovery of VMware VMs (.OVA file) and Hyper-V VMs (.VHD file) to create a new VM which hosts the appliance.
+- If you don't want to use a template, you can deploy the appliance on an existing physical or virtual machine for discovery of VMware VMs or Hyper-V VMs using a PowerShell installer script, available for download in a zip file from portal.
+- For physical or virtual servers from on-premises or any cloud, you always deploy the appliance using a script on an existing server.
+- For Azure Government, all three appliances can only be deployed using the PowerShell installer script.
 
 ## How does the appliance connect to Azure?
 
-The appliance can connect via the internet or by using Azure ExpressRoute.
+The appliance can connect via the internet or by using Azure ExpressRoute. Make sure these [URLs](https://docs.microsoft.com/azure/migrate/migrate-appliance#url-access) are whitelisted for the appliance to connect to Azure.
 
 - To use Azure ExpressRoute for Azure Migrate replication traffic, Microsoft peering or an existing public peering is required (Public peering is deprecated for new ER creations).
 - Replication over Azure ExpressRoute with (only) private peering enabled is not supported.
@@ -61,6 +62,7 @@ See the following articles for information about data that the Azure Migrate app
 
 - **VMware VM**: [Review](migrate-appliance.md#collected-data---vmware) collected data.
 - **Hyper-V VM**: [Review](migrate-appliance.md#collected-data---hyper-v) collected data.
+- **Physical or virtual servers**:[Review](migrate-appliance.md#collected-data---physical) collected data.
 
 ## How is data stored?
 
@@ -102,8 +104,7 @@ A project can have multiple appliances attached to it. However, an appliance can
 
 ## Can the Azure Migrate appliance/Replication appliance connect to the same vCenter?
 
-Yes. You can add both the Azure Migrate appliance (used for assessment and agentless VMware migration), and the replication appliance (used for agent-based migration of VMware VMs) to the same vCenter server.
-
+Yes. You can add both the Azure Migrate appliance (used for assessment and agentless VMware migration), and the replication appliance (used for agent-based migration of VMware VMs) to the same vCenter server. But make sure that you are not setting up both appliances on the same VM and that is currently not supported.
 
 ## How many VMs or servers can I discover with an appliance?
 
@@ -119,7 +120,9 @@ However, deleting the resource group also deletes other registered appliances, t
 
 ## Can I use the appliance with a different subscription or project?
 
-After you use the appliance to initiate discovery, you can't reconfigure the appliance to use with a different Azure subscription, and you can't use it in a different Azure Migrate project. You also can't discover VMs on a different instance of vCenter Server. Set up a new appliance for these tasks.
+To use the appliance with a different subscription or project, you would need to re-configure the existing appliance by running the PowerShell installer script for the specific scenario (VMware/Hyper-V/Physical) on the appliance machine. The script will clean up the existing appliance components and settings to deploy a fresh appliance. Please ensure to clear the browser cache before you start using the newly deployed appliance configuration manager.
+
+Also, you cannot re-use an existing Azure Migrate project key on a re-configured appliance. Make sure you generate a new key from the desired subscription/project to complete the appliance registration.
 
 ## Can I set up the appliance on an Azure VM?
 

articles/migrate/deploy-appliance-script.md

@@ -47,7 +47,7 @@ Check that the zipped file is secure, before you deploy it.
 
     **Algorithm** | **Download** | **SHA256**
     --- | --- | ---
-    VMware (85 MB) | [Latest version](https://go.microsoft.com/fwlink/?linkid=2140334) | 5d0a3dbce4b5010980d59d49859f809acfeb17f5a36f57af4dac44a0a62dde1f
+    VMware (85 MB) | [Latest version](https://go.microsoft.com/fwlink/?linkid=2116601) | 72fef66b8efd93106e626ea87354af0fb800893f9cb77edb5490490106c6a193
 
 
 
@@ -96,7 +96,7 @@ Check that the zipped file is secure, before you deploy it.
 
     **Scenario** | **Download** | **SHA256**
     --- | --- | ---
-    Hyper-V (85 MB) | [Latest version](https://go.microsoft.com/fwlink/?linkid=2140334) |  5d0a3dbce4b5010980d59d49859f809acfeb17f5a36f57af4dac44a0a62dde1f
+    Hyper-V (85 MB) | [Latest version](https://go.microsoft.com/fwlink/?linkid=2116657) |  bea013eab690ae3a476422c55becd87c369c14834e52f8cafe6ad0ed7f416b4f
 
 ### Run the script
 

articles/migrate/media/migrate-appliance-architecture/architecture.png

@@ -58,15 +58,15 @@ Data collected by the client for all deployment scenarios is summarized in the [
 
 ## Discovery and collection process
 
-![Architecture](./media/migrate-appliance-architecture/architecture.png)
+![Architecture](./media/migrate-appliance-architecture/architecture1.png)
 
 The appliance communicates with vCenter Servers and Hyper-V hosts/cluster using the following process.
 
 1. **Start discovery**:
-    - When you start the discovery on the Hyper-V appliance, it communicates with the Hyper-V hosts on WinRM ports 5985 (HTTP) and 5986 (HTTPS).
+    - When you start the discovery on the Hyper-V appliance, it communicates with the Hyper-V hosts on WinRM port 5985 (HTTP).
     - When you start discovery on the VMware appliance, it communicates with the vCenter server on TCP port 443 by default. IF the vCenter server listens on a different port, you can configure it in the appliance web app.
 2. **Gather metadata and performance data**:
-    - The appliance uses a Common Information Model (CIM) session to gather Hyper-V VM data from the Hyper-V host on ports 5985 and 5986.
+    - The appliance uses a Common Information Model (CIM) session to gather Hyper-V VM data from the Hyper-V host on port 5985.
     - The appliance communicates with port 443 by default, to gather VMware VM data from the vCenter Server.
 3. **Send data**: The appliance sends the collected data to Azure Migrate Server Assessment and Azure Migrate Server Migration over SSL port 443. The appliance can connect to Azure over the internet, or you can use ExpressRoute with public/Microsoft peering.
     - For performance data, the appliance collects real-time utilization data.
@@ -77,17 +77,12 @@ The appliance communicates with vCenter Servers and Hyper-V hosts/cluster using
     - For Server Migration, the appliance starts collecting VM data, and replicates it to Azure.
 4. **Assess and migrate**: You can now create assessments from the metadata collected by the appliance using Azure Migrate Server Assessment. In addition, you can also start migrating VMware VMs using Azure Migrate Server Migration to orchestrate agentless VM replication.
 
-
-
-
-
 ## Appliance upgrades
 
 The appliance is upgraded as the Azure Migrate agents running on the appliance are updated. This happens automatically because auto-update is enabled on the appliance by default. You can change this default setting to update the agents manually.
 
 You turn off auto-update in the registry by setting the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AzureAppliance "AutoUpdate" key to 0 (DWORD).
 
- 
 
 ## Next steps
 

articles/migrate/media/migrate-appliance-architecture/architecture1.png

@@ -117,7 +117,7 @@ download.microsoft.com/download | Allow downloads from Microsoft download.
 graph.windows.net | Sign in to your Azure subscription.
 login.microsoftonline.us  | Create Azure Active Directory (AD) apps for the appliance to communicate with Azure Migrate.
 management.usgovcloudapi.net | Create Azure AD apps for the appliance to communicate with the Azure Migrate service.
-dc.services.visualstudio.com | Upload app logs used for internal monitoring.
+*.services.visualstudio.com | Upload app logs used for internal monitoring.
 *.vault.usgovcloudapi.net | Manage secrets in the Azure Key Vault.
 aka.ms/* | Allow access to aka links. Used for Azure Migrate appliance updates.
 download.microsoft.com/download | Allow downloads from Microsoft download.

articles/migrate/migrate-appliance-architecture.md

@@ -111,7 +111,7 @@ Check that the zipped file is secure, before you deploy it.
 
         **Scenario*** | **Download** | **SHA256**
         --- | --- | ---
-        Hyper-V (85 MB) | [Latest version](https://go.microsoft.com/fwlink/?linkid=2140424) |  8025f315e41c01ebdb4ffb1de87982ae6cc4ea7c4cce612612c7e90a44e79b44
+        Hyper-V (85 MB) | [Latest version](https://go.microsoft.com/fwlink/?linkid=2140424) |  0769c5f8df1e8c1ce4f685296f9ee18e1ca63e4a111d9aa4e6982e069df430d7
 
 
 ### Create the appliance VM

articles/migrate/migrate-appliance.md

@@ -110,13 +110,13 @@ Check that the zipped file is secure, before you deploy it.
 
         **Scenario** | **Download*** | **Hash value**
         --- | --- | ---
-        Physical (85 MB) | [Latest version](https://go.microsoft.com/fwlink/?linkid=2140334) | 6de88e229c2b4836d16ce03fdfac93b5c27274945577bd8a359d598cf3777b24
+        Physical (85 MB) | [Latest version](https://go.microsoft.com/fwlink/?linkid=2140334) | 207157bab39303dca1c2b93562d6f1deaa05aa7c992f480138e17977641163fb
 
     - For Azure Government:
 
         **Scenario** | **Download*** | **Hash value**
         --- | --- | ---
-        Physical (85 MB) | [Latest version](https://go.microsoft.com/fwlink/?linkid=2140338) | 5a4715a9d10e81a5f38192b7d1c6ac0919ae3998afbf2e933c99bafae6bef80e
+        Physical (85 MB) | [Latest version](https://go.microsoft.com/fwlink/?linkid=2140338) | ca67e8dbe21d113ca93bfe94c1003ab7faba50472cb03972d642be8a466f78ce
 
 ### Run the Azure Migrate installer script
 

articles/migrate/tutorial-assess-hyper-v.md

@@ -109,7 +109,7 @@ Check that the OVA file is secure, before you deploy it:
 
         **Algorithm** | **Download** | **SHA256**
         --- | --- | ---
-        VMware (85 MB) | [Latest version](https://go.microsoft.com/fwlink/?linkid=2140337) | 7dab9445a89b47302994d6de4caddaa092c1c582c8f3c1fc5b9c4908c7d2f9f7
+        VMware (85 MB) | [Latest version](https://go.microsoft.com/fwlink/?linkid=2140337) | 47179f47eba2842337bbe533c424dd1da56baccdcf68b1d87b71a5a4280108c2
 
 
 ### Create the appliance VM