Merge pull request #101637 from musa-57/hanaadocslocal

Scale article for physical assess, troubleshooting changes, fix depen…

Author: Jak-MS

articles/migrate/common-questions-appliance.md

@@ -78,9 +78,9 @@ Yes, for both.
 
 No. There's a one-to-one mapping between an appliance and vCenter Server. To discover VMs on multiple vCenter Server instances, you need to deploy multiple appliances.
 
-### How many VMs can I discover with an appliance?
+### How many VMs or servers can I discover with an appliance?
 
-You can discover up to 10,000 VMware VMs and up to 5,000 Hyper-V VMs with a single appliance. If you have more machines in your on-premises environment, read about scaling [Hyper-V](scale-hyper-v-assessment.md) and [VMware](scale-vmware-assessment.md) assessment.
+You can discover up to 10,000 VMware VMs, up to 5,000 Hyper-V VMs and up to 250 servers with a single appliance. If you have more machines in your on-premises environment, read about scaling [Hyper-V](scale-hyper-v-assessment.md), [VMware](scale-vmware-assessment.md) and [physical](scale-physical-assessment.md) assessment.
 
 ## Can I delete an appliance?
 

articles/migrate/common-questions-discovery-assessment.md

@@ -16,7 +16,7 @@ This article answers common questions about discovery, assessment, and dependenc
 
 ## How many VMs can I discover with an appliance?
 
-You can discover up to 10,000 VMware VMs and up to 5,000 Hyper-V VMs with a single appliance. If you have more machines in your on-premises environment, read about scaling [Hyper-V](scale-hyper-v-assessment.md) and [VMware](scale-vmware-assessment.md) assessment.
+You can discover up to 10,000 VMware VMs, up to 5,000 Hyper-V VMs and up to 250 servers with a single appliance. If you have more machines in your on-premises environment, read about scaling [Hyper-V](scale-hyper-v-assessment.md), [VMware](scale-vmware-assessment.md) and [physical](scale-physical-assessment.md) assessment.
 
 
 

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

@@ -83,10 +83,10 @@ Choose the machines on which you want to enable dependency discovery.
 
 1. In **Azure Migrate: Server Assessment**, click **Discovered servers**.
 2. Click the **Dependency analysis** icon.
-3. Click **Start dependency discovery**.
-3. In the **Start dependency discovery** page, choose the appliance that's discovering the relevant machines.
+3. Click **Add servers**.
+3. In the **Add servers** page, choose the appliance that's discovering the relevant machines.
 4. From the machine list, select the machines.
-5. Click **Start dependency discovery**.
+5. Click **Add servers**.
 
     ![Start dependency discovery](./media/how-to-create-group-machine-dependencies-agentless/start-dependency-discovery.png)
 
@@ -119,10 +119,10 @@ Choose the machines on which you want to stop dependency discovery.
 
 1. In **Azure Migrate: Server Assessment**, click **Discovered servers**.
 2. Click the **Dependency analysis** icon.
-3. Click **Stop dependency discovery**.
-3. In the **Stop dependency discovery** page, choose the **appliance** that is discovering the VMs on which you look to stop dependency discovery.
+3. Click **Remove servers**.
+3. In the **Remove servers** page, choose the **appliance** that is discovering the VMs on which you look to stop dependency discovery.
 4. From the machine list, select the machines.
-5. Click **Stop dependency discovery**
+5. Click **Remove servers**.
 
 
 ## Next steps

articles/migrate/media/how-to-create-group-machine-dependencies-agentless/start-dependency-discovery.png

