When basic WMI connectivity works but specific classes fail, it’s typically a permissions issue. The account used by the MID Server needs explicit permissions (like Enable Account and Remote Enable) not just for WMI generally, but for the specific namespace (e.g., root\cimv2) and potentially the class being queried. The other options are less likely as the probe is connecting (ruling out service stoppage or IP range) and Java version issues would typically cause broader failures.

The ‘host_name’ attribute discovered from the system is the primary source used to populate the CI’s ‘Name’ field. While the FQDN is also discovered, the ‘Name’ field is typically set from the shorter hostname. ‘sys_class_name’ defines the CI class (e.g., cmdb_ci_linux_server), and ‘ip_address’ populates the IP address field, not the Name.

For SNMPv3 authPriv, both authentication (for data integrity and origin verification) and privacy (for encryption) passwords must be provided. While the authentication and privacy protocols (like SHA and AES) also need to be selected, the question asks for the mandatory *fields* to configure. The passwords are the essential credentials. Security Level is a setting (e.g., authPriv) and Security Name is the username, but without both passwords, discovery will fail at the authPriv level.

The ‘Runs on’ relationship is typically established by the entry point sensor (like a process or port sensor). Within its configuration, the ‘Related CI’ field must be mapped correctly, often using a reference qualifier like ‘javascript:getLinuxServer()’ or similar, to identify the hosting server CI. If this mapping is incorrect or missing, the relationship won’t be created. The probe sensor identifies the CI, but the entry point links it.

The Win32_BaseBoard WMI class contains information about the motherboard, including its serial number (SerialNumber property). Win32_BIOS provides BIOS info, Win32_ComputerSystem provides model and manufacturer, and Win32_SystemEnclosure would provide the chassis serial number. The discovery behavior indicates the probe is querying Win32_BaseBoard for the serial number data.

The Shazzam probe is used in the horizontal phase of discovery. Its job is rapid, lightweight scanning of IP ranges (using ICMP ping and port scans) to identify which IPs are alive and what ports are open. This creates ‘tentative’ CIs and determines which vertical probes (like SSH, WMI, SNMP) should be used for deeper investigation. It does not use credentials or perform deep interrogation.

The ‘MID Server > Servers’ module provides a list of all configured MID Servers. This list shows key status columns like ‘Status’ (Up/Down), the last heartbeat timestamp, and the version. It is the direct administrative view for monitoring MID Server health. ‘Discovery > Runs’ shows discovery execution history, ‘Schedules’ shows schedule configurations, and the ‘MID Server Queue’ is for debugging message traffic.

For non-standard ports, you must specify the port in the credential record (so the MID Server knows which port to use for SSH) and often in the probe parameters or a specific sensor if the standard SSH probe expects port 22. The credential tells the system *where* to connect, and the probe parameters define *how* to connect for that protocol. The CI record port is informational, and the schedule IP range doesn’t specify application ports.

Relying solely on a port is not a robust classification method. The best practice is to add a verification sensor (like a Telnet or TCP sensor) that connects to the port and checks for a unique identifier—such as a specific banner string in the response or the result of a diagnostic query (e.g., a database version command). This positively identifies the service, not just the port. A process name check is good but may not be accessible without credentials.

When basic WMI connectivity works but specific classes fail, it’s typically a permissions issue. The account used by the MID Server needs explicit permissions (like Enable Account and Remote Enable) not just for WMI generally, but for the specific namespace (e.g., root\cimv2) and potentially the class being queried. The other options are less likely as the probe is connecting (ruling out service stoppage or IP range) and Java version issues would typically cause broader failures.0