Windows Deployment for OTserver Scanner

Prerequisites

Install the bundled, unmodified Win10Pcap package only when explicitly requested and approved. Select the physical adapter by its interface name or GUID. The scanner never creates a TAP adapter or Windows Network Bridge. Without Win10Pcap, pktmon provides passive PROFINET observation but cannot transmit DCP Identify.

Build and inspect the scanner

Build the Windows target and inspect interfaces:

1
2
3

cargo build --release --target x86_64-pc-windows-msvc
.\target\x86_64-pc-windows-msvc\release\otserver-scanner.exe doctor
.\target\x86_64-pc-windows-msvc\release\otserver-scanner.exe interfaces

Windows scan

1
2
3
4
5
6

.\otserver-scanner.exe scan `
  --target 192.168.1.0/24 `
  --interface '<interface name or GUID>' `
  --source-mac 00:11:22:33:44:55 `
  --output .\scan.otserver.json `
  --ack-authorized

Use --no-profinet when the site only authorizes routed protocol probes, and keep the explicit --ack-authorized flag in every manual or scheduled scan.

The Windows GUI provides the same target, interface, source MAC, output, protocol, and authorization controls. Use it instead of the CLI for an interactive scan.

Verify the result

Run validate on the JSON and inspect the warnings before importing. Confirm that the selected adapter is the intended physical interface.

Plan scanner placement in a plant or read the PROFINET guide.