Safeguard Desktop Player system requirements
The Safeguard Desktop Player application supports the following platforms:
-
Microsoft Windows:
64-bit version of Windows 7 or newer. Install the appropriate driver for your graphic card.
-
Linux:
RHEL 6, CentOS 6, or newer. The Safeguard Desktop Player application will probably run on other distributions as well that have at least libc6 version 2.12 installed.
-
Mac:
macOS High Sierra 10.13, or newer.
Installing the Safeguard Desktop Player application requires about 120MB disk space, and a temporarily used disk space to store the audit trails that are replayed. The size of the temporary files depends on the size of the replayed audit trails.
You can install the Safeguard Desktop Player application with user privileges.
Hardware specifications
The One Identity Safeguard for Privileged Sessions (SPS) appliances are built on high performance, energy efficient, and reliable hardware that are easily mounted into standard rack mounts.
The following sections provide detailed information of SPS appliances.
Topics:
Product licensing
To enable a trial license
-
Visit the Download Trials page, and navigate to One Identity Safeguard for Privileged Sessions > Download Free trial.
-
Complete the registration form, and click Download Trial.
-
You will receive the details on how to access your license key and the download the ISO files in email.
To enable a purchased commercial license
- Navigate to My Account > My License Assets on the support portal.
- To access your license key, click Retrieve Key next to your product.
- Once you have the license keys, navigate to My Account > My Products and click Download next to your product. The Download Software page is displayed.
- Download the ISO image (install cdrom) of your product.
If you need help with accessing your license, navigate to the Licensing Assistance page, and follow the instructions on screen.
Upgrade and installation instructions
The One Identity Safeguard for Privileged Sessions appliance is built specifically for use only with the One Identity Safeguard for Privileged Sessions software that is already installed and ready for immediate use.
To upgrade to One Identity Safeguard for Privileged Sessions6.5
For step-by-step instructions on upgrading to SPS6.5, see Upgrade Guide.
Due to legal reasons, installation packages of the external indexer application will be available only from the SPS web interface. After SPS versions 6.4 and 6.0.3 are released, the installation packages will be removed from our website.
About feature releases
This is a feature release, which means that it will be supported for 6 months after the release date or 2 months after the release of a succeeding feature release (whichever date is later). It also means that if you are running a previous feature release (such as versions 6.1), you have 2 months to upgrade to version 6.5 if you want to keep running on a supported release.
For a full description of long-term-supported and feature releases, open the SPS product page on the Support Portal and navigate to Self Service Tools > Product Support > Product Life Cycle & Policies > Product Support Policies > Software Product Support Lifecycle Policy.
If you have a physical appliance based on MBX hardware
One Identity recommends you to upgrade to SPS6.5, if you are not running SPS on Pyramid hardware and any of the following is true:
If you do not know the type of your hardware, see If you have a physical appliance based on Pyramid hardware.
-
You wish to take advantage of any of the new features.
-
You are running a previous feature release.
-
You are OK with having to continuously upgrade to the latest feature release to remain supported.
We are releasing new feature releases approximately once every 2 months.
If you have a physical appliance based on Pyramid hardware
Do NOT upgrade to SPS6.5 if you are running SPS on Pyramid hardware:
Downgrading from a feature release
Do NOT downgrade from a feature release.
|
|
Caution:
Downgrading from a feature release is not supported. If you upgrade from an LTS release (for example, 4.0) to a feature release (4.1), you have to keep upgrading with each new feature release until the next LTS version (in this case, 5.0) is published. |
