Remote Access Configuration Network Maps for TrialDirector

TrialDirector has been tested and is only supported on a classic LAN configuration. In some instances, users may require flexibility to use TrialDirector remotely. This type of setup can be complex as TrialDirector was not developed to be used outside a LAN. Supported and Non-Supported Configuration examples and their Network Maps are listed below.

Deploying TrialDirector with Data Sync for Remote Usage (Limited Support)

  • Classic LAN is staged as the endpoint for NDS (TrialDirector Network Data Store).

  • A typical setup is over VPN, RDS, or a combination of the two. (Data Sync over LAN only)

  • Physical hardware only. No VM server or VM workstation supported.

  • NAS has been tested in this configuration, but has limited support.

  • Users must remote into a physical system at the LAN site and launch TrialDirector from there.

  • Users should NOT launch TrialDirector locally then VPN into their NDS endpoint. (Not supported)

  • Users need full Windows permissions (Read/Write/Modify/Execute) to the NDS.

  • When bringing case data local, users may need to work with their IT group to perform the task and then manually export the case to a local source. The exported case will no longer work with Data Sync. Users will have to import the case as-is, if operating from a site outside of the LAN. For more information on Data Sync, see Overview: Data Sync.

  • An example of a Supported Configuration is below:

Deploying TrialDirector with Data Sync Over VPN (No Support)

  • This type of setup is NOT supported by IPRO. The end user’s IT group will provide all support.

  • Issue: When users collaborate, Data Sync traffic is forced over WAN instead of supported LAN.

  • A Non-Supported Configuration example is below:

Deploying TrialDirector Within a Citrix Environment (No Support)

  • This type of setup is NOT supported by IPRO. The end user’s IT group will provide all support.

  • Issue: When users collaborate, Data Sync traffic could be compromised within Citrix.

  • Issue: Over Citrix, Data Sync traffic has been reported to have latency (slow and laggy).

  • Issue: Over Citrix, load balancing and multiple Citrix Servers may cause database corruption.

  • Issue: There is no official codec or video playback support in TrialDirector when Citrix is used anywhere within or outside of the TrialDirector application. Citrix should not be present anywhere on the end-user system.

  • Issue: Users are unable to reliably use Data Sync and will have issues moving their case data to their local machine to take to the courtroom. There is no mechanism in TrialDirector that allows Citrix to perform this task.

  • A Non-Supported Configuration example is below:

Deploying TrialDirector for Data Sync Within the Cloud (No Support)

  • This type of setup is NOT supported by IPRO. The end user’s IT group will provide all support.

  • Issue: When users collaborate, Data Sync traffic is slow over the Cloud application.

  • Issue: Database write failures are common when deploying to Cloud or Cloud applications.

  • Issue: Users are unable to reliably use Data Sync and will have issues moving their case data to their local machine to take to the courtroom. There is no mechanism in TrialDirector that allows for Cloud applications to do this.

  • Common Cloud-level applications are DropBox, OneDrive, ExpanDrive, Pure Storage, Amazon Web Services (AWS), Data Center deployments, SAAS / STaaS deployments, etc.

    Warning: The above list of Cloud-level applications is not a complete list. IPRO Support will not assist with any variation of this type of setup.

  • A Non-Supported Configuration example is below:

 

Related Topics

Overview: Data Sync