It is important to understand this information before installing WebTitan OTG for Windows.
A single installation of WebTitan OTG for Windows creates the following on WebTitan:
a device in Environment > Devices that represents the client machine that OTG is installed on, e.g. a user's laptop. A device is any entity that can be configured to send DNS requests to WebTitan for filtering per your policies.
a virtual location in Environment > Locations.
a user in Environment > Users based on the Windows username of the machine it is installed on, e.g. user@USER-PC.
Before installation, you can edit the global device configuration in WebTitan from Settings > Device Configuration to specify a policy that is assigned at installation. This is useful if you want to apply a particular policy you have created to a set of users, such as the Sales Department or Engineering Department.
Example: You are rolling WebTitan OTG for Windows out to your Sales and Engineering staff and want to apply a different policy to each group.
In this case, change the policy in the global device configuration to your Sales Department policy, e.g. OTG-sales-dept, and then carry out the installation for your sales staff. Once installation is complete and you have verified the users (sales staff) have been added to WebTitan, change the policy in the global device configuration to your Engineering Department policy, e.g. OTG-eng-dept, and carry out the installation for your engineering staff.
WebTitan OTG for Windows allows you to edit a device's configuration in WebTitan after installation. This can be done globally for all devices on WebTitan, or individually for a single device. See Managing OTG Devices on WebTitan.
This guide describes a command-line installation for OTG for Windows. As part of the installation, you need to create a command script. The installation instructions provide a sample script that you can edit with your own parameters. See OTG Installation Parameters.
When serving a block page, WebTitan determines the requesting customer’s details via an IP mapping done over HTTP/S, with no reference to the original UDP DNS request. When virtual locations are used (as with OTG), there is no such direct mapping and the default block page at the WebTitan admin level is returned, providing generic block page information rather than specific per-customer information. Therefore, if using OTG, it is recommended to keep your WebTitan admin-level block page as generic as possible.
Any software that redirects DNS requests may interfere with OTG's ability to filter your DNS traffic.
For example, components such as “Secure DNS” in AVs, like AVG and AVAST are not compatible with WebTitan Cloud/OTG, as they send DNS requests via an encrypted connection between your web browser and their own DNS servers.
In many cases, the component features causing the conflict can be disabled within the product's UI.
VPNs vary widely depending on their environment and configuration. In some cases, additional configuration may be required to use OTG 2. There are also a number of VPNs with known conflicts.