@@ -0,0 +1,91 @@
+---
+title: Assess large numbers of physical servers for migration to Azure with Azure Migrate | Microsoft Docs
+description: Describes how to assess large numbers of physical servers for migration to Azure using the Azure Migrate service.
+author: rayne-wiselman
+manager: carmonm
+ms.service: azure-migrate
+ms.topic: conceptual
+ms.date: 01/19/2020
+ms.author: hamusa
+---
+
+# Assess large numbers of physical servers for migration to Azure
+
+This article describes how to assess large numbers of on-premises physical servers for migration to Azure, using the Azure Migrate Server Assessment tool.
+
+[Azure Migrate](migrate-services-overview.md) provides a hub of tools that help you to discover, assess, and migrate apps, infrastructure, and workloads to Microsoft Azure. The hub includes Azure Migrate tools, and third-party independent software vendor (ISV) offerings. 
+
+
+In this article, you learn how to:
+> [!div class="checklist"]
+> * Plan for assessment at scale.
+> * Configure Azure permissions, and prepare physical servers for assessment.
+> * Create an Azure Migrate project, and create an assessment.
+> * Review the assessment as you plan for migration.
+
+
+> [!NOTE]
+> If you want to try out a proof-of-concept to assess a couple of servers before assessing at scale, follow our [tutorial series](tutorial-prepare-physical.md).
+
+## Plan for assessment
+
+When planning for assessment of large number of physical servers, there are a couple of things to think about:
+
+- **Plan Azure Migrate projects**: Figure out how to deploy Azure Migrate projects. For example, if your data centers are in different geographies, or you need to store discovery, assessment or migration-related metadata in a different geography, you might need multiple projects.
+- **Plan appliances**: Azure Migrate uses an on-premises Azure Migrate appliance, deployed on a Windows machine, to continually discover servers for assessment and migration. The appliance monitors environment changes such as adding VMs, disks, or network adapters. It also sends metadata and performance data about them to Azure. You need to figure out how many appliances to deploy.
+
+
+## Planning limits
+ 
+Use the limits summarized in this table for planning.
+
+**Planning** | **Limits**
+--- | --- 
+**Azure Migrate projects** | Assess up to 35,000 servers in a project.
+**Azure Migrate appliance** | An appliance can discover up to 250 servers.<br/> An appliance can only be associated with a single Azure Migrate project.<br/> Any number of appliances can be associated with a single Azure Migrate project. <br/><br/> 
+**Group** | You can add up to 35,000 servers in a single group.
+**Azure Migrate assessment** | You can assess up to 35,000 servers in a single assessment.
+
+
+## Other planning considerations
+
+- To start discovery from the appliance, you have to select each physical server. 
+
+## Prepare for assessment
+
+Prepare Azure and physical servers for server assessment. 
+
+1. Verify [physical server support requirements and limitations](migrate-support-matrix-physical.md).
+2. Set up permissions for your Azure account to interact with Azure Migrate.
+3. Prepare the physical servers.
+
+Follow the instructions in [this tutorial](tutorial-prepare-physical.md) to configure these settings.
+
+## Create a project
+
+In accordance with your planning requirements, do the following:
+
+1. Create an Azure Migrate project.
+2. Add the Azure Migrate Server Assessment tool to the projects.
+
+[Learn more](how-to-add-tool-first-time.md)
+
+## Create and review an assessment
+
+1. Create assessments for physical servers.
+1. Review the assessments in preparation for migration planning.
+
+[Learn more](tutorial-assess-physical.md) about creating and reviewing assessments.
+    
+
+## Next steps
+
+In this article, you:
+ 
+> [!div class="checklist"] 
+> * Planned to scale Azure Migrate assessments for physical servers.
+> * Prepared Azure and physical servers for assessment.
+> * Created an Azure Migrate project and ran assessments.
+> * Reviewed assessments in preparation for migration.
+
+Now, [learn how](concepts-assessment-calculation.md) assessments are calculated, and how to [modify assessments](how-to-modify-assessment.md).

articles/migrate/scale-physical-assessment.md

@@ -125,6 +125,8 @@
       href: scale-vmware-assessment.md
     - name: Assess large numbers of Hyper-V VMs
       href: scale-hyper-v-assessment.md
+    - name: Assess large numbers of physical servers
+      href: scale-physical-assessment.md
     - name: Automate migration of large number of VMs
       href: how-to-migrate-at-scale.md
     - name: Migration examples (Contoso series)

articles/migrate/toc.yml

@@ -87,6 +87,7 @@ Server Assessment reports "PercentageOfCoresUtilizedMissing" or "PercentageOfMem
 - This can occur if the VMs are turned off during the assessment duration. The appliance can't collect performance data for a VM when it's turned off.
 - If only the memory counters are missing and you're trying to assess Hyper-V VMs, check whether you have dynamic memory enabled on these VMs. There's a known issue for Hyper-V VMs only, in which an Azure Migrate appliance can't collect memory utilization data for VMs that don't have dynamic memory enabled.
 - If any of the performance counters are missing, Azure Migrate Server Assessment falls back to the allocated cores and memory, and it recommends a corresponding VM size.
+- If all of the performance counters are missing, ensure the port access requirements for assessment are met. Learn more about the port access requirements for [VMware](https://docs.microsoft.com/azure/migrate/migrate-support-matrix-vmware#port-access), [Hyper-V](https://docs.microsoft.com/azure/migrate/migrate-support-matrix-hyper-v#port-access) and [physical](https://docs.microsoft.com/azure/migrate/migrate-support-matrix-physical#port-access) server assessment.
 
 ## Is the operating system license included?