I’m trying to remote control a Windows desktop from Hexnode. The device is enrolled and has the Hexnode UEM app installed, but I don’t see how the Hexnode Remote Assist app gets installed on the target device. When I go to Remote View/Control for the Windows device, I can’t start a session. What needs to be enabled for this to work?
- Home
- Remote Actions
- Cannot start Windows Remote View/Control until Remote Assist installs
Cannot start Windows Remote View/Control until Remote Assist installsSolved
Replies (5)
For Windows remote view/control, the Hexnode Remote Assist app must be installed on the target device in addition to the Hexnode UEM app. Check the following first:
- Go to Admin > General Settings in the Hexnode console.
- Under Remote View & Control Settings, enable:
– Enable Remote View
– Enable Remote Control - Under Hexnode App Updates, enable the option to install/update the Hexnode Remote Assist app on Windows devices.
- Save the changes.
On the target Windows device, also ensure that Remote View and Remote Control permissions are enabled inside the Hexnode Remote Assist app.
After this, go to Manage > Devices, select the Windows device, and try Remote View/Control again. You can choose either User level access or System level access when starting the session. System level access is required if you need to interact with UAC prompts or system-level screens.
I had the same issue. The admin setting was already enabled, but the device only showed Hexnode UEM installed. The Remote View/Control option was there, but the session wouldn’t start.
If the Remote Assist app has not installed automatically yet, you can trigger it manually from the device page:
- Go to Manage > Devices.
- Open the affected Windows device.
- Go to Device Summary > Enrollment Details.
- Find Hexnode Remote Assist and click Trigger.
- Check Action History and confirm that the Install Application action changes to Success.
You may briefly see a status similar to “Installation initialized” while the installation is being pushed. Once the Remote Assist app installation is completed, the device should show it as installed and the remote session can be started.
That worked for me. After clicking Trigger, it first showed installation initialized, then changed to installed. Remote View/Control started working after that.
If you want to start future remote view sessions without requiring the user to approve the prompt on the Windows device each time, configure Unattended Remote Access:
- Go to Policies.
- Create a new policy or edit an existing one.
- Navigate to Windows > Troubleshooting > Unattended Remote Access.
- Enable the available unattended remote access options.
- Add the target Windows device under Policy Targets and save the policy.
After the policy is applied, supported remote sessions can be initiated without user intervention on the device.