-
Title
Upgrade and Patching requirements for Safeguard for Privilege Passwords and Safeguard for Privilege Sessions -
Description
What are the required steps to upgrade or patch to the latest version of Safeguard for Privileged Sessions or Safeguard for Privileged Passwords? -
Resolution
RESOLUTION:
NOTE: This article describes upgrade paths related to versions. For specfic details regarding cluster and stand alone upgrades please see the appropriate guides.
Safeguard for Privileged Sessions Guide
Safeguard for Privileged Passwords Guide
Before you can patch to the latest version of a major release you first must upgrade to the initial major version.
EXAMPLE: Safeguard for Privileged Sessions
If you want to upgrade to 6.6 and are running something earlier than 6.0 you first must upgrade to 6.0.
First upgrade to the latest release of the previous version, either LTS or feature release. So in this example, the latest 5.x version available.
Then you can patch to 6.0.
Please see the Admin Guide for more details.
EXAMPLE: Safeguard for Privileged Passwords
The same requirements exist for Privileged Passwords as well. However the version previous to 6.0 was 2.11.2 as opposed to 5.
More information is available here.
NOTE: On both products, if you upgrade to a feature release you cannot upgrade to a non-Feature Release until the next LTS major release version is available.
Long Term Support (LTS) and Feature Releases
Releases use the following version designations:
- Long Term Support (LTS) Releases: The first digit identifies the release and the second is a zero (for example, 6.0 LTS).
- Maintenance LTS Releases: A third digit is added followed by LTS (for example, 6.0.1 LTS).
- Feature Releases: The Feature Releases are two digits (for example, 6.6).
Customers choose between two lanes for receiving releases: Long Term Support (LTS) Release or Feature Release. See the following table for details.
Long Term Support (LTS) Release Feature Release Release Frequency Frequency: Typically, every 2 years
Scope: Includes new features, resolved issues and security updates
Versioning: The first digit identifies the LTS and the second digit is a 0 (for example, 6.0 LTS, 7.0 LTS, and so on).
Frequency: Typically, every 3 months
Scope: Includes the latest features, resolved issues, and other updates, such as security patches for the OS
Versioning: The first digit identifies the LTS and the second digit is a number identifying the Feature Release (for example, 6.6, 6.7, and so on).
Maintenance Release Frequency: Typically, every 3 months during full support
Scope: Includes critical resolved issues
Versioning: A third digit designates the maintenance LTS Release (for example, 6.0.1 LTS).
Frequency: Only for highly critical issues
Scope: Includes highly critical resolved issues
Versioning: A third digit designates the maintenance Feature Release (for example, 6.7.1).
Support Typically 3 years after the original publication date or until the next LTS is published (whichever date is later) Typically 6 months after the original publication date or until the next feature or LTS Release is published (whichever date is later)