Merge pull request #107148 from musa-57/hanaalocal

PRMerger13 · web-flow · commit 05d2aca106ab · 2020-03-10T12:26:35.000-07:00
Import enhancements, App disc troubleshooting
diff --git a/articles/migrate/common-questions-discovery-assessment.md b/articles/migrate/common-questions-discovery-assessment.md
@@ -65,6 +65,12 @@ For example, if you set the performance duration to one day and the percentile v
 
 Using the 95th percentile value ensures that outliers are ignored. Outliers might be included if your Azure Migrate uses the 99th percentile. To pick the peak usage for the period without missing any outliers, set Azure Migrate to use the 99th percentile.
 
+## How are import-based assessments different from assessments with discovery source as appliance?
+
+Import-based assessments are assessments created with machines that are imported into Azure Migrate using a CSV file. Only four fields are mandatory to import: Server name, cores, memory, and operating system. Here are some things to note: 
+ - The readiness criteria is less stringent in import-based assessments on the boot type parameter. If the boot type isn't provided, it is assumed the machine has BIOS boot type and the machine is not marked as **Conditionally Ready**. In assessments with discovery source as appliance, the readiness is marked as **Conditionally Ready** if the boot type is missing. This difference in readiness calculation is because users may not have all information on the machines in the early stages of migration planning when import-based assessments are done. 
+ - Performance-based import assessments use the utilization value provided by the user for right-sizing calculations. Since the utilization value is provided by the user, the **Performance history** and **Percentile utilization** options are disabled in the assessment properties. In assessments with discovery source as appliance, the chosen percentile value is picked from the performance data collected by the appliance.
+
 ## What is dependency visualization?
 
 Dependency visualization can help you assess groups of VMs to migrate with greater confidence. Dependency visualization cross-checks machine dependencies before you run an assessment. It helps ensure that nothing is left behind, and it helps avoid unexpected outages when you migrate to Azure. Azure Migrate uses the Service Map solution in Azure Monitor to enable dependency visualization. [Learn more](concepts-dependency-visualization.md).
