Merge pull request #96250 from snehaamicrosoft/azuremigrateIgnite

appliance hash updates

Author: ShannonLeavitt

articles/migrate/how-to-create-group-machine-dependencies-agentless.md

@@ -1,27 +1,24 @@
 ---
-title: Group machines in Azure Migrate using agentless dependency visualization 
+title: Group machines in Azure Migrate using agentless dependency visualization
 description: Describes how to create groups using machine dependencies in an agentless manner.
 author: rayne-wiselman
 ms.service: azure-migrate
 ms.topic: article
-ms.date: 10/23/2019
+ms.date: 11/18/2019
 ms.author: hamusa
 ---
 
 
 # Set up agentless dependency visualization for assessment
 
-> [!NOTE]
-> If you don't yet see this feature in the Azure Migrate portal, hang on. It will appear over the next week or so.
-
 This article describes how to set up agentless dependency mapping in Azure Migrate: Server Assessment. This capability is currently available in preview for VMware machines discovered using an Azure Migrate appliance. 
 
 > [!IMPORTANT]
 > Agentless dependency visualization is currently in preview for Azure VMware VMs discovered using an Azure Migrate appliance.
-> This preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities. 
+> This preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.
 > For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
-## About dependency mapping 
+## About dependency mapping
 
 Dependency mapping helps you to visualize dependencies across machines that you want to assess and migrate. You typically use dependency mapping when you want to assess machines with higher levels of confidence.
 
@@ -43,7 +40,7 @@ Agentless dependency visualization doesn't require you to install any agents on
 ## Current limitations
 
 - Agentless dependency visualization is currently available for VMware VMs only.
-- Right now you can't add or remove a server from a group, in the dependency analysis view. 
+- Right now you can't add or remove a server from a group, in the dependency analysis view.
 - Dependency map for a group of servers is currently not available.
 - Currently, the dependency data cannot be downloaded in tabular format.
 
@@ -57,12 +54,12 @@ Agentless dependency visualization doesn't require you to install any agents on
 
 
 ### Supported operating systems
- 
+
 Supported operating systems for agentless dependency visualization are as follows.
 
 **Type** | **Supported operating systems**
---- | --- 
-**Windows** | Microsoft Windows Server 2016 <br/> Microsoft Windows Server 2012 R2 <br/> Microsoft Windows Server 2012 <br/> Microsoft Windows Server 2008 R2 (64-bit) 
+--- | ---
+**Windows** | Microsoft Windows Server 2016 <br/> Microsoft Windows Server 2012 R2 <br/> Microsoft Windows Server 2012 <br/> Microsoft Windows Server 2008 R2 (64-bit)
 **Linux** | Red Hat Enterprise Linux 7, 6, 5 <br/> Ubuntu Linux 14.04, 16.04 <br/> Debian 7, 8 <br/> Oracle Linux 6, 7 <br/> CentOS 5, 6, 7  
 
 
@@ -81,7 +78,7 @@ Add the account as follows:
 
 1. Open the appliance management app. Navigate to the **Provide vCenter details** panel.
 2. In the **Discover application and dependencies on VMs** section, click **Add credentials**
-3. Choose the **Operating system**. 
+3. Choose the **Operating system**.
 4. Provide a friendly name for the account.
 5. Provide the **User name** and **Password**
 6. Click **Save**.
@@ -110,8 +107,8 @@ You will be able to visualize dependencies 6 hours after starting dependency dis
 2. Search for the machine for which you want to view the dependency map.
 3. Click **View dependencies** in the **Dependencies** column.
 4. Change the time period for which you want to view the map using the **Time duration** dropdown.
-5. Expand the **Client** group to list the machines that have a dependency on the selected machine. 
-6. Expand the **Port** group to list the machines that have a dependency from the selected machine. 
+5. Expand the **Client** group to list the machines that have a dependency on the selected machine.
+6. Expand the **Port** group to list the machines that have a dependency from the selected machine.
 7. To navigate to the map view of any of the dependent machines, click on the machine name, and then click **Load server map**
 
     ![Expand Server port group and load server map](./media/how-to-create-group-machine-dependencies-agentless/load-server-map.png)

articles/migrate/how-to-discover-applications.md

@@ -4,20 +4,17 @@ description: Describes how to discover apps, roles, and features on on-premises
 author: snehaamicrosoft
 ms.service: azure-migrate
 ms.topic: article
-ms.date: 10/16/2019
+ms.date: 11/18/2019
 ms.author: snehaa
 ---
- 
-# Discover machine apps, roles, and features 
 
-> [!NOTE]
-> If you don't yet see this feature in the Azure Migrate portal, hang on. It will appear over the next week or so.
+# Discover machine apps, roles, and features
 
 This article describes how to discover applications, roles, and features on on-premises servers, using Azure Migrate: Server Assessment.
 
-Discovering the inventory of apps, and roles/features running on your on-premises machines helps you to identify and plan a migration path to Azure that's tailored for your workloads. 
+Discovering the inventory of apps, and roles/features running on your on-premises machines helps you to identify and plan a migration path to Azure that's tailored for your workloads.
 
-App discovery using Azure Migrate: Server Assessment is agentless. Nothing needs to be installed on machines and VMs. Server Assessment uses the Azure Migrate appliance to perform discovery along with machine guest credentials. The appliance remotely accesses machines using WMI and SSH calls. 
+App discovery using Azure Migrate: Server Assessment is agentless. Nothing needs to be installed on machines and VMs. Server Assessment uses the Azure Migrate appliance to perform discovery along with machine guest credentials. The appliance remotely accesses machines using WMI and SSH calls.
 
 > [!NOTE]
 > App discovery is currently supported for VMware VMs only, and is limited to discovery only. We don't yet offer app-based assessment.  Right now Server Assessment currently assesses on-premises VMware VMs, Hyper-V VMs, and physical servers at the machine level, for lift-and-shift migrations.
@@ -45,7 +42,7 @@ After the appliance is deployed and you've provided credentials, the appliance s
 
 ## Review and export the inventory
 
-After discovery finishes, if you provided credentials for app discovery, you can review and export the app inventory in the Azure portal. 
+After discovery finishes, if you provided credentials for app discovery, you can review and export the app inventory in the Azure portal.
 
 1. In **Azure Migrate - Servers** > **Azure Migrate: Server Assessment**, click the displayed count to open the **Discovered servers** page.
 

articles/migrate/how-to-set-up-appliance-hyper-v.md

@@ -25,7 +25,7 @@ The Hyper-V VM appliance is a lightweight appliance used by Azure Migrate Server
 
 To set up the appliance you:
 - Download a compressed Hyper-V VHD from the Azure portal.
-- Create the appliance, and check that it can connect to Azure Migrate Server Assessment. 
+- Create the appliance, and check that it can connect to Azure Migrate Server Assessment.
 - Configure the appliance for the first time, and register it with the Azure Migrate project.
 
 ## Download the VHD
@@ -47,14 +47,15 @@ Check that the zipped file is secure, before you deploy it.
 2. Run the following command to generate the hash for the VHD
     - ```C:\>CertUtil -HashFile <file_location> [Hashing Algorithm]```
     - Example usage: ```C:\>CertUtil -HashFile C:\AzureMigrate\AzureMigrate.ova SHA256```
-3.  For appliance version 1.19.05.10, the generated hash should match these settings.
+3.  For appliance version 2.19.11.12, the generated hash should match these settings.
 
   **Algorithm** | **Hash value**
   --- | ---
-  SHA256 | 598d2e286f9c972bb7f7382885e79e768eddedfe8a3d3460d6b8a775af7d7f79
+  MD5 | 29a7531f32bcf69f32d964fa5ae950bc
+  SHA256 | 37b3f27bc44f475872e355f04fcb8f38606c84534c117d1609f2d12444569b31
+
 
 
-  
 ## Create the appliance VM
 
 Import the downloaded file, and create the VM.
@@ -100,7 +101,7 @@ Set up the appliance for the first time.
 ### Register the appliance with Azure Migrate
 
 1. Click **Log In**. If it doesn't appear, make sure you've disabled the pop-up blocker in the browser.
-2. On the new tab, sign in using your Azure credentials. 
+2. On the new tab, sign in using your Azure credentials.
     - Sign in with your username and password.
     - Sign-in with a PIN isn't supported.
 3. After successfully signing in, go back to the web app.
@@ -138,16 +139,16 @@ Connect from the appliance to Hyper-V hosts or clusters, and start VM discovery.
     - You can add a cluster, even if there are issues with specific hosts in the cluster.
 4. After validation, click **Save and start discovery** to start the discovery process.
 
-This starts discovery. It takes around 15 minutes for metadata of discovered VMs to appear in the Azure portal. 
+This starts discovery. It takes around 15 minutes for metadata of discovered VMs to appear in the Azure portal.
 
 ## Verify VMs in the portal
 
 After discovery finishes, you can verify that the VMs appear in the portal.
 
 1. Open the Azure Migrate dashboard.
-2. In **Azure Migrate - Servers** > **Azure Migrate: Server Assessment** page, click the icon that displays the count for **Discovered servers**. 
+2. In **Azure Migrate - Servers** > **Azure Migrate: Server Assessment** page, click the icon that displays the count for **Discovered servers**.
 
 
 ## Next steps
 
-Try out [Hyper-V assessment](tutorial-assess-hyper-v.md) with Azure Migrate Server Assessment.
+Try out [Hyper-V assessment](tutorial-assess-hyper-v.md) with Azure Migrate Server Assessment.

articles/migrate/how-to-set-up-appliance-physical.md

@@ -51,14 +51,15 @@ Check that the zipped file is secure, before you deploy it.
 2. Run the following command to generate the hash for the VHD
     - ```C:\>CertUtil -HashFile <file_location> [Hashing Algorithm]```
     - Example usage: ```C:\>CertUtil -HashFile C:\AzureMigrate\AzureMigrate.ova SHA256```
-3.  For appliance version 1.19.05.10, the generated hash should match these settings.
+3.  For the latest appliance version, the generated hash should match these settings.
 
   **Algorithm** | **Hash value**
   --- | ---
-  SHA256 | 598d2e286f9c972bb7f7382885e79e768eddedfe8a3d3460d6b8a775af7d7f79
+  MD5 | 5b98cf68dad495696c789bdad8f0d91b
+  SHA256 | c2364887738875a31634eb0cf5defd0398f813d41069875976ca076297071e6f
+
 
 
-  
 ## Run the Azure Migrate installer script
 =
 The installer script does the following:
@@ -107,7 +108,7 @@ Set up the appliance for the first time.
 ### Register the appliance with Azure Migrate
 
 1. Click **Log In**. If it doesn't appear, make sure you've disabled the pop-up blocker in the browser.
-2. On the new tab, sign in using your Azure credentials. 
+2. On the new tab, sign in using your Azure credentials.
     - Sign in with your username and password.
     - Sign-in with a PIN isn't supported.
 3. After successfully signing in, go back to the web app.
@@ -129,14 +130,14 @@ You can add one set of credentials each for Windows and Linux servers.
     - To remove a server, select > **Delete**.
 4. After validation, click **Save and start discovery** to start the discovery process.
 
-This starts discovery. It takes around 15 minutes for metadata of discovered VMs to appear in the Azure portal. 
+This starts discovery. It takes around 15 minutes for metadata of discovered VMs to appear in the Azure portal.
 
 ## Verify servers in the portal
 
 After discovery finishes, you can verify that the servers appear in the portal.
 
 1. Open the Azure Migrate dashboard.
-2. In **Azure Migrate - Servers** > **Azure Migrate: Server Assessment** page, click the icon that displays the count for **Discovered servers**. 
+2. In **Azure Migrate - Servers** > **Azure Migrate: Server Assessment** page, click the icon that displays the count for **Discovered servers**.
 
 
 ## Next steps

articles/migrate/how-to-set-up-appliance-vmware.md

@@ -4,7 +4,7 @@ description: Describes how to set up an appliance for discovery, assessment, and
 author: rayne-wiselman
 ms.service: azure-migrate
 ms.topic: article
-ms.date: 10/10/2019
+ms.date: 11/18/2019
 ms.author: raynew
 ---
 
@@ -44,11 +44,12 @@ Check that the OVA file is secure, before you deploy it.
 2. Run the following command, to generate the hash for the OVA:
     - ```C:\>CertUtil -HashFile <file_location> [Hashing Algorithm]```
     - Example usage: ```C:\>CertUtil -HashFile C:\AzureMigrate\AzureMigrate.ova SHA256```
-3. For appliance version 1.0.0.5, the generated hash should match these settings.
+3. For the latest appliance version, the generated hash should match these settings.
 
   **Algorithm** | **Hash value**
   --- | ---
-  MD5 | ddfdf21c64af02a222ed517ce300c977
+  MD5 | c06ac2a2c0f870d3b274a0b7a73b78b1
+  SHA256 | 4ce4faa3a78189a09a26bfa5b817c7afcf5b555eb46999c2fad9d2ebc808540c
 
 
 ## Create the appliance VM

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

@@ -5,7 +5,7 @@ author: rayne-wiselman
 manager: carmonm
 ms.service: azure-migrate
 ms.topic: tutorial
-ms.date: 08/11/2019
+ms.date: 11/18/2019
 ms.author: raynew
 ms.custom: mvc
 ---
@@ -114,10 +114,8 @@ Check that the zipped file is secure, before you deploy it.
 
   **Algorithm** | **Hash value**
   --- | ---
-  MD5 | d0a68e76ea24ba4e4a494c0dab95e90e
-  SHA256 | 0551221d2a9de75c352c201ccc88f7f10e87e5df1ecda42bfd4ec6c8defc57c0
-
-
+  MD5 | 29a7531f32bcf69f32d964fa5ae950bc
+  SHA256 | 37b3f27bc44f475872e355f04fcb8f38606c84534c117d1609f2d12444569b31
 
 ### Create the appliance VM
 
@@ -218,7 +216,7 @@ Connect from the appliance to Hyper-V hosts or clusters, and start VM discovery.
     - You can add a cluster, even if there are issues with specific hosts in the cluster.
 4. After validation, click **Save and start discovery** to start the discovery process.
 
-This starts discovery. It takes around 1.5 minutes per host for metadata of discovered servers to appear in the Azure portal. 
+This starts discovery. It takes around 1.5 minutes per host for metadata of discovered servers to appear in the Azure portal.
 
 ### Verify VMs in the portal