---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Upgrade an agent in an instance

# Upgrade an agent in an instance {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

Perform selective self-upgrade instead of bulk upgrade for enhanced efficiency when working with agents that are difficult to access, such as agents deployed in the cloud. You can perform selective upgrade on up to 20 agents
at a time.

## Vorbereitungen

Hinweis:  
Selective upgrade is available for the agents version 2.7.0 and above.

Supported Operating Systems: Windows and Linux.

Ensure that data files are up to date by restarting the MID Server and collecting host data. For details on collecting host data, see [Run host data collection on demand](https://servicenow-prod.fluidtopics.net/ewhlvgxP53w8Qn1kene5Eg "You can perform host data collection on demand, if you need to perform data collection before the job is scheduled to run.").  
Hinweis:  
When working in a Linux environment, ensure that you have sudo permissions and that the following configurations are set:{#upgrade-agent-from-instance__id_gcj_ftm_cyb__entry__4}

| OS | OS version | Commands | Agent version |
|-|-|-|-|
| CentOS,Red Hat | 7, 8 | * `/usr/bin/systemctl start acc` * `/usr/bin/systemctl stop acc` * `<systemctl location> daemon-reload` (default location is `/usr/bin`) * `/usr/bin/rpm -Uv <cache dir location>/upgrade/agent-client-collector-upgrade.rpm` {#upgrade-agent-from-instance__ul_tyf_4vm_jyb} Default cache directory location: `/var/cache/servicenow/agent-client-collector` * `unzip -o`: Unzips the signature file to validate the installation. * `openssl dgst -sha256 -verify`: Verifies use of a signature from a servicenow installation file. {#upgrade-agent-from-instance__ul_acz_1wm_jyb} | 2.7 |
| Debian, Ubuntu |   | * `/usr/bin/systemctl start acc` * `/usr/bin/systemctl stop acc` * `<systemctl location> daemon-reload` (default location is `/usr/bin`) * `/usr/bin/dpkg --install --refuse-downgrade --skip-same-version <cache dir location>/upgrade/agent-client-collector-upgrade.deb` {#upgrade-agent-from-instance__ul_gjn_lxm_jyb} Default cache directory location: `/var/cache/servicenow/agent-client-collector` * `unzip -o: Unzips the signature file to validate the installation` * `gpg -import && gpg --verify: Verifies use of a signature from a servicenow installation file.` {#upgrade-agent-from-instance__ul_ppj_5tx_k2c} | 2.7 |
[Tabelle : 1. Linux Operating Systems]

{#upgrade-agent-from-instance__id_gcj_ftm_cyb}  
When connecting via a MID Server, ACC installs need to access one of the following URLs:

* https://\<MID-WEBSERVER-URI:PORT\>/static/acc_installers/agent-client-collector
* https://install.service-now.com/
{#upgrade-agent-from-instance__ul_d54_p5p_chc}  
When upgrading MID-less agents, upgrade is performed at the URL set in the agent-upgrade-url-path property of the acc.yml file. If no URL is set at this property, upgrade is performed by downloading the installer script from the following Content Delivery Network (CDN) URL: https://cdn-install.sncapps.service-now.com/glide/distribution/builds/package  
Hinweis:  
When using a CDN, send your download request through a proxy server, for added security. For details, see [Configure proxies when performing MID-less upgrade using a Content Delivery Network (CDN)](https://servicenow-prod.fluidtopics.net/20bKOl~53WgWPT_iZkZ9lQ "Create proxies for added security when upgrading MID-less agents via a Content Delivery Network (CDN). You add proxy servers to the sn_agent_proxy table on the ServiceNow instance.").  
Select the version to which you want to upgrade your agent.

1. Navigate to AllSystem PropertiesAll Properties.
2. Select New.
3. Assign the following values:
   * Name = sn_agent.agent_upgrade_version
   * Type = string
   * Value = The version number to be upgraded to, in the format \<major_version.minor_version.patch_version\>. For example: 4.3.2
   {#upgrade-agent-from-instance__ul_slp_wwp_chc}
4. Select Submit.

{#upgrade-agent-from-instance__ol_oyg_qvp_chc}If you do not select a version, the agent automatically upgrades to the current Agent Client Collector Framework scoped app version.

Role required:

* Windows: Local SYSTEM account (Agent Client Collector service running as Local System)
* Linux: sudo rpm/dpkg
* macOS: sudo pkg
{#upgrade-agent-from-instance__ul_owx_1ll_cyb}

## Warum und wann dieser Vorgang ausgeführt wird

Agent Client Collector supports selective self-upgrade in the following operating systems:

* Windows: Due to Windows UAC restrictions, the agent must run as a local SYSTEM account to perform the upgrade via msiexec.
* Linux: RPM and DEB
{#upgrade-agent-from-instance__ul_yd4_dmb_bvb}

## Prozedur

1. Navigate to AllAgent Client CollectorAgents.
2. Select the agent that you want to upgrade.
3. In the Related Links section, select Upgrade agent.
4. In the confirmation dialog box, select Upgrade.  
   The Agent Upgrade Histories page appears, where you can monitor the upgrade progress in the State column, which displays either Success or Failed.
5. View the log for the agent upgrade in the Message column.  
   For a failed upgrade on a Linux machine, navigate to the \<cache directory location\>/upgrade/agent-client-collector-upgrade.rpm file and ensure that the configurations are set for the relevant OS, according to the Linux Operating Systems table, above.  
   For a failed upgrade on a Windows machine, check the relevant log file, located at \<user folder\>\\AppData\\Local\\Temp\\ACC_Logs:
   * ACC logs: ACC_Upgrade.log
   * MSI logs: MSI_ACC_Upgrade.log
   {#upgrade-agent-from-instance__ul_vrp_pdk_3yb}