In Kingston Patch 10, Shazzam will scan for WinRM over SSL using a new scanner HTTPS. This scanner uses a socket connect time out of 20 seconds. When discovering a large subnet which is sparsely populated, the discovery duration may be significantly impacted by this timeout.

Steps to Reproduce

We were able to reproduce the defect under the following conditions:

  1. Start Discovery on a large subnet with many unassigned IPs.
  2. Observe the probe time of the Shazzam probes.
  3. The probe time now takes multiple times longer compared to the same Discovery prior to upgrade to KP10.


To switch from HTTPS to HTTP, use the following process.  This will remove the long time delays, providing a workaround until the instance can be upgraded to a release with the fix.

  1. Navigate to Discovery Definition->Port Probes
  2. Select record winrm_ssl
  3. Change the Scanner field to HTTP (Web Server)

Related Problem: PRB1315398

Seen In

Kingston Patch 10

Intended Fix Version


Fixed In

Kingston Patch 11

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-12-15 07:51:25