---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Supported platforms for auto-upgrade

# Supported platforms for Agent Client Collector auto-upgrade {#ariaid-title1}

* Release version: Yokohama
* 
* Updated May 28, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Operating systems and package types supported for Agent Client Collector auto-upgrade, and the minimum agent version required.
The minimum agent version for upgrade eligibility is 2.7.0 on all platforms. Agents on unsupported platforms are skipped with error code ACC-5005.{#acc-agent-upgrade-platforms__acc-agent-upgrade-platforms-para-1}
{#acc-agent-upgrade-platforms__table_upgrade_platforms__entry__3}

| Operating system | Package type | Requirements |
|-|-|-|
| Windows | MSI | Agent must run as the SYSTEM account. |
| Linux --- Red Hat, CentOS, Oracle, Rocky, Alma, CentOS Stream | RPM | Agent must run as root or have full sudo access. For information on configuring sudo access, see [Install Agent Client Collector on a Linux system](https://servicenow-prod.fluidtopics.net/gnStIIij9QHlEGg9eHnQWA "Install Agent Client Collector using a package distribution tool. Before that, you can manually install the Agent Client Collector on a few machines to verify that your agents contain the correct policies and checks."). |
| Linux --- Ubuntu, Debian, GNU/Linux | DEB | Agent must run as root or have full sudo access. For information on configuring sudo access, see [Install Agent Client Collector on a Linux system](https://servicenow-prod.fluidtopics.net/gnStIIij9QHlEGg9eHnQWA "Install Agent Client Collector using a package distribution tool. Before that, you can manually install the Agent Client Collector on a few machines to verify that your agents contain the correct policies and checks."). |
| macOS --- Intel (x64) | PKG | Agent must run as root or have full sudo access. For information on configuring sudo access, see [Manually install Agent Client Collector on macOS](https://servicenow-prod.fluidtopics.net/BFALtWFfFIjoOvFPQci8dA "Install Agent Client Collector manually on a machine that uses macOS when the agent is not connected to the instance or you want enhanced customization options."). |
| macOS --- Apple Silicon (ARM64) | PKG | Architecture is detected automatically. Agent must run as root or have full sudo access. For information on configuring sudo access, see [Manually install Agent Client Collector on macOS](https://servicenow-prod.fluidtopics.net/BFALtWFfFIjoOvFPQci8dA "Install Agent Client Collector manually on a machine that uses macOS when the agent is not connected to the instance or you want enhanced customization options."). |
[Table 1. Supported platforms for auto-upgrade]

{#acc-agent-upgrade-platforms__table_upgrade_platforms}

## Non-supported platforms {#acc-agent-upgrade-platforms__acc-agent-upgrade-platforms-unsupported}

Auto-upgrade is not supported on Linux SuSE, Solaris, or AIX. Agents on these platforms are skipped during upgrade runs and generate error code ACC-5005. To upgrade agents on
unsupported platforms, manually install the new version on the agent host.{#acc-agent-upgrade-platforms__acc-agent-upgrade-platforms-para-2}

## Required agent permissions {#acc-agent-upgrade-platforms__acc-agent-upgrade-platforms-permissions}

Agents must run with elevated privileges on the host to perform a self-upgrade:{#acc-agent-upgrade-platforms__acc-agent-upgrade-platforms-para-3}

* Windows: SYSTEM account
* Linux: root user or sudoers file configuration with full sudo access
* macOS: root user or sudoers file configuration with full sudo access
{#acc-agent-upgrade-platforms__ul_upgrade_permissions}