Overview

The Remote POS Device Manager (Also known in engineering as the RMR or WindwardPOS.exe).  This technology uses .NET framework as part of the technology stack required for our software to communicate.  We can alternatively change the communication to use a virtual channel using TCPIP.

This configuration may be required for workstations experiencing WindwardPOS.exe crashing or disconnecting from PINpad devices. 

This setup will only function on a 64-bit Windows operating system.

Configure Virtual Channel in Remote POS Device Manager

  1. Open the Remote POS Device which can be found in the status bar. 
  2. Navigate to the Remote Desktop Tab
  3. Set the communication mode:
    • Enable “Listen - RDP with VPN or workstation has fixed external IP”
    • Server: localhost
    • Port: 35888
    • If these settings are grayed out, Set the Connection Mode to “Connect - Server has fixed external IP”, make the changes to the port and server, then set it back to “Listen - RDP with VPN or workstation has fixed external IP“
  4. Turn on Enable Remote Desktop Devices
    1. image
  5. Right-click on WindwardPOS device manager icon in the local machine system tray to register RDP Virtual Channel
    • *** - Need to search for WindwardRDP.dll on local computer. You will be asked for this file when you register the Remote POS Device Manager.
  6. Connect to System Five on Cloud.
  7. Log into System Five on the Remote Machine
  8. Navigate to Setup Wizard, Point of Sales Devices, Device Options
  9. Enable RDP Virtual Channel in Use Point of Sale Manager, Port: 35888


Troubleshooting

Note that older versions of the WindwardPOS Device Manager can have both Virtual Channels and Message Relay configured. This will still cause WindwardPOS to crash as it will be using .NET technology to communicate. 
Ensure Use Message Relay checkbox is disabled.
image


Other Troubleshooting

  • Check on-premise threat protection or Virus software.  You can try to white list WindwardPOS.exe 
  • Ensure the workstation is not running Windows Home edition.  Conflicts with Windows Defender can cause connectivity issues.
  • Older versions of the POS Device Manager required the executable to be run as administrator once to create registry entries.  Otherwise it may prompt for Administrator rights each time.