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 Client Edge Migration: Don't Forget Your OS Imaging Pipeline
This is a companion piece to our earlier post, Tanium Cloud Client Edge Server Names Are Changing — Here’s What to Do. If you haven’t read that one yet, start there for the full overview of the migration.
You’ve run the Client Edge Migration Status dashboard, updated your ServerNameList, and watched your endpoints move to Complete. You’re done, right?
Not quite. There’s one area that’s easy to overlook: any process that installs a fresh Tanium Client onto a newly provisioned endpoint.
If your imaging or provisioning pipelines still reference the legacy zsb1/zsb2 server names, every new endpoint you build will ship with a stale configuration. Once the legacy server names are decommissioned, those endpoints won’t register with Tanium Cloud.
Where to look
Audit anywhere in your build and provisioning chain that installs the Tanium Client. Common places to check include:
Any OS images managed through Tanium Provision should be reviewed and rebuilt with an updated Tanium Client installer that already targets the new Client Edge URLs. Confirm that the bundled installation parameters reference the new FQDNs and not the legacy ones.
For every imaging or provisioning workflow that installs the Tanium Client, make sure of the following:
If you would like a second set of eyes on your imaging and provisioning workflows, contact your Chuco consultant for assistance with this project. We are happy to walk through them with your team — including reviewing your Tanium Provision images, MECM task sequences, or any custom installer scripts you use to onboard new endpoints — and to validate that your refreshed images and pipelines register cleanly against the new Client Edge URLs.
If you don’t have a direct contact at Chuco yet, you can also reach us through chuco.com/contact.
Primary Tanium documentation for the Client Edge URL migration:
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.