NetSpeek Windows Runtime Service Integration Guide

This document serves as a comprehensive guide that outlines the steps required to integrate Windows OS devices instrumented with the NetSpeek Windows Runtime Service (NWRS) with the NetSpeek platform.

This device type uses a concept called “sub-connection” which means that the Edge VM uses another component to reach orchestrated devices. In the case of this sub-Connector, that component is the NetSpeek Windows Runtime Service being used to orchestrate a Windows OS device.

Prerequisites

Before beginning, confirm the following:

Terminology change, October 2026

The device and tenant level “Connector” configurations were previously called “Integration” and have been renamed in both the NetSpeek portal interface, and NetSpeek Docs.

Note

Traffic is relayed from Edge VM → Windows OS device → NWRS software (and the reverse path for responses). The final Windows-NWRS step takes place within Windows, not over an IP network connection.

Step 1. Create Sub-Connection (Tenant-Level)

Sub-Connection Configuration

This step assumes an Edge VM is already deployed – the sub-connection is added as a configuration parameter to the Edge at the tenant level.

  1. Ensure you have selected the desired tenant/sub-tenant with the selector in the upper left of the portal interface, and click “Connectors” in the Platform configuration list at the lower left.
  2. Click “+ Add Connector“
  3. Choose the NetSpeek Windows Runtime Service Connector type.
    • Note that for Connectors where a sub-connector applies (and only those Connectors), a “Parent Connector” field is shown.
  4. Select the appropriate NetSpeek Edge VM to serve as the parent.

Note that the Tenant Id and Admin User Email parameters are required in all deployment paths.

If using the Sync with Intune deployment path, the Entra Group Id value is also required.

See the individual-PC guide, or the Intune guide, for Windows OS installation details regarding your specific deployment path.

Step 2. Add Device to NetSpeek Room Canvas

Device Provisioning Flow

  1. From a new WorkSpace, select Locations and search for or navigate to the Room the device will reside in.
  2. Select the room you wish to add your NWRS-orchestrated Windows PC to
  3. The Room Canvas opens by default.
  4. Click “Add Devices” and then “Create new“
  5. For most use cases, choose Generic in the Manufacturer list, and Room Compute – Windows from the device model list.
  6. Configure the appropriate values, and in the “Connectors” section, select the previously created NetSpeek Edge VM sub-Connector from Step 1. Ensure that the Edge VM is on a network that can reach the Windows PC’s configured IP address. Configure the following:
    • Device Name
    • Serial Number
    • IP Address or Hostname of the Windows PC

Verification

Once the relevant settings described above are configured, to validate the Connector:

  • Select a NWRS-orchestrated Windows OS device in the NetSpeek console, open the Device Actions Tab, and select an available device action. It is generally advisable to test by dispatching a non-intrusive command such as a Get Status.
  • On the device, observe the selected action occurring.

Troubleshooting

Network / Connectivity Issues

  • Confirm the IP address on the NWRS-orchestrated device is correct and routable from the network segment where the NetSpeek Edge VM is deployed.
  • Ensure port TCP 443 (or your configured listening port) is not blocked by firewall rules on the Windows PC where your NWRS instance is installed.

Support

If you run into any issues during onboarding or have questions, contact NetSpeek Support at support@netspeek.com.