Tanium Patch – Remediation Scripts
Tanium Patch – Scripts
A collection of remediation and automation snippets used for fixing Patch issues on endpoints.
These scripts support troubleshooting findings from:
-
Patch – Coverage Status Details
-
Patch – Scan Age
-
Patch – Scan Errors
-
Patch – Is Process Running
-
Endpoint Configuration – Tools Status Details contains patch
1. Windows Remediation Scripts
1.1 Restart Tanium Client (Fix stale scans or [no results])
Use when:
-
Patch process is not running
-
Scan Age = stale
-
Scan Errors not returning
-
Coverage Status = Needs Attention
# Restart Tanium Client on Windows
$svcNames = @('TaniumClient','Tanium Client')
foreach ($name in $svcNames) {
$svc = Get-Service -Name $name -ErrorAction SilentlyContinue
if ($svc) {
Write-Host "Restarting service: $($svc.Name)"
Restart-Service -Name $svc.Name -Force -ErrorAction Stop
}
}
1.2 Force Patch Tools Redeploy (tools missing or corrupt)
Use when:
-
Tools Status =
[no results] -
Patch engine not running
-
Coverage: Needs Attention due to tool issues
# Force redeploy Patch Tools by removing the local tools directory
$patchToolsPath = "C:\Program Files (x86)\Tanium\Tanium Client\Tools\Patch"
if (Test-Path $patchToolsPath) {
Write-Host "Stopping Tanium Client..."
Stop-Service -Name 'TaniumClient' -ErrorAction SilentlyContinue
Write-Host "Removing Patch tools directory..."
Remove-Item -Path $patchToolsPath -Recurse -Force
Write-Host "Starting Tanium Client..."
Start-Service -Name 'TaniumClient'
Write-Host "Patch tools removed. Tanium will redeploy automatically."
}
else {
Write-Host "Patch tools directory not found: $patchToolsPath"
}
1.3 WMI Verification & Repair (fix scan errors on Windows)
Use when:
-
Scan Errors indicate WMI or inventory issues
-
Scan Age will not refresh
# Verify & salvage WMI repository
Write-Host "Verifying WMI repository..."
winmgmt /verifyrepository
Write-Host "Attempting to salvage repository..."
winmgmt /salvagerepository
⚠️ Important:
Use winmgmt /resetrepository Only under change-control—it resets WMI completely.
1.4 Endpoint Network Connectivity Check (catalog download issues)
Use when:
-
Scan Errors indicate catalog download problems
-
Patch Tools keep failing to initialize
# Adjust hostname to your environment
$taniumServer = "tanium.domain.com"
Test-Connection -ComputerName $taniumServer -Count 4
Test-NetConnection -ComputerName $taniumServer -Port 174721.5 Windows Quick Patch Health Check Script (single endpoint)
Ideal for hands-on triage of a single problematic device.
# Tanium Patch Quick Health Check – Windows
$results = [ordered]@{}
# Service status
$svc = Get-Service -Name 'TaniumClient' -ErrorAction SilentlyContinue
$results["TaniumClientService"] = $svc.Status
# Patch tools folder exists?
$patchToolsPath = "C:\Program Files (x86)\Tanium\Tanium Client\Tools\Patch"
$results["PatchToolsExists"] = Test-Path $patchToolsPath
# Free disk space
$sysDrive = Get-PSDrive -Name C
$results["FreeSpaceGB"] = [math]::Round($sysDrive.Free/1GB,2)
# Network to Tanium Server
$taniumServer = "tanium.domain.com"
$results["CanPingServer"] = Test-Connection -ComputerName $taniumServer -Count 1 -Quiet
$results
2. Linux Remediation Scripts
2.1 Restart Tanium Client on Linux
Useful when:
-
Patch process not running
-
Coverage = Needs Attention
-
Scan Age too old
#!/bin/bash
echo "Restarting Tanium Client..."
sudo systemctl restart taniumclient.service
echo "Checking status..."
sudo systemctl status taniumclient.service2.2 Force Patch Tools Redeploy on Linux
Use when Linux endpoint is returning:
-
Tools Status =
[no results] -
Patch engine never starts
#!/bin/bash
TOOLS_DIR="/opt/Tanium/TaniumClient/Tools/Patch"
if [ -d "$TOOLS_DIR" ]; then
echo "Stopping Tanium Client..."
sudo systemctl stop taniumclient.service
echo "Removing Patch tools directory..."
sudo rm -rf "$TOOLS_DIR"
echo "Starting Tanium Client..."
sudo systemctl start taniumclient.service
echo "Patch tools removed. Tanium will redeploy automatically."
else
echo "Patch tools directory not found."
fi