Update the ePO Policy with CSR
This topic explains how to update the ePolicy Orchestrator (ePO) policy for Content Security Reporter (CSR). To support the latest ePO update, ensure that CSR runs version 2.9.1 or later. If the current version is lower, upgrade it to version 2.9.3 or higher to ensure compatibility.
Prerequisites
- Create a backup of the existing CSR configuration.
- Ensure the necessary installation files for CSR 2.9.3 are available.
- Ensure access to ePO with the necessary administrative privileges.
- Check your database to see if it is external or internal. (MariaDB).
NOTE: To maintain encryption compatibility when upgrading CSR from 2.8.0 to 2.9.3, use the old csr.keystore
file.
Steps to Upgrade CSR Using an External Database
To upgrade CSR using an external database, follow these steps:
- Go to
..\reporter\conf\backupauto\
, copy thebackup.xml
file from CSR 2.8.0, and obtain thebackup.xml
file for CSR 2.9.3.
Back up the current configuration
- Go to
- Remove the existing CSR configuration
- Go to ePO > Registered Server Settings and delete the report server.
- Go to ePO > Extensions and remove McAfee Content Security Reporter.
- Go to Extensions > Shared Components, remove Common Catalog Plugin and Analytics in order.
- Uninstall the CSR server from the system.
- Install CSR 2.9.3
- Start the installation of CSR 2.9.3. After the prompt, enter the passkey as the password.
- Reconfigure CSR in ePO
- Install the CSR 2.9.3 extension in ePO.
- Go to ePO > Registered Server Settings > Add New Server. Provide the CSR server IP address and enter the passkey (password).
- Click Test Settings to verify the connection.
- Click Save to save the configuration.
- Restore configuration from backup
- Create a folder named backup inside
..\Content Security Reporter\reporter\conf\
. Copy the previously savedbackup.xml
file into..\Content Security Reporter\reporter\conf\backup\
. - Restart the CSR service to restore the configuration.
- Create a folder named backup inside
- Post-upgrade considerations
- CSR 2.9.3 supports ePO CU13. If you upgrade ePO to a newer version, CSR may show as unsupported. To resolve this, remove the CSR extension, upgrade ePO, and reinstall the CSR extension.
Steps to Upgrade CSR Using an Internal Database - MariaDB
To upgrade CSR using an internal database - MariaDB, follow these steps:
- Use MariaDB SQL dump of the existing database. Save the backup in a secure location for restoration later.
Backup the current database
- Install CSR 2.9.3
- Start the installation of the latest CSR version/CSR 2.9.3.
- Modify database settings
- Go to ePO > Report Server Settings > Database.
- Click Edit and set the database offline.
- Click Save.
- Restore the database in MariaDB
- Open Command Prompt and go to
..\reporter\mariadb\bin
. Log in to MariaDB. Drop the existing reporting database. - Create a new reporting database. Restore the previous database backup into the newly created reporting database.
- Open Command Prompt and go to
- Bring the database back online
- Once the restoration is complete, go to ePO > Report Server Settings > Database. Click Edit and set the database online. click Save.
NOTE: After the upgrade, perform testing and validation by verifying the CSR configuration, ensuring reports are generated correctly, and running test reports to confirm proper functionality.