Predator PDM IT Requirements

Predator PDM IT Requirements

Overview

IT requirements are minimal, but vital to a successful implementation. 

Software Installation

Follow How to License a New Predator Installation guide to install the Predator PDM 

Vaults Folder

The vault is stored in a folder and is located on a file share. The folder must be accessible by the Windows Service Account

Folder Requirements

  1. Accessible by the Windows service account
  2. Accessible by Predator DNC (when applicable)
Example path
  1. \\server\predator\vaults\

Windows Service Account

A service account, i.e. functional account, is widely used within Predator applications. The primary role of the service account is to facilitate access to file share. Both Predator PDM and Predator DNC will use the same Windows Service Account. 

Permissions Required

  1. Full access to the Vaults folder
  2. Ability to run Predator DNC Service (when applicable)
  3. Local Administrator Rights on Predator DNC server (when applicable)
  4. Interactive Logon must be allowed
  5. Does not expire (at minimum, expires once a year)

Example account names

  1. predator
  2. predator_admin
  3. predator_pdm

Client Requirements

Predator PDM clients have some requirements that must be followed to ensure success. 

Predator Temp Folder

  1. Create a group policy that grants Domain Users Full Control of their "C:\ProgramData\Predator Software" folder
    1. This folder is used as a local cache and is required to view files from the vault
    2. This is transparent to the end user

System Requirements

  1. .NET 3.5 is required for all clients
  2. Review What are the Predator Software System Requirements? for more details