HTML remote control (legacy)
HTML remote control was introduced in Ivanti® Endpoint Manager 9.5. Endpoint Manager 2018.1 replaced this HTML remote control version with an updated remote control engine designed around HTML 5 Web Sockets. For more information, see Remote control.
This legacy HTML remote control still works with in version 2018.1, though we recommend you use the new remote control for enhanced security and speed.
HTML remote control uses your browser as the remote control viewer. The HTML remote control viewer requires no software installation or browser plugins. After using the HTML remote control viewer, there's nothing to uninstall. This lets administrators easily start an HTML remote control session at someone else's desk if necessary.
HTML remote control works from most HTML 5 browsers, such as current versions of the following:
- IE 10 or later
You can run these browsers on any operating system they support and HTML remote control should work:
- OS X
- iOS and Android mobile devices
For more information on using HTML remote control, see Starting an HTML remote control session (legacy).
Enabling HTML remote control on managed devices
HTML remote control is part of the existing client remote control agent and it isn't enabled by default. Once you enable it, the client remote control agent hosts a small custom web server on port 4343. There are no extra programs to install or configure.
Enabling HTML remote control doesn't disable classic remote control. You also don't need to manually switch between remote control modes on clients. The remote control agent automatically detects which type of remote control session is being requested.
HTML remote control supports all of the same security models that classic remote control supports.
To enable HTML remote control
- Click Tools > Configuration > Agent configuration.
- Double-click the agent configuration you want to modify.
- On the Remote control page, click Configure.
- Select the remote control settings configuration that you want to modify, and then click Edit.
- On the general settings page, select Allow HTML access.
- Click Save and exit the dialogs.
- Redeploy the agent configuration you modified to managed devices.
After enabling HTML remote control and deploying updated agents (or agent settings) to managed devices, you'll have to wait for the devices to send an inventory scan before the right-click Network view menu shows an HTML remote control option. You can still remote control the device directly from a browser. For more information, see Starting an HTML remote control session (legacy).
Using remote control from a mobile device
A larger tablet or iPad mobile device works well with HTML remote control. Because mobile devices tend to have slower CPUs than desktop devices, your remote control sessions may have a slightly slower frame rate than an equivalent desktop HTML remote control session. Consider enabling grayscale mode to improve performance.
Older Android mobile devices may have older browser versions that won't work as well with HTML remote control. In particular, remote controlling another computer from a mobile device running an older browser and then letting the mobile device sleep while the session is active can cause the mobile browser to freeze. If this happens, you may be able to type a new URL for the browser to navigate to and that will release the HTML remote control page.
Multiple viewer support
HTML remote control allows multiple viewers to view the same target device. Any viewer can control the target, so you will want to choose one person to operate the remote mouse and keyboard.
The number of remote viewers is limited by the target device's CPU speed and available network bandwidth. Generally, up to three viewers will work acceptably. If you add more than that, you may notice framerate reductions.
Enabling grayscale mode may allow you to add more viewers because of the reduced network bandwidth requirements.