Connecting directly to a device without using a Management Console
This method is NOT compatible with the use of the PreConnect setting.
1. The WLRemoteControl.exe is actually a part of the RC client (not the Server).
2. Download & save WLRMTCTL_4_1_3_001.AVA without adding it to a Management Console:
3. WLRMTCTL_4_1_3_001.AVA is an archive file and needs to be opened with compression software
before the files inside can be accessed. Windows, OS X, and Linux all come with ZIP compression
built-in to the operating system, or you can use third-party programs to access them.
To extract, rename client WLRMTCTL_4_1_3_001.AVA to WLRMTCTL_4_1_3_001.zip.
4. Extract the .zip file.
5. Once extracted, the WLRemoteControl.exe can be located here:
6. Create a folder and place the WLRemoteControl.exe in it by itself.
7. To execute the WLRemoteControl.exe launch the Windows Command Line Interface (CLI)
and navigate to WLRemoteControl.exe.
8. To execute the WLRemoteControl.exe use the following CLI command:
wlremotecontrol.exe /action:view /connect:tcpip /device:IPAddress of the target device
9. If the Remote Control Server is Local to the CLI command connection attempt,
the RC session will begin.
10. If the Remote Control Server is NOT local to the CLI command connection attempt,
then you will be prompted for the Remote Control Server’s Address (On the first attempt only).
11. Enter the Server IP address being used and Port 1900.
12. Remote control to devices via IP is established.
13. Remember If you are using preconnect the above connection method does not work.