---
title: "Windows Agent Updates & Versioning | v10.1 Onwards"
canonical: "https://docs.certero.com/space/CUP/118918337/Windows+Agent+Updates+%26+Versioning+%7C+v10.1+Onwards"
format: markdown
---
---

**Applies to:** CerteroX v10.1.54.41303 or later.

## Summary

From CerteroX v10.1.54.41303:

- **The auto-update setting is enforced.** With **Allow agents to auto-update** switched off, an agent on v10.1 or later keeps its client and modules whatever version its Endpoint Server is on. Before v10.1, an Endpoint Server upgrade could still reinstall the agent.
- **New Windows devices keep their installer's version.** A Windows device built from a v10.1 or later installer keeps the installer's agent service and core agent from its first start.
- **New option: Image-managed agents.** For non-persistent Windows VDI. See Global Settings below.

**The upgrade to v10.1 is a one-off exception.** When your Endpoint Servers are upgraded to v10.1.54.41303, expect every agent to move to the v10.1 agent, whatever its auto-update setting. The staged deployment method below works from the next CerteroX release.

---

## Auto-update Settings 

The **Allow agents to auto-update** setting can be configured in two places: Global Settings and Computer Systems Configurations.

### 1) Global Settings

**Main Menu > Global Settings > Other Options > Client Agent**:

