Configuring the connection with Tanium Server
The Tanium™ Client initiates connections to the Tanium Server, so the connection setting is on the client.
The ServerName setting is configured during installation using any of the deployment tools and techniques described in this guide. The Tanium Client attempts to connect to the fully qualified domain name (FQDN) or IP address specified in the ServerName setting. In Tanium Core Platform 7.2.314.3263 and later, you can optionally set the port that the Tanium Client uses to communicate with the Tanium Server by appending :<port_number> to the ServerName (for example, ts1.local.com:12345). The ServerName port overrides the ServerPort setting in the Tanium Client configuration (default is 17472).
In HA deployments, you configure the ServerNameList setting. Specify a comma-separated list of FQDNs or IP addresses. When ServerNameList is populated with multiple names, the Tanium Client must select one each time the Tanium Client processes is restarted or client registration is reset. The result of the evaluation is written to the ServerName setting, and it is this value that is used in the connection request to the Tanium Server.
The order in which servers are listed does not matter, and there is no weight. The Tanium Client selects a server from ServerNameList at random. The Tanium Client does maintain a count of failed connection attempts, and preference is given to the server with the least failed connections.
In Tanium Core Platform 7.2.314.3263 and later, you can optionally set the port that the Tanium Client uses to communicate with Tanium Servers by appending :<port_number> to the Tanium Server IP addresses or FQDNs (for example, ts1.local.com:12345,ts2.local.com:12345). ServerNameList port values override the ServerPort setting in the Tanium Client configuration (default is 17472).
For the last successful client-server connection, the Tanium Client stores the name of the Tanium Server and the port. If the client cannot reach the server configured in ServerName, it attempts to connect to the value contained in LastGoodServerName. You do not set LastGoodServerName.
Tanium Initial Content pack includes sensors and packages that can be used to manage the ServerName value and ServerNameList value on Tanium Client host computers.
|Sensors||Tanium Server Name||
Return the current value of ServerName from the configuration on the client.
get computer name AND Tanium Server Name from all machines
|Tanium Server Name List||
Return the current value of ServerNameList from the configuration on the client.
get computer name AND Tanium Server Name List from all machines
|Packages||Set Tanium Server Name||Set the ServerName value in the Tanium Client Windows registry and restart the Tanium Client Windows service.|
|Set Tanium Server Name List||Set the ServerNameList value in the Tanium Client Windows registry and restart the Tanium Client Windows service.|
|Set Tanium Server Name [Non-Windows]||Set the ServerName value in the TaniumClient.ini file and restart the Tanium Client system service.|
|Set Tanium Server Name List [Non-Windows]||Set the ServerNameList value in the TaniumClient.ini file and restart the Tanium Client system service.|
The following example shows how to use these objects to set ServerNameList on Tanium Client host computers in a common scenario: a second Tanium Server was added to the deployment after the Tanium Client had already been deployment.
To update ServerNameList:
- In Interact, ask the question:
get computer name and server name list from all machines
- Review the results grid.
- Select the rows for the computers that need the values set and click Deploy Action.
Interact displays the Deploy Action page.
- In the Deployment Package section, select the Set Tanium Server Name List package and set values.
- Set a schedule.
- Set targeting criteria.
- Click Deploy Action.
- Review the status.
- Go to Administration > Question History.
- Find the question, select it, and click Load.
- Review the results grid and verify that ServerNameList has been populated on the targeted endpoints.
Last updated: 4/18/2019 8:15 AM | Feedback