Replace rolling upgrades

The replace rolling upgrades model involves deploying new Windows servers that you are installing 25.3 on, and joining them to your existing Trust Protection Foundation database for the cluster, then replacing the existing servers with the new servers. It requires you deploy one new server for each existing server. For example, if you have six Trust Protection Foundation servers on your origin version (that you are upgrading from), you would need to deploy six new Windows servers, each one matching exactly the configuration of the server it will replace (including CyberArk components, processing engine assignments, and network discovery zones).

This model can often result in a cleaner upgrade process, and allows you to upgrade your Windows operating system at the same time you are upgrading your CyberArk version, but results in extra manual configuration or steps that need to be scripted.

When performing this upgrade, follow all the steps in each of the following sections.

Getting Started

1. Create new Windows servers that match 1:1 the roles of the servers in your current CyberArk deployment cluster.
2. Download, distribute, and unzip installation files for the 25.3.x upgrade.

3. [Optional] Export your software encryption key (if used).

   For more information, see Backing up the software encryption key.

Database configuration

1. Back up your database.

   For instructions on how to perform the database backup, visit Microsoft's SQL documentation: Create a Full Database Backup.

2. [Conditional] If using answer file(s): Update the answer file so the DBO credentials are included, and new components (if desired) are added to the appropriate servers.

   For detailed information about the schema and settings of the answer file, see Creating and using answer files.

Run the installation MSI

1. Verify that the extracted CyberArk Trust Protection Foundation 25.3.x.zip is available on the server.

2. From an elevated command prompt, change your directory to the extracted zip folder and enter the following command:

   CyberArkTrustProtectionFoundationInstall-25.3.x.msi

   How to open an elevated command prompt

   1. From the Start menu, search for CMD.
   2. In the search results, right-click on Command Prompt, and choose Run as administrator.
   Why do I need an elevated command prompt?

   Running CyberArkTrustProtectionFoundationInstall-25.3.x.msi from an elevated command prompt ensures that:

   • The CyberArk Configuration Console launches properly after the installation is complete.
   • You can uninstall Trust Protection Foundation from Windows' Programs and Features tool without needing to run a special command in an elevated command prompt.

3. When the Welcome window appears, click Next.

4. Read the terms stated in the License Agreement window. If you agree, select I accept the terms in the license agreement, and then click Next.

5. Run the previous steps on all the new Windows Trust Protection Foundation server. Do not modify your existing (production) servers.

Configure the server

1. Either use the configuration wizard GUI to complete the configuration steps for the upgrade, or use the TPPConfiguration.exe CLI to do a silent upgrade using the appropriate updated answer file.

   If you have questions about the command line interface, see Upgrade using the command line.

   For information about the TPPConfiguration utility, see Using the TppConfiguration command line tool.

   To configure CyberArk Trust Protection Foundation using the CyberArk Configuration Console

   1. On the Welcome screen, review the information, and then click Next.

      If you have any questions about fields in this wizard, refer to the field-specific information in Configure CyberArk Trust Protection Foundation - Self-Hosted from the CyberArk Configuration Console.

   2. On the Administrative Account screen, enter the local master admin credentials for Trust Protection Foundation, and then click Next.

   3. On the Database Settings screen, enter the information for the database owner account: type, login, and password.

      For information about the Settings tab, see Field descriptions - Settings tab.

      For information about the Expert tab, see Field descriptions - Expert tab.

   4. On the Customer Experience screen, review the information on how data is collected.

      NOTE  Participation in the Customer Experience Improvement Project is required for all customers, enabling CyberArk to gather license utilization and product usage telemetry. This does not include any personally-identifiable data. Read more about our data collection policy in the CyberArk Data Privacy Policy for Trust Protection Foundation.

   5. On the Upgrade Server screen, review the information, and then click Finish.

   6. When the configuration is complete, click Close.

   Once you have completed the configuration wizard, the CyberArk Configuration Console window automatically opens. For more information about how to use the CyberArk Configuration Console, see CyberArk Configuration Console.

2. [Conditional] If you used the upgrade wizard GUI in step 1: In the CyberArk Configuration Console, enable any new components that you want for each server.
3. In the CyberArk Configuration Console, click the Product node.
4. Start all Trust Protection Foundation Windows services.
5. If this server has the WebConsole component installed, open the console (without the application delivery controller; for example, use https://localhost/Aperture)
6. Repeat on all Trust Protection Foundation servers.

Validate the installation

• Validate that each server in the cluster is performing its assigned role.

  For example, on a server that has the Web Console, try renewing a certificate or rotating an SSH key. On a code signing server, try signing code. For a server, validate that connections are happening as expected.