-
Notifications
You must be signed in to change notification settings - Fork 10
Settings
- Start with Windows
- Should Duo automatically started on boot? This setting will be turned off, when you install a new version of Duo.
- Isolate HID devices
-
Isolation of Mouse and keyboard inputs is compulsory by design. With this toggle you can control isolation of other HID devices, like gamepads for example. If you turn this off, gamepad input from the host system will bleed into your remote Duo sessions – if this is what you want.
Without process patching the isolation is solely achieved by setting the Session ID property on the device. While this will work for many use-cases, some setups will also need Process Patching to achieve full isolation, including but not limited to:
- Bluetooth Gamepads
- Enable Process Patching
-
Enabling this installs an Application Compatiblity Database, which is a native Windows feature that allows us to apply patches to various Games and Windows components to improve general compatibility with Duo and the level of isolation. This is needed for the following use-cases:
- Bluetooth Gamepad isolation
- Games that check if running in a remote session (and complain)
- Steam isolation (see below)
⚠️ While this has been tested thoroughly, there may still be some edge cases left, which could compromise system stability. Use this at you own risk. - Isolate Steam
- The Steam client only allows to be started once per system. With this setting enabled, additional patches are applied to hide one Steam instance from another. Without this patch, starting a new instance of Steam will terminate any other instances. Only disable this, if you have problems using Steam.
You can control Duo remotely via the Web User Interface, by navigating your web browser to http://localhost:38299 (default settings, replace localhost with the name of your computer).
- Web User Interface Port
- Only change the port if there is a conflict with another network service on your computer.
Duo writes to the Windows Event Log about internal events, like stopping and starting an instance for example.
- Verbosity
- This allows you to control the level of detail. The default is 'Information'. Select 'Debug' to help us analyse an error situation.