On this page

Show all

Help Center/ Migration Center/ Service Overview/ Collection Security/ Permissions and Principles for Data Collection over an Intranet

Permissions and Principles for Data Collection over an Intranet

Updated on 2025-02-17 GMT+08:00

View PDF

Permission requirements
- Windows: An account with administrator permissions is required.
- Linux: The root account is required.
Collection principle
- Windows: The MgC Agent accesses Windows servers through WinRM and runs a PowerShell script to collect server details.
  Linux: The MgC Agent uses SSH to access Linux servers. A PowerShell script is uploaded to /root/rda and then executed to collect server details.

Permission requirements: The MgC Agent can scan for servers on specific network ranges over the required ports. By default, port 3389 is required for Windows and port 22 is required for Linux. You can also specify a different port if needed.
Collection principle: After all IP addresses in the network range are listed, TCP connection requests are sent to each IP address over the required ports. If port 3389 is listened on, the IP address is used by a Windows server. If port 22 is listened on, the IP address is used by a Linux server.

Required permissions
- Windows: An account with administrator permissions is required.
- Linux: The root account is required.
Collection principle
- Windows: The MgC Agent uses the WinRM service to remotely access Windows servers, securely transfer a PowerShell script to the C:/Edge-Scripts directory of Windows servers, and executes the script to automatically collect server details.
- Linux: The MgC Agent uses SSH to access Linux servers. A Shell script is uploaded to /root/rda directory and then executed to automatically collect server details.

Required permissions: An account with full permissions is required to ensure that all necessary data can be accessed. The required account depends on the database management system.
- MySQL: root
- PostgreSQL: postgres
- MongoDB: admin
- Oracle: system
- SQL Server: sa
Collection principle: Source databases are connected, and query statements are sent to collect database details.

Required permissions
- Redis: A general account with basic access permissions is required.
- Kafka: An account with the permissions to access all topics and topic information is required.
Collection principle: Data is collected through the Java applications integrated with middleware SDKs. These applications interact with middleware through the methods and APIs provided by the SDKs.

Permission requirements: An administrator account is required to export files that contain necessary access credentials.
Collection principle: Kspider is used to collect data.

Permission requirements: An administrator account is required. This account must have full access permissions to all VMs managed by the vCenter Server.
Collection principle: The vSphere SDK is used to list VMs and collect their details.