Host System Requirements
In this section, we'll cover the server requirements for the various component host systems.
The Privileged Identity software is a 32-bit application that runs in a WOW64 environment on 64-bit systems. For a production install of Privileged Identity, you must have a Windows Server operating system. Privileged Identity is fully supported on a physical server or virtual machine. All service pack levels and editions are supported except where specifically noted.
|Minimum Requirements||Suggested Configuration|
|Windows Server 2012 R2 or later||The most current version of Windows Server|
|2GB of RAM||
2GB of RAM for the software
4GB of RAM for the program database
~1GB of hard drive space to install
This does not include space required by log files, which are enabled by default and can consume large amounts of space over time.
|4GB of hard drive space to install and for local log files|
|Intel or AMD multi-core system||Intel or AMD processors with 4 or more CPU cores|
|Microsoft .NET Framework 4.5.2 or later||
The most recent version of Microsoft .NET Framework from the 4.x family
To download the most recent version of .NET, please see https://dotnet.microsoft.com/download.
|Windows Management Framework 4.0 or later||
The most recent version of Windows Management Framework
To download Windows Management Framework 5.1, please see www.microsoft.com/en-us/download/details.aspx?id=54616.
- When managing COM on Windows 2000 target systems, there will be inconsistencies with Remote COM management interfaces, as your host operating system will not match. This is by Microsoft's security design.
- Take note of any components which will manage databases other than Microsoft SQL Server. This should include the management console as well as any deferred or zone processors. These components must have the most recent 32-bit OLE DB providers installed, typically available from the database provider.
- To integrate System Center Service Manager (SCSM) or System Center Operations Manager (SCOM), you must obtain the appropriate SDK binaries from the SCSM or SCOM installation directory and place them into the Privileged Identity installation or zone processor directory.
- A poorly configured virtual host can impede the software's ability to work. Make sure that the recommended resource allotments for each component have been met, and if possible, allow for dynamic increases in memory and storage. Supported host virtualization platforms are Hyper-V Server 2012 R2 or later, VMware ESX, and VMware Workstation.
- For lab environments, Windows 10 Professional 64-bit will suffice. Workstation-class operating systems are not supported in production environments.
You may need to install IIS on the management console host system and zone processor host systems, even if the web app will not be installed on those systems. Some IIS components are required to install the web app to a remote server and to manage remote IIS installations.
For more information about installing these required components, please see Install Server Components.
The Privileged Identity web application provides access to managed credentials and other functionality using a web browser.
Because the web app is deployed as an IIS web application, you must install certain components of IIS on the host server. The web app requires IIS 8.5 or above, which, in turn, requires Windows Server 2012 R2 or above (we recommend using the most current version of Windows Server).
These requirements differ from those for the web service host.
For more information, please see Install Server Components.
The management console can push the web application to the same system or to a remote web server.
The Privileged Identity web service is required by the web app, PowerShell, and session recording.
You must install certain components of IIS and application server roles on the host server. The web service requires IIS 8.5 or above, which, in turn, requires Windows Server 2012 R2 or above. We recommend using the most current version of Windows Server.
These requirements differ from those for the web app host.
Also, a valid SSL certificate is highly recommended. Certificate and authentication configuration affect browser support.
If the web service is hosted at a different URL than the web app, CORS support (Cross-Origin Resource Sharing) must also be enabled in the web service's web.config file, and additional browser configuration may be required.