# Upgrade Manager

The upgrade process for OpManager - installed servers across your network is simplified using the Upgrade Manager. It offers a centralised platform to manage and perform upgrades for **OpManager Standalone servers, Central, Probes, their Failover servers.** The enhanced smart upgrade feature helps to overcome the bottlenecks faced during the upgrade process.

**Note:**

- In the **Enterprise Edition**, all Probe services must be up and actively communicating with the Central server. For Failover setups, both the primary and secondary services should be up and running.
- For service pack versions **12.8.344 and above**, manual backup prerequisites are optional as the Upgrade Manager takes the backup automatically.
- The **QPM**, designed to deliver targeted patches can be seamlessly applied across services using **Upgrade Manager**, following the same steps as a service pack.
- If you are encountering issues caused by AV/EDR interactions during the upgrade process, please follow this [exclusion guide](https://www.manageengine.com/network-configuration-manager/pgsql-av-edr-exclusion.html?upgrade-manager).

![Upgrade Manager](https://www.manageengine.com/network-configuration-manager/help/images/upgrade-ncm-1.png)

![Select service pack](https://www.manageengine.com/network-configuration-manager/help/images/upgrade-ncm-2.png)

![Upgrade details](https://www.manageengine.com/network-configuration-manager/help/images/upgrade-ncm-3.png)

- The service pack's download progress status for individual Probes will be displayed under the **Current Status** column.

While downloading the service pack, if slowness or network issues is encountered, you can manually stop the download using the **Stop** button in the Actions column. In that case, manually copy the service pack to the `<OpManagerProbe>\UpgradeManager` directory for OpManager service packs. Use the **Refresh** button to fetch the latest status of the respective probe service.

- If a Probe goes offline or loses connection with Central during the service pack download, then the download will automatically resume once communication is restored.

![Health status](https://www.manageengine.com/network-configuration-manager/help/images/upgrade-ncm-4.png)

- With a successful health check for both the Central and all Probes, the product is now ready for the upgrade.

![Start Upgrade](https://www.manageengine.com/network-configuration-manager/help/images/upgrade-ncm-5.png)

- For **Failover servers,** the upgrade will start automatically for both the active and the standby server.
- All Probes will automatically begin upgrading simultaneously once the Central upgrade is successfully completed.
- Upgrade details for individual servers will be automatically updated under the **Current Status** column in Central.

![Upgrading status](https://www.manageengine.com/network-configuration-manager/help/images/upgrade-ncm-6.png)

- [Upgrade Backup Pre-requisites](#backup)
- [Upgrade Pre-requisites](#pre)
- [Edition-specific Upgrade](#edition)
- [Upgrade OpManager using UpdateManager.bat and .sh file](#bat)

- If you are encountering issues caused by AV/EDR interactions during the upgrade process, please follow this [exclusion guide](https://www.manageengine.com/network-configuration-manager/pgsql-av-edr-exclusion.html?upgrade-manager).
- Ensure that the user performing the upgrade has the required permissions for the OpManager folder.

## Edition-specific Upgrade

| Edition | Without Failover | New Failover |
|---|---|---|
| **Standard / Professional** | Upgrade the service using the [UpdateManager.bat /.sh file](#bat) | - Stop both primary and secondary Failover service.<br>- Follow the steps provided under [UpdateManager.bat /.sh file](#bat) to upgrade the service.<br>- Then, start the secondary service once as master and stop the service.<br>- Now start the primary service followed by secondary service. |
| **Enterprise Edition** | - Stop the Network Configuration Manager Central and all the Probe services.<br>- Upgrade using [UpdateManager.bat /.sh file](#bat).<br>- Once the upgrade is completed, restart the Central service.<br>- Then, the Probes will detect the upgrade, perform it in all the Probes and start the services on its own. | - Stop both primary and secondary service in Network Configuration Manager Central.<br>- Stop the secondary service and ensure only the primary service in running in all Probes.<br>- Follow the steps provides under [UpdateManager.bat /.sh file](#bat) to perform upgrade in Central.<br>- Once upgrade is completed start the Network Configuration Manager Central service.<br>- Then, the Probes will detect the upgrade, perform automatically in all the Probe services.<br>- Start and stop the Standby service once as master across Central and Probe, then start the primary followed by the Standby service. |