![image-20261103-115424.png](media://31574a2f-051e-42b4-a4c4-2d198a61f0eb)

This global setting applies to agents that don't fall into the scope of any Computer Systems Configuration (explained next). Untick it if you don't want your agents to update themselves when CerteroX is upgraded, for example if agent upgrades must go through your internal change control.

**From v10.1**, an agent on v10.1 or later with this setting off keeps its client and modules whatever version its Endpoint Server is on. Before v10.1, an Endpoint Server upgrade could still reinstall the agent. Two exceptions remain:

- **Devices built from an installer earlier than v10.1** take the Endpoint Server's version when they first start, whatever this setting. Rebuild your images and deployment packages from a v10.1 or later installer.
- **Non-persistent VDI clones** from a golden image that isn't marked as image-managed continue to update as before. To hold their version, use image-managed agents.

**Image-managed agents (from v10.1)**

The Client Agent options also include **Image-managed agents**, which is off by default. It is needed for image-managed VDI, where clones started from a marked, non-persistent Windows golden image keep the image's agent and module versions through restarts, resets and Endpoint Server upgrades. Prepare the golden image and its Configurations before you switch it on: see <u>[Image-Managed VDI Agents | Managing the Golden Image](https://docs.certero.com/space/CUP/401145857/Image-Managed+VDI+Agents+%7C+Managing+the+Golden+Image)</u>. 

### 2) Computer Systems Configuration

![image-20261103-115826.png](media://bb3f4ba3-b308-49e7-b07a-8c459a5cb7fe)

As in the following example, an enabled Computer Systems Configuration (1) controls auto-update behaviour (2) for either Windows or Mac agents (3), and also switches module functionality such as Distribution and Patching on or off (4).

![image-20261103-115726.png](media://d661e585-a602-4290-9f9e-0466fe42d58b)

The scope of a Configuration, meaning which computers it applies to, is set with the Query Builder. Any computer that matches the criteria is subject to the Configuration. The criteria below target non-server operating systems, so the example above turns on agent auto-updates and AppsMonitor for desktops and laptops.

![image-20261103-115928.png](media://021e5503-14be-421b-b4b0-b4bd8705547a)

You can create more than one Configuration. A computer that falls into the scope of more than one adopts the settings of the Configuration with the highest priority (lowest number):

![Screenshot 2026-11-03 at 12.06.47-20261103-120652.png](media://2796075f-cd66-4440-b1a2-64a7186614ad)

Configurations are evaluated about every 10 minutes, so allow around 30 minutes for a change to reach an agent.

> ℹ️ **Configurations for image-managed VDI.** A Configuration that holds image-managed clones must use criteria that can be qualified (Computer Name, Computer Domain and operating system properties). It must also rank above any Configuration that uses Active Directory data, connector fields, user-defined fields or a limiting group. See Step 1 of <u>[Image-Managed VDI Agents | Managing the Golden Image](https://docs.certero.com/space/CUP/401145857/Image-Managed+VDI+Agents+%7C+Managing+the+Golden+Image)</u>.

---

### Staging Agent Updates under Change Control

A common use for more than one Configuration is to stage agent updates under your change control. Here's how it can work.

> ⚠️ **On upgrade to v10.1.54.41303** every agent moves to the v10.1 agent, regardless of its auto-update setting, so this method can't stage it. Use it from the next CerteroX release onwards.

1. In Global Settings, switch off **Allow agents to auto-update**, so auto-updating is controlled only by your Computer Systems Configurations.
2. Create a fleet-wide Configuration with criteria that include your whole agent estate.
3. Create a pilot Configuration with criteria that include only a pilot group of computers, for testing new agent versions before they reach the whole estate. **Rank it above the fleet-wide Configuration**, so pilot computers take its settings.
4. When a new CerteroX release is available, begin your change control.
5. Switch off auto-update in the fleet-wide Configuration.
6. Make sure auto-update is on in the pilot Configuration.
7. Upgrade CerteroX.
8. Watch the pilot agents update. This assumes the release includes agent changes: compare the Client Agent Installer version in the release notes' Component Versions table with your current version.
9. When you're satisfied the pilot group isn't adversely affected, switch auto-update back on in the fleet-wide Configuration so the rest of your agents update.
10. Rebuild your images and deployment packages from the new release's installer, so new devices are built on the version you have approved.

Auto-update in the fleet-wide Configuration stays on until the next CerteroX release. Auto-update in the pilot Configuration can stay on at all times.

For non-persistent VDI, pilot a new agent version by deploying a new golden image to a pilot pool instead. See *Moving to a new agent version* in <u>[Image-Managed VDI Agents | Managing the Golden Image](https://docs.certero.com/space/CUP/401145857/Image-Managed+VDI+Agents+%7C+Managing+the+Golden+Image)</u>.

---

## Windows Agent Versions & Reporting

The current Windows agent version for your solution is the version of the agent installer your Endpoint Server hosts. Go to **Main Menu > User > Downloads**:

![image-20261103-124057.png](media://e0abf3cb-948e-42f9-b69a-49d5a2a07569)

Download the **Client Agent Setup for Windows** executable:

![image-20261103-124436.png](media://d12162d1-a2b6-4dcf-92c5-39cd8de567ee)

Right-click the downloaded file, choose **Properties**, select the **Details** tab and check the **File version**.

The last section of the version string is the **revision number**, which identifies the agent version. For CerteroX v10.1.54.41303, the Windows agent installer is v10.1.12.41293, so the revision number is **41293**. The Component Versions table in each release's notes gives the agent installer version.

Agents installed on new computers joining the network show the full version string. Existing agents that have auto-updated show a matching revision number only.

> ℹ️ **From v10.1, "current" means the version you have approved.** If you hold agents back with auto-update off, or run image-managed VDI clones, agents on an older revision are expected and are not out of date. Compare your estate with your approved version, not only with the latest release.

To report on this, go to **Computer Systems > Windows Systems**. On the **Summary** tab, filter on **Last Update** greater than **-30d**, and on the **Client** tab filter on **Type = Agent**. Then group by agent version by dragging the **Version** column header next to the active/archive drop-down list:

![image-20261103-125940.png](media://f4cca7f5-d8db-42c7-9c06-4ef86e626d45)

The grouped view shows how current your agent versions are. 

You can also create a Dashboard chart to track this. Click a bar on the chart to drill into the computers with a specific agent version:

![image-20261103-130630.png](media://035ec7dc-f2ad-442f-beb7-60f6a98d2d7d)

---

## Related

- <u>[When Will a Certero Agent Self-Update?](https://docs.certero.com/space/CUP/335937537/When+Will+a+Certero+Agent+Self-Update%3F)</u> – when an update actually happens, and common scenarios.
- <u>[Image-Managed VDI Agents | Managing the Golden Image](https://docs.certero.com/space/CUP/401145857/Image-Managed+VDI+Agents+%7C+Managing+the+Golden+Image)</u> – how to build, mark and seal a golden image so VDI clones keep their versions.
- <u>[CerteroX | Release Notes | v10.1.54.41303](https://helpdesk.certero.com/space/RN/400195587/CerteroX+%7C+Release+Notes+%7C+v10.1.54.41303+%7C+Latest)</u> – the release that introduced auto-update enforcement and image-managed agents.

---

# Support

For help with agent updates, please review the related support articles and then raise a support request through the <u>**[Certero Help Desk](https://helpdesk.certero.com/)**</u>.

---

© 2026 Certero Company Confidential. All rights reserved.