Follow

How To Configure the eDiscovery Public Site Server and Collections

Created by: Justin Johns
Created date:
Last Updated date:

Question

How does one setup Public Site Server and configure an Agent collection through the Public Site Server?

 

Overview 

Public Site Servers are used to collect from machines that are not on the internal network or VPN.  Agents can then be set up to periodically "phone home" to the Public Site Server to get any queued jobs issued to them.

 

Prerequites

  • A functioning eDiscovery environment with at least one Site Server.
  • A DMZ where the Public Site Server can reside.
  • Allow bidirectional communication between the Root Site Server to the and the Public Site Server over port 54545.
  • Allow bidirectional communication between the Public Site Server and the Internet over port 54545.

 

Site Server Setup

The following IPs are used in the examples below:

  • Root Site Server - 10.2.3.51 (internal IP)
  • Public Site Server - 10.2.3.52 (internal IP); 153.20.16.87 (external IP)

  1. Install a Public Site Server in the DMZ.
    Note: As long as the DMZ machine is only running PostgreSQL and the Public Site Server, this machine can be off-domain and Public Site Server can be run by the "Local System" account.
  2. Expose port 54545 of the Public Site Server so that it can be seen publicly.
  3. Configure the Root Site Server to point to the Public Site Server as a Child Instance.  The below screenshot shows the Public Site Server's internal IP of 10.2.3.52.
  4. Configure the Public Site Server to point to the Root Site Server as a Parent Instance.  The below screenshot shows the Root Site Server's internal IP of 10.2.3.51.
  5. Configure the Public Site Server to know its internal and external IPs.  The above screenshot shows the Public Site Server's internal IP of 10.2.3.52, and external IP of 153.20.16.87.
  6. Confirm that the Site Server Console in eDiscovery shows that both the Root and Public Site Servers are online.
  • Root Site Server (single server install) - 10.2.3.51
  • Public Site Server - 10.2.3.52 (internal IP); 153.20.16.87 (external IP)

 

Agent Setup

Public Agents can be installed manually, using the PUBSS argument to point the the Public Site Server's public IP as show in the example below.

MSIEXEC /I "<path>\AccessData Agent (64-bit).msi" CER="<path>\<certificate_name>.crt" PUBSS=153.20.16.87:54545

 You can also modify your Agent installer MSI to point to your Public Site Server, so that pushed Agents can use the Public Site Server when they are off-network.

Data Source

Public Agents/targets should be added to Data Sources > Computers using the target's FQDN.

 

Jobs

Any Computer collection jobs whose IPs are outside of the Managed Subnet ranges of other Site Servers will be assigned to the Public Site Server.  By default, each public Agent will check-in every 30 minutes to see if the Public Site Server has a job waiting for it.

 

Note

Public collection jobs generally take longer than a typical internal collection due to check-ins and internet traffic/speeds.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk