A Simpler Way to Execute Tasks in Tanium
You can’t secure what you can’t see — but what happens when the tools providing that visibility are the ones failing? We took that question to Tanium Atlas.
Tanium Cloud Client Edge Server Names Are Changing — Here's What to Do
This applies to Tanium Cloud customers only. If you’re hosting Tanium on-prem, this change doesn’t affect you.
What are Client Edge server names and why does this matter?
The Client Edge server name is the address that managed Tanium Clients use to connect with your Tanium Cloud instance. Making this change before the Tanium deadline is required to maintain connectivity between your managed endpoints and your Tanium instance.
Tanium is updating the Client Edge server names that endpoints use to communicate with Tanium Cloud. The legacy zsb1/zsb2 format is being replaced with zs1/zs2, and the old server names will be retired starting in July.
Does this affect you?
Go to Data > Dashboards and search for “Client Edge Migration Status.” If the Action Required panel shows 0, no changes are needed for your environment. You can view your current Client Edge URLs in your Tanium Cloud administration settings.
The dashboard provides recommended actions for Windows and non-Windows endpoints. It updates your ServerNameList setting and moves endpoints through three phases: Not Started → In Progress → Complete. For more details on the migration process, see the Client Edge Migration community article.
A few recommendations:
Select a Tanium Deployment plan that matches your preferred ring-based update schedule to ensure coverage across endpoints that may not be online at the same time.
Endpoints on Client 7.6.2 or later will automatically prioritize the new URLs and should reach Complete within about four hours. If they stay at In Progress past that, review them manually.
Endpoints on Client versions earlier than 7.6.2 don’t support priority prefixes, you’ll need to upgrade those Clients or remove the legacy FQDNs from their ServerNameList. For guidance on connecting endpoints, see the Tanium Client Management User Guide.
If you run into error statuses on specific endpoints, Tanium’s Client troubleshooting guide covers common Client health issues.
Before starting, confirm that ports 17472 and 17486 are open from your endpoints to the updated URLs.
From our team: We had to refresh the client bundle in our NFR environment before the new names appeared. If you’re not seeing the updated URLs, try that first.
Timeline:
Can’t complete by June 30? Open a case through the Tanium Resource Center.
You can’t secure what you can’t see — but what happens when the tools providing that visibility are the ones failing? We took that question to Tanium Atlas.
You can’t secure what you can’t see — but what happens when the tools providing that visibility are the ones failing? We took that question to Tanium Atlas.
When a $30 billion dollar transportation company with 10,000 endpoints and hundreds of servers adopted Tanium, they realized that improving their patching capabilities, efficiency and overall compliance levels could have a significant impact on their ROI. Tanium introduced them to Chuco, and we got moving fast.