[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-11。"],[],[],null,["# Requirements for machines and databases scanned\n\nThe physical machines and VMs that the discovery client collects data from\nare referred to as **target servers** in Migration Center. This page\ndescribes the specific configurations that the target servers must have,\ndepending on the OS type and the collection method.\n\nWindows machines\n----------------\n\nTo allow the discovery client to scan your physical or virtual Windows\nmachines, you provide it with\n[authentication credentials for the operating system](/migration-center/docs/create-and-manage-credentials).\nWindows machines must meet the following requirements:\n\n- WMI (Windows Management Instrumentation) Service is running.\n- Windows Firewall is disabled. Alternatively, a firewall exception to allow for Remote WMI.\n- The discovery client must be able to connect to each asset.\n- An account with administrator rights to the operating system.\n\nLinux machines\n--------------\n\nTo allow the discovery client to scan your physical or virtual Linux\nmachines, you provide it with authentication credentials for the operating\nsystem. Linux machines must meet the following requirements:\n\n- SSH enabled with support for the following encryption algorithms:\n - RSA and DSA in PEM format\n - ECDSA 256/384/521, ED25519 in OpenSSL or PEM formats\n- The discovery client must be able to connect to each asset.\n- An account with user-level access (no sudo or root privileges required).\n\n| **Note:** HP-UX, AIX, Solaris, FreeBSD and other UNIX-like systems are not supported.\n\nVMware vCenter\n--------------\n\nTo allow the discovery client to scan your vCenter source you provide the\nfollowing:\n\n- The credentials required to access vCenter.\n- The vCenter URL. Optionally, the vCenter Inventory Path to limit the scope of the collection.\n\nIn addition, you must configure vCenter and meet the requirements as described\nin the following sections.\n\n### vCenter configuration\n\nBefore you run a vCenter discovery, you need to configure your vCenter\nenvironment.\nThe data you collect with the discovery client, in fact, depend on\nthe settings for statistics in vCenter.\n\nvCenter supports four levels of statistics:\n\n- Level 1 exposes only CPU and memory performance.\n- Level 2 exposes the network performance.\n- Level 3 exposes input/output operations per second (IOPS).\n- Level 4 exposes all the available metrics.\n\nFor a detailed list of the available metrics for all statistics levels, see\n[Data collection levels](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-25800DE4-68E5-41CC-82D9-8811E27924BC.html).\n\nBy default, the statistics level is set to level 1. Levels 1 and 2 let you\ncollect partial data about your infrastructure, while level 3 lets you\ncollect everything you need to generate a complete total cost of ownership (TCO)\nreport.\nAfter the statistics level is changed in vCenter, it might take several\nhours for performance data to become available.\n\nFor more information on how to change statistics levels in vCenter, see\n[Configure statistics collection intervals in the vSphere client](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-5D85751A-2CE8-4FD5-83C8-90A17060631E.html).\n\n### VMs running on vCenter\n\nVMs running on vCenter must meet the following requirements:\n\n- You can add up to 100 vCenter sources (URL + inventory path).\n\n\u003c!-- --\u003e\n\n- The machine running the discovery client must be able to connect to your vCenter and ESX hosts. This includes opening all necessary ports in firewall rules and ensuring network connectivity between the discovery client host machine and target vCenter server and ESX hosts.\n- The vSphere vCenter server must be version 5.5 or later.\n- The vSphere vCenter server must support TLS version 1.2 or later.\n- The username you pass to the discovery client must have read privileges on one or more VMs. The discovery client is only able to discover information about VMs that are accessible to the specified user. The read privilege is typically assigned to all roles except for `No Access`.\n- The username you pass to the discovery client must have read privileges on the host ESX. If there are multiple ESX servers, then read privileges are required for every ESX that hosts a discovered VM.\n- The user running discovery client must have read, write, execute privileges on the machine running the discovery client.\n\nWhat's next\n-----------\n\n- Learn about the [installation requirements for the discovery client](/migration-center/docs/installation-requirements)."]]