Installing web protection components

Before you begin

For information about version compatibility, see the Version Equivalencies Between Forcepoint DLP and EIP Infrastructure/Web/Email Components.

Complete these steps to install one or more web protection software components on Windows.
Important: If, when installing v8.5.4, you encounter the error ‘Installation failed with error code 3004’, refer to the Installation Guide for instructions.

To install web protection components on a Linux machine, see Installing Web Protection Components on Linux.

If you are distributing components across multiple machines, run the installer and complete the installation steps on each machine.

These instructions assume that you have already launched the installer and selected Custom. (For instructions on performing these steps, see Deployment section in Installing components via the Custom option.) If you are adding components, skip to Step 2.

Steps

  1. On the Custom Installation dashboard, click the Forcepoint Web Security or Forcepoint URL Filtering Install link.
    The web protection component installer is launched.
  2. Use the Select Components screen to identify the component or components to install on this machine. As you make your selection, remember that:
    • Policy Broker, Policy Server, and Filtering Service must be installed in the order listed, and before any other web protection components. (If you select all 3 at the same time, they are installed in the correct order.)
    • The Web Security module of the Forcepoint Security Manager is available only when Forcepoint Infrastructure is already installed on the machine (see Installing Forcepoint Infrastructure).
    • Note that in an appliance-based deployment, a Web mode appliance running in full policy source mode has Policy Broker already installed and running. In this scenario, there can be only one Policy Broker for the deployment.
  3. Depending on the components selected, some or all of the following installer screens appear. (The parenthetical information below indicates which components or machine conditions cause the screen to appear.)
    Click the screen name for instructions.
    • Policy Server Connection Screen (Filtering Service, Network Agent, Usage Monitor, Forcepoint Security Manager [Web Security module)\], Real-Time Monitor, Log Server, User Service, DC Agent, Logon Agent, eDirectory Agent, RADIUS Agent, State Server, Remote Filtering Client Pack, Remote Filtering Server, Linking Service, Sync Service, or Directory Agent)
    • Policy Broker Connection Screen (Policy Server, Sync Service, or Directory Agent)
    • Select Policy Broker Screen (Policy Server)
    • Multiple Network Interfaces Screen (if multiple NICs detected)
    • Active Directory Screen (if installing User Service, DC Agent, or Logon Agent on Windows Server)
    • Computer Browser Screen (if installing User Service, DC Agent, or Logon Agent on Windows Server and the Computer Browser service is not running)
    • Integration Option Screen (Filtering Service)
    • Select Integration Screen (Filtering Service, to be integrated with a third-party product, or Filtering Plug-In)
    • Network Card Selection Screen (Network Agent)
    • SQL Server Native Client Tools (management module or Log Server)

      If the installer appears in the foreground, follow the prompts to install the required tools.

    • Database Information Screen (Log Server)
    • Log Database Location Screen (Log Server)
    • Optimize Log Database Size Screen (Log Server)
    • Feedback Screen (Filtering Service or Network Agent)
    • Directory Service Access Screen (User Service, DC Agent, or Logon Agent)
    • Remote Filtering Communication Screen (Remote Filtering Server)
    • Remote Filtering Pass Phrase Screen (Remote Filtering Server)
    • Filtering Service Information for Remote Filtering Screen (Remote Filtering Server)
    • Filtering Service Communication Screen (Network Agent, a filtering plug-in, or Linking Service)
  4. On the Installation Directory screen, accept the default installation path, or click Choose to specify another path, and then click Next.
    The installation path must be absolute (not relative). The default installation path is one of the following:
    • C:\Program Files (x86)\Websense\Web Security (on the Forcepoint management server)
    • C:\Program Files\Websense\Web Security (on servers that do not have management components)

    The installer creates this directory if it does not exist.

    Important: The full installation path must use only ASCII characters. Do not use extended ASCII or double-byte characters.
    The installer compares the installation’s system requirements with the machine’s resources.
    • Insufficient disk space prompts an error message. The installer closes when you click OK.
    • Insufficient RAM prompts a warning message. The installation continues when you click OK. To ensure optimal performance, increase your memory to the recommended amount.
  5. On the Pre-Installation Summary screen, verify the information shown.
    The summary shows the installation path and size, and the components to be installed.
  6. Click Next to start the installation. An Installing progress screen is displayed. Wait for the installation to complete.
  7. On the Installation Complete screen, click Done.
    Additional configuration may be necessary if you are integrating Forcepoint URL Filtering with another product. See:
    • Integrating Forcepoint URL Filtering with Cisco
    • Integrating Forcepoint URL Filtering with Citrix
    • Integrating Forcepoint URL Filtering with TMG
    • Installing for Universal Integrations