Interactive Probe Shell runs separately from UNIX - Classify when discovering a Network Range - Causes duplicate device history records and unwanted messages in the Discovery LogDescriptionInteractive Probe Shell runs separately from UNIX - Classify when discovering a Network Range - Causes duplicate device history records and unwanted messages in the Discovery Log. The purpose of this JavascriptProbe SSHTerminalInteractiveCommand probe is to look for Citrix OS Unix for Citrix NetScaler SDX devices, which is a hardware-based Application Delivery Appliance. This then triggers Unix Classification “Netscaler FreeBSD”, which launches the "Citrix NetScaler SDX pattern". This is not done in traditional way, as a probe within the UNIX - Classify multiprobe, which is how we have done it for F5, ESX and others. This was added in Quebec, and uses the new Multi Classification feature, to avoid the cases where if a sub-probe in a MultiProbe fails, the whole probe fails.Steps to Reproduce Create a Discovery Schedule with a wide Network Range.Run Discovery.During or after Discovery is completed, notice the "Name of unclassified CI is ___" messages in the Discovery Log, coming from a ECC Queue Input of JavascriptProbe SSHTerminalInteractiveCommand, even though that CI will probably be properly discovered by the UNIX - Classify probe.In the ECC Queue tab, you should see multiple records for the SSHTerminalInteractiveCommand as well.Discovery Device History will show duplicate records for the same Source IP. e.g. "UNIX - Classify - Updated CI", and also "Interactive Probe Shell - Active, couldn't classify" records.WorkaroundThis problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this article to be notified when more information becomes available. There are two choices for a workaround: Ignore the logs/device histories as they are expected behavior and are not harmful.If customers are not discovering Citrix Netscaler devices within their network, they can disable/remove the "Interactive Shell Probe" from the SSH port probe. This will prevent the creation of the discovery logs/device histories described by the PRB.Related Problem: PRB1495230