Delen via


WSD Scan Discover

This automated test verifies that a Web Services on Devices (WSD) scan device responds to "Probe" and "Resolve" multi-cast Web Services for Scanner (WS-Scan)-Discovery messages according to the Device Profile for Web Services protocol document. The "Probe" filters on the ScanDeviceType and the "Resolve" message filters on the Device UUID.

Note

   For WS-Discovery details, visit WS-Discovery Specification Compliance. For WS-Scan details, visit Scan Service (WS-Scan) Schema.

 

The test first performs the "Probe" WS-Discovery operation filtered by ScanDeviceType. The second and final test is the "Resolve" WS-Discovery operation based on the device WSD ID. Both test cases will timeout if the device does not respond within 60 seconds.

Test details

   
Specifications
  • Device.Imaging.Scanner.WSD.WSScan
Platforms
  • Windows 10, client editions (x86)
  • Windows 10, client editions (x64)
  • Windows Server 2016 (x64)
Supported Releases
  • Windows 10
  • Windows 10, version 1511
  • Windows 10, version 1607
  • Windows 10, version 1703
  • Windows 10, version 1709
  • Windows 10, version 1803
  • Windows 10, version 1809
  • Windows 10, version 1903
  • Next update to Windows 10
Expected run time (in minutes) 2
Category Compatibility
Timeout (in minutes) 120
Requires reboot false
Requires special configuration false
Type automatic

 

Additional documentation

Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s):

Running the test

Before you run the test, complete the test setup as described in the test requirements:Scanner Testing Prerequisites.

In addition, this test requires the following:

  • For versions of Windows Server, the "Desktop Experience" Feature must be installed.

  • The "Network Discovery" firewall exception must be enabled on the test host.

Warning

   The device must be on the same subnet as the test host. It does not have to be installed.

 

Troubleshooting

For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.

For troubleshooting information, see Troubleshooting Device.Imaging Testing

Multicast network traces will be needed to determine the root cause of any failures.

More information

Parameters

Parameter name Parameter description
LLU_LclAdminUsr LUA Local Admin User
LLU_NetAccessOnly LUA Network Access Only User
WDKData_WSDID Device UUID (i.e. urn:uuid:11111111-2222-3333-4444-555555555555)