Platform / Tz0 Deploy

Module · distribution

Tz0 Deploy

Large-scale software distribution

A critical patch was released today. How long until it reaches your twelve thousand workstations — and how many people have to stop working for that to happen?

Request a technical evaluation

See how it works

Silent installation · scheduled window · bandwidth control

A central server cabled to three workstations

Distribution

The package leaves from one place only.

You approve once, on the server, and each workstation’s agent pulls it down when its turn comes. No shared folder, no technician with a USB stick, and no network bandwidth disappearing all in the same minute.

tz0.suaempresa.local/deploy/atualizacoes

Tz0 Deploy · web console

Console capture from an estate in production. Machine and person identification replaced; figures untouched.

What the module does

Installing on twelve thousand machines without bringing the network down.

The problem with distribution at scale is never the installer. It is the bandwidth, the window and the machine that happened to be switched off.

Silent installation

Installs, updates and uninstalls with no user interaction and no technician at the machine.

Scheduled window

Overnight for head office, weekends for the branches, immediate for anything critical.

Bandwidth control

Caps what the rollout consumes so it does not compete with the system that keeps the business running.

Automatic resume

Link dropped mid-transfer? Resume picks up where it stopped.

Security fixes

Critical patches distributed transparently, keeping the workstation protected without interrupting the day.

Package catalogue

What the company approved sits ready to install; what is not in the catalogue can be removed in bulk.

Servers too

Desktop, laptop and server in the same process, each with its own window and criteria.

Windows, Linux and Android

One pipeline serves all three, with no separate tool per platform.

How it works

From the approved package to the updated workstation.

The whole pipeline runs on your network: the package passes through no cloud before it reaches the machine.

Console

From scheduling to follow-up, in the browser.

Tz0 console screenshot: A failure is a failure, noise is noise — **A failure is a failure, noise is noise.** 10 resumed interruptions and 25 deployments that did not apply are left out of the count, and every machine that was off received the package later.

Tz0 console screenshot: Only 7 of 35 machines have this month's cumulative update — **Only 7 of 35 machines have this month’s cumulative update.** One security fix has been pending for 2 years, and 21 machines run a Windows that no longer receives fixes.

Tz0 console screenshot: Updated is not the same as protected — **Updated is not the same as protected.** 27 machines run Windows that is out of support or on ESU only, and 18 haven’t installed anything in more than 30 days.

Tz0 console screenshot: 15 machines still run Windows 10 22H2, which no longer receives fixes, and 19 have a latest cumulative update more than 3 months old — **15 machines still run Windows 10 22H2, which no longer receives fixes, and 19 have a latest cumulative update more than 3 months old.** The conclusion already points the way: update the system.

Profiles screen in Tz0 Deploy, showing the Development group policy: rules, software distribution, Windows Update, access blocking and firewall — **Policy by group, not machine by machine.** The Development group with everything that applies to it — rules, apps to push (here, updating Git), Windows Update, access blocking, firewall. Beside it, the other groups: BitLocker with TPM on and off, Servers, Support, Macs. You define it once and it holds for everyone who joins.

Tz0 console screenshot: Only 22 of 55 machines are ready to receive packages — **Only 22 of 55 machines are ready to receive packages.** 14 are missing the installation component, and each reason comes with the way to fix it.

Tz0 console screenshot: 11,877 packages ready to distribute, and the screen already shows what exists in the company: 219 programs across 721 installations, 135 of them with an update available — **11,877 packages ready to distribute, and the screen already shows what exists in the company: 219 programs across 721 installations, 135 of them with an update available.**

Tz0 console screenshot: Software nobody installed through the catalog: 95 programs came from the Store or from outside, and Notepad++ runs in 7 different versions, a natural candidate for standardization — **Software nobody installed through the catalog: 95 programs came from the Store or from outside, and Notepad++ runs in 7 different versions, a natural candidate for standardization.**

Screens from a real estate in production, not a demo environment. Anything identifying a person was replaced with generic equivalents before publishing; machine names, KB numbers, versions, percentages and the interface itself are untouched.

Exposure

The cost of each day with a known flaw.

Machine-days exposed to CVEs, the highest-risk package and how much of the window closes today with what is already in the repository.

Tz0 console screenshot: Each day with a known flaw is a day with the door open — **Each day with a known flaw is a day with the door open.** That is 1,862 machine-days exposed to CVEs on 28 of 41 machines, all of them critical, exploited or ransomware flaws, and 16% closes now with what is already in the repository.

Tz0 console screenshot: The product says what got stuck and how to unstick it — **The product says what got stuck and how to unstick it.** winrar is the highest-risk package, with a ransomware CVE on 9 machines, and the open window adds up to 1,862 machine-days, 16% of it closable today.

Priority

What to update first.

Security fixes go now; new major versions are tested first. Unsupported Windows and updates that fail in a loop show up on their own.

Tz0 console screenshot: Update in the right order — **Update in the right order.** 20 of 35 machines with pending updates: security fixes go now; the 18 new major versions are tested first.

Tz0 console screenshot: An update that fails 125 times does not go unnoticed — **An update that fails 125 times does not go unnoticed.** 7 machines with no support at all, 20 on ESU only and one that hasn’t installed an update in 2,529 days.

What changes in practice

Eight things that stop requiring a trip.

The critical patch reaches the whole estate the same night.

Nobody stops working to receive an installation.

The rollout does not compete with production systems for bandwidth.

A dropped link does not force the transfer to start over.

A machine that was off during the window joins the next one on its own.

Software outside the catalogue is removed in bulk, not desk by desk.

The distant branch is served just like head office.

Windows, Linux and Android in one pipeline.

Included with the module

Three tools in the same package.

A new report does not become a project. We do not build bespoke work for a single customer, but we look at every request: when the need serves everyone, the report goes into the product and reaches all customers in the next update.

Tz0 EIS