# Upgrade on traditional platforms Upgrade on traditional platforms ================================ This section describes the various upgrade methods and options for specific platform configurations. For a list of supported platforms, refer to [Supported platforms for CloudBees CD/RO on traditional platforms](/docs/cloudbees-common/latest/supported-platforms/cloudbees-cd-traditional). When upgrading a traditional platform, the steps you must vary depending on whether your environment is clustered or non-clustered: * [Upgrade a clustered environment](/docs/cloudbees-cd/latest/upgrade-traditional/clustered-environment) * [Upgrade a non-clustered environment](/docs/cloudbees-cd/latest/upgrade-traditional/non-clustered-environment) When upgrading CloudBees CD/RO to version 10.2 or higher you must first delete all legacy services and containers. Failure to do so can result in upgrade failure or broken database consistency that prevents running the `validateDatabase` API. Refer to [Model dynamic environments](/docs/cloudbees-cd/latest/applications-environments/model-dynamic-environments) and [Model and deploy microservice applications](/docs/cloudbees-cd/latest/applications-microservice/) [](#_user_interface_upgrade)User interface upgrade -------------------------------------------------- This [method](/docs/cloudbees-cd/latest/upgrade-traditional/user-interface) provides a wizard for upgrading CloudBees CD/RO on a supported server platform. This upgrade method is generally preferred by Windows users, but is supported on Linux platforms with the X Window System installed. See [User Interface Upgrade Method](/docs/cloudbees-cd/latest/upgrade-traditional/user-interface) for more details. Upgrade options: * **Upgrade Existing Installation** This option uninstalls the current release, installs the latest CloudBees CD/RO release, collects the CloudBees CD/RO service account credentials, configures the system with all property values, and restores custom files and data. * **Clean Install** This option allows you to specify a different installation directory for the new version. The files from your previous CloudBees CD/RO version will not be removed or modified and will remain in their original directories. On Linux, when CloudBees CD/RO is already installed, and you want to use the clean install upgrade method, you must do an advanced installation. On Windows, a clean installation replaces the registry entries of the current installation. On Linux, a clean installation replaces the CloudBees CD/RO files in the `/etc/init.d` or, if using systemd, the `/etc/systemd/system` directory. The result is that only one instance of CloudBees CD/RO (the new version) is running. [](#_interactive_command_line_upgrade)Interactive command-line upgrade ---------------------------------------------------------------------- This [method](/docs/cloudbees-cd/latest/upgrade-traditional/interactive-cli) provides an interactive command-line for upgrading CloudBees CD/RO on a supported server platform. This upgrade method is only available for Linux platforms. See [Interactive Command-Line Upgrade Method](/docs/cloudbees-cd/latest/upgrade-traditional/interactive-cli) for more details. Upgrade options: * **Upgrade Existing Installation** This option uninstalls the current release, installs the latest CloudBees CD/RO release, collects the CloudBees CD/RO service account credentials, configures the system with all property values, and restores custom files and data. * **Clean Install** This option allows you to specify a different installation directory for the new version. The files from your previous CloudBees CD/RO version will not be removed or modified and will remain in their original directories. On Linux, when CloudBees CD/RO is already installed, and you want to use the clean install upgrade method, you must do an advanced installation. On Windows, a clean installation replaces the registry entries of the current installation. On Linux, a clean installation replaces the CloudBees CD/RO files in the `/etc/init.d` or, if using systemd, the `/etc/systemd/system` directory. The result is that only one instance of CloudBees CD/RO (the new version) is running. [](#_silent_unattended_upgrade)Silent unattended upgrade -------------------------------------------------------- This [method](/docs/cloudbees-cd/latest/upgrade-traditional/silent-unattended) provides a non-interactive command-line upgrade for supported server platforms. You may find this installation method preferable for upgrading multiple remote agents and servers. See [Silent (Unattended) Upgrade Method](/docs/cloudbees-cd/latest/upgrade-traditional/silent-unattended) for more details. Upgrade options: * **Upgrade Existing Installation** This option uninstalls the current release, installs the latest CloudBees CD/RO release, collects the CloudBees CD/RO service account credentials, configures the system with all property values, and restores custom files and data. You cannot add a new repository server with this upgrade method. [](#_repository_server_with_a_cloudbees_cdro_upgrade)Repository server with a CloudBees CD/RO upgrade ----------------------------------------------------------------------------------------------------- The only way to install a repository server on the same machine as other services is to uninstall and reinstall CloudBees CD/RO. You can install the repository server on a different machine to avoid uninstalling and reinstalling CloudBees CD/RO. [](#_non_server_platform_agent_upgrade)Non-server platform agent upgrade ------------------------------------------------------------------------ _You cannot directly upgrade a non-server platform agent_ (that is, an agent on a machine that is not a supported CloudBees CD/RO server platform). You must uninstall and then reinstall these machines using the CloudBees CD/RO installer. For more information, see [Uninstalling CloudBees CD/RO](/docs/cloudbees-cd/latest/install-trad/uninstall) and [Non-Server Platform Agent Installation Method](/docs/cloudbees-cd/latest/install-trad/non-server-agent-install) . [](#_stand_alone_repository_server_or_web_server_upgrade)Stand-alone repository server or web server upgrade ------------------------------------------------------------------------------------------------------------ _You cannot directly upgrade a standalone repository server or standalone web server._ You must uninstall and then reinstall these servers using the CloudBees CD/RO installer. The uninstall and reinstall process is required to install an agent on the server machine. An agent is required on the machine with the standalone repository server or web server. For more information, see [Uninstalling CloudBees CD/RO](/docs/cloudbees-cd/latest/install-trad/uninstall) , [Installing CloudBees CD/RO](/docs/cloudbees-cd/latest/install-trad/) , and [Copying Repository Contents](/docs/cloudbees-cd/latest/upgrade-traditional/duplicate-repository) .