diff --git a/articles/migrate/concepts-dependency-visualization.md b/articles/migrate/concepts-dependency-visualization.md
@@ -50,7 +50,7 @@ There are two options for deploying dependency visualization:
 **Supported operating systems** | Review the [operating systems](migrate-support-matrix-vmware.md#agentless-dependency-visualization) supported for agentless visualization.
 **VMs** | **VMware tools**: VMware Tools must be installed and running on VMs you want to analyze.<br/><br/> **Account**: On the Azure Migrate appliance, you need to add a user account that can be used to access VMs for analysis.<br/><br/> **Windows VMs**: The user account needs to be a local or a domain administrator on the machine.<br/><br/> **Linux VMs**: The root privilege is required on the account. Alternately, the user account requires these two capabilities on /bin/netstat and /bin/ls files: CAP_DAC_READ_SEARCH and CAP_SYS_PTRACE. | [Learn about](migrate-appliance.md) the Azure Migrate appliance.
 **VMware** | **vCenter**: The appliance needs a vCenter Server account with read-only access, and privileges enabled for Virtual Machines > Guest Operations.<br/><br/> **ESXi hosts**: On ESXi hosts running VMs you want to analyze, the Azure Migrate appliance must be able to connect to TCP port 443.
-**Collected data** |  Agentless dependency visualization works by capturing TCP connection data from machines for which it's enabled. After dependency discovery starts, the appliance gathers this data from machines by polling every five minutes:<br/> - TCP connections.<br/> - Names of processes that have active connections.<br/> - Names of installed applications that run the process with active connections.<br/> - The number of connections detected at every polling interval.
+**Collected data** |  Agentless dependency analysis works by capturing TCP connection data from machines on which it's enabled. After dependency discovery is enabled, the appliance collects TCP connection data every 5 minutes from guest VMs. This data is gathered from guest VMs via vCenter Server using vSphere APIs. The gathered data is processed on the appliance to deduce dependency information and sent to Azure Migrate every 6 hours. The following data is gathered from each machine: <br/> - Names of processes that have active connections.<br/> - Names of applications that run the process with active connections.<br/> - Destination port on the active connections.
 
 
 ## Next steps
diff --git a/articles/migrate/migrate-support-matrix-vmware.md b/articles/migrate/migrate-support-matrix-vmware.md
@@ -38,6 +38,7 @@ In addition to discovering machines, Azure Migrate: Server Assessment can discov
 **vCenter credentials** | A vCenter Server account with read-only access, and privileges enabled for Virtual Machines > Guest Operations.
 **VM credentials** | Currently supports the use of one credential for all Windows servers, and one credential for all Linux servers.<br/><br/> You create a guest user account for Windows VMs, and a regular/normal user account (non-sudo access) for all Linux VMs.
 **VMware tools** | VMware tools must be installed and running on VMs you want to discover. <br/> If your VMware tools version is between 9.10 - 10.2.0, please ensure you upgrade it to beyond 10.2.0.
+**Powershell** | VMs must have Powershell of version 2.0 or above
 **Port access** | On ESXi hosts running VMs you want to discover, the Azure Migrate appliance must be able to connect to TCP port 443.
 **Limits** | For app-discovery  you can discover up to 10000 per appliance. 
 
@@ -95,6 +96,7 @@ This option is currently in preview. [Learn more](how-to-create-group-machine-de
 **Linux account** | Visualization needs a user account with Root privilege.<br/><br/> Alternately, the user account needs these permissions on /bin/netstat and /bin/ls files: CAP_DAC_READ_SEARCH and CAP_SYS_PTRACE.
 **VM agents** | No agent needed on the VMs.
 **VMware tools** | VMware tools must be installed and running on VMs you want to analyze. <br/> If your VMware tools version is between 9.10 - 10.2.0, please ensure you upgrade it to beyond 10.2.0.
+**Powershell** | VMs must have Powershell of version 2.0 or above
 **vCenter credentials** | A vCenter Server account with read-only access, and privileges enabled for Virtual Machines > Guest Operations.
 **Port access** | On ESXi hosts running VMs you want to analyze, the Azure Migrate appliance must be able to connect to TCP port 443.
 
diff --git a/articles/migrate/troubleshoot-appliance-discovery.md b/articles/migrate/troubleshoot-appliance-discovery.md
@@ -146,6 +146,7 @@ Typical app discovery errors are summarized in the table.
 10004: "Unable to discover installed applications for <Windows/Linux> machines." |  Credentials to access <Windows/Linux> machines weren't provided in the appliance.| Add a credential to the appliance that has access to the <Windows/Linux> machines.
 10005: "Unable to access the on-premises server". | The access credentials might be wrong. | Update the appliance credentials make sure you can access the relevant machine with them. 
 10006: "Unable to access the on-premises server". | This might occur if the machine operating system isn't Windows or Linux.|  Only use app discovery for Windows/Linux.
+10007: "Unable to process the metadata retrieved" | This internal error occurred while trying to deserialize JSON | Contact Microsoft Support for a resolution
 9000/9001/9002: "Unable to discover the applications installed on the server". | VMware tools might not be installed or is corrupted. | Install/reinstall VMware tools on the relevant machine, and check it's running.
 9003: Unable to discover the applications installed on the server". | This might occur if the machine operating system isn't Windows or Linux. | Only use app discovery for Windows/Linux.
 9004: "Unable to discover the applications installed on the server". | This might happen if the VM is powered off. | For discovery, make sure the VM is on.
@@ -154,9 +155,21 @@ Typical app discovery errors are summarized in the table.
 9008: "Unable to retrieve the applications installed the server". | Might be an internal error.  | Tf the issue doesn't resolve itself within 24 hours, contact support.
 9009: "Unable to retrieve the applications installed the server". | Can occur if the Windows User Account Control (UAC) settings on the server are restrictive, and prevent discovery of installed applications. | Search for 'User Account Control' settings on the server, and configure the UAC setting on the server to one of the lower two levels.
 9010: "Unable to retrieve the applications installed the server". | Might be an internal error.  | Tf the issue doesn't resolve itself within 24 hours, contact support.
+9011: "File to download from guest is not found on the guest VM" | The issue can occur due to an internal error. | The issue should automatically get resolved in 24 hours. If the issue still persists, please contact Microsoft Support.
+9012: "Result file contents are empty." | The issue can occur due to an internal error. | The issue should automatically get resolved in 24 hours. If the issue still persists, please contact Microsoft Support.
+9013: "A new temporary profile is created for every login to the VMware VM" | A new temporary profile is created for every login into the VM | Ensure the user name provided in the guest VM credentials is in UPN format.
+9015: "Unable to connect to VMware VMs due to insufficient privileges on vCenter" | Guest Operations role is not enabled on the vCenter user account | Ensure Guest Operations role is enabled on the vCenter user account.
+9016: "Unable to connect to VMware VMs as the guest operations agent is out of data" | VMware tools is not properly installed or is not up to date. | Ensure the VMware  tools is properly installed and up to date.
+9017: "File with discovered metadata is not found on the VM." | The issue can occur due to an internal error. | Contact Microsoft Support for a resolution.
+9018: "PowerShell is not installed in the Guest VMs." | PowerShell is not available in the guest VM. | Install PowerShell in the guest VM.
+9019: "Unable to discover due to guest VM operation failures" | VMware guest operation failed on the VM. | Ensure that the VM credentials are valid and user name provided in the guest VM credentials is in UPN format.
+9020: "File creation permission is denied." | The role associated to the user or the group policy is restricting the user to create the file in the folder | Check if the guest user provided has create permission for the file in the folder. See **Notifications** in Server Assessment for the name of the folder.
+9021: "File create permission is denied in folder System Temp Path." | VMware tool version on the VM is unsupported | Upgrade your VMware tool version above 10.2.0.
+9022: "Get WMI object access is denied." | The role associated to the user or the group policy is restricting the user to access WMI object. | Please contact Microsoft Support.
+9023: "SystemRoot environment variable value is empty." | Not known | Please contact Microsoft Support.
+9024: "TEMP environment variable value is empty." | Not known | Please contact Microsoft Support.
+9025: "PowerShell is corrupt in the Guest VMs." | Not known | Reinstall PowerShell in the guest VM and check if PowerShell can be run on the guest VM.
 8084: "Unable to discover applications due to VMware error: <Exception from VMware>" | The Azure Migrate appliance uses VMware APIs to discover applications. This issue can happen if an exception is thrown by vCenter Server while trying to discover applications. The fault message from VMware is displayed in the error message shown in portal. | Search for the message in the [VMware documentation](https://pubs.vmware.com/vsphere-51/topic/com.vmware.wssdk.apiref.doc/index-faults.html), and follow the steps to fix. If you can't fix, contact Microsoft support.
-9012: "Unable to discover the applications installed on the server" | The issue can occur due to an internal error.  | If the issue doesn't resolve itself within 24 hours, contact support.
-9013: "Unable to discover the applications installed on the server" | A new temporary profile is created each time there is  log in to the VM.  | Ensure that a temporary profile is not created for the guest user provided.
 
 
 
diff --git a/articles/migrate/tutorial-assess-import.md b/articles/migrate/tutorial-assess-import.md
@@ -104,7 +104,7 @@ The following table summarizes the file fields to fill in:
 **IP address** | No | Server address.
 **Cores** | Yes | Number of processor cores allocated to the server.
 **Memory** | Yes | Total RAM, in MB, allocated to the server.
-**OS name** | Yes | Server operating system.
+**OS name** | Yes | Server operating system. <br/> Operating system names that match or contain the names in [this](#supported-operating-system-names) list are recognized by the assessment.
 **OS version** | No | Server operating system version.
 **Number of disks** | No | Not needed if individual disk details are provided.
 **Disk 1 size**  | No | Maximum size of disk, in GB.<br/>You can add details for more disks by [adding columns](#add-multiple-disks) in the template. You can add up to eight disks.
