Advanced Discovery configuration You can configure several additional components of Discovery such as Application Dependency Mapping, the ECC queue, and extensions for the MID server. Credential-less Discovery with NmapIf the instance fails to identify a configuration item (CI) because of authentication failure, Discovery or Service Mapping can run selected Network Mapper (Nmap) commands with a MID Server to collect some basic information about the CI without using credentials.PowerShell for DiscoveryPowerShell is built on the Windows .NET Framework and is designed to control and automate the administration of Windows machines and applications.Application Dependency Mapping (ADM) for DiscoveryApplication Dependency Mapping (ADM) discovers CIs by detecting TCP connections between devices.vCenter event collectorThe vCenter event collector is a MID Server extension that listens for vCenter-related events and updates the CMDB accordingly.SNMP trap collector extensionThe SNMP trap collector is a MID Server extension that listens for SNMP traps from the devices on your network.Discovery behaviorsDiscovery behaviors determine the probes that Shazzam launches, and from which MID Servers these probes are launched. CI deletion strategies for pattern discoveryWhen you perform discovery with a pattern, you can choose what to do with certain CIs that Discovery can no longer find. Configuration file trackingThe horizontal discovery process can find configuration files that belong to certain applications and add those configuration files to the CMDB. You can track the changes to these files by comparing them to previous versions.Change the source name of Discovery resultsYou have the option of changing the source name of discovery results. This might be desirable if ServiceNow® Discovery is running on your network together with another discovery product, and you want to use customized identifiers.