https://docs.titanhq.com/en/3083-downloading-and-installing-otg-for-windows.html
setup.msi /quiet /qb WTC_SERVER_URL=https://ofekcloud.webtitancloud.com:8443 DNS_RESOLVER=3.120.167.161,3.121.248.116 CUSTOMER_EMAIL=DDD@ofEEEkDDCd.com CUSTOMER_PASSWORD=XXXXX FORWARD_DOMAIN=true
customers will need to change the "customer_email" and "customer_password"
Optional OTG additional Parameters:
When creating your command line script for installing OTG, as well as the four required parameters there are also several optional parameters which you can use:
Parameter | Description |
---|---|
LOCATION_NAME | When creating a roaming location, OTG assigns the Windows or Mac computer name by default. To change this you can specify a LOCATION_NAME value. LOCATION_NAME should not be used if installing multiple OTGs, as the roaming location names must be unique. Example: |
LOCATION_NAME_SUFFIX | If specified, a LOCATION_NAME_SUFFIX is appended to the LOCATION_NAME and separated using '@', e.g LOCATION_NAME@LOCATION_NAME_SUFFIX LOCATION_NAME and LOCATION_NAME_SUFFIX should not be used together if installing multiple OTGs, as the roaming location names must be unique. Example: |
BYPASS_IPS | A remote user may visit a location (e.g. main office) which is also using WebTitan Cloud or any other internal filtering solution for filtering. In this case, you may want OTG to be disabled while there. To do this, the office's public facing IP can be added to a list of bypass IP when OTG is installed. When the user leaves the office, OTG will detect the IP change and start filtering again. When OTG is in bypass mode, the OTG tray icon will show "status: ignored". To bypass multiple IPs (e.g. several locations) use a comma to separate them: Example: To bypass a range of IPs use a hyphen to separate the two addresses: Example: |
TRAY_TYPE | Controls the WebTitan Cloud OTG information, logo and popup notifications in the Windows system tray or macOS menu bar. Values can be:
Example: |
DYNAMIC_FORWARD | Used conditionally forward requests for particular domains to specific DNS servers, based on the current external IP address. This is useful if you want to treat domains differently depending on where the user is, e.g. if a company's internal domain is the same name as its external domain and where access to the local office resources are impacted if routed externally. The format is: DYNAMIC_FORWARD= [site]@[external IP]-[Resolvers, …]; Example: When external IP is and When external IP is |
FORWARD_DOMAIN (this option is if the customer has network mapping with DNS name) | Unconditionally forward any requests for the local domain to a local DNS server (rather than to WebTitan Cloud). If enabled, on startup OTG will attempt to get the name of local domain and will store the DNS settings provided, for example by the DHCP server of that local domain. When OTG detects requests for the local domain (or subdomains), it doesn't send them to WebTitan Cloud, but to the stored IP of the local DNS server. Can be set either true or false, e.g. |
RPC_PORT | Allows OTG to specify a port for communication with WebTitan Cloud other than the default 7771. NoteIf this parameter is supplied, private cloud WebTitan Cloud servers must also be configured to listen on the port specified. Example: |