Additional post-installation steps

Configure software and hardware firewalls

ECC Client computers and ECC Admin Console computers must be capable of reaching the ECC Server (or the stand alone WAMP router, if installed). Software firewalls running on each ECC Client, ECC Admin Console and ECC Server computer must permit traffic over the TCP ports that the server has configured for HTTP or HTTPS. Hardware firewalls may also require configuration to permit this traffic.

If the ECC Server is configured to send email notifications, it must access the specified SMTP server on the specified TCP port.

If the ECC Server is configured to integrate with a Keycloak server for federated user authentication, then the firewalls between the ECC Server and the Keycloak server must permit traffic on the TCP port that the Keycloak server is configured to listen on. The Keycloak server, in turn, may need firewall access for TCP ports associated with LDAP or Active Directory (i.e. TCP port 389) as well as access to TCP ports for any SMTP server configured for sending email notifications from Keycloak.

If the ECC Server is configured to integrate with a stand-alone Crossbar WAMP messaging router, then any firewalls must permit traffic on the Crossbar server's specified TCP port between the ECC Server, the ECC Admin Console computers, the ECC Client computers, and the Crossbar server. In this case, the port used by the ECC Server for its own services does not need to be permitted through the firewalls, as all access will be indirect via the Crossbar server.

Deploy and Relocate jobs require ECC Client computers to be able to communicate with each other directly. This can occur over a randomly selected pair of TCP ports, or over a specific set of inbound and outbound TCP ports. Firewall rules must permit these TCP ports or port ranges for Deploy and Relocate jobs to succeed.

The default Computer Configuration defines the range or random TCP ports for Deploy and Relocate jobs as broadly as possible; however, this range can be narrowed in each Computer Configuration so that a corresponding narrow range of TCP ports can be permitted through the firewalls to support Deploy and Relocate jobs.

Individual Deploy and Relocate jobs can be manually edited to specify a pair of TCP ports to be used for inbound and outbound communications, rather than using a randomly selected pair of ports. Collection Configurations (or "job templates") can be defined so that future Deploy and Relocate jobs specify these ports without requiring any manual editing of jobs.

For details see topic Configuring ECC Client Computers, specifically the Port Range - Minimum and Port Range - Maximum settings for a Computer Configuration. The Nuix Collector and ECC JobFile Reference has a clear description of the attributes of the SmartMoverParams element used to set the ports in Deploy and Relocate jobs.

Note: HTTPS connections for ECC Server, Crossbar and Keycloak are recommended. TCP Port 443 can be used for these connections and is generally allowed through firewalls without adding extra firewall rules. Using an SSL certificate from a trusted Certificate Authority generally requires each server having a fully qualified domain name and a corresponding pair of DNS "A" and "PTR" records.

Gather network-wide details for the collection administrator

The individuals who configure and conduct collections using Collection Center will need certain details to be able to configure their collections, including:

A list of all the computers containing files to be collected (or perhaps a comprehensive list of all computers in the organization).

A list of all the UNC shares containing files to be collected. This may include server shares, workstation shares, NAS shares and any SAMBA shares. The IT administrator or the Collections Administrator will also need a list of the User IDs and passwords needed to access these shares.

A comprehensive list of the volumes or folders on each PC to be collected.

Exporting lists from Active Directory

If your network runs on an Active Directory domain, you can export a list of users and computers from Active Directory's database. Various command line utilities and scripts are available for producing such lists. These lists can assist the collections administrator when establishing the Custodians and Targets. For details see topic Appendix C: Network Management Commands and Scripts.

Note: ECC Administration Console can directly import Active Directory users as ECC custodians. Refer to the ECC Users Guide for details on Administration Console's import capabilities.

Exporting lists from a workgroup

Networks based on Windows Workgroups have fewer network management tools available to generate reports; however, it is possible to list servers, shares and workstations using a few command line utilities. These lists will assist the collections administrator when establishing the Custodians and Targets. For details see topic Appendix C: Network Management Commands and Scripts.

Discuss collections with the collection administrator

Collections, by their nature, are data and I/O-intensive operations with significant performance and security considerations. With Collection Center, a collections administrator can easily schedule massive collections spanning tens or hundreds of systems holding several terabytes of data. Such collections can have an unintended impact on overall network performance or the performance of the servers, clients and other devices involved in the collection.

The Network Systems Administrator and the Collections Administrator should each understand the impact of large collections and know how to schedule collections in a manner that will have a minimal impact on the overall network. Consider reviewing the following discussion topics together:

Security Considerations for Destination Folders

Disk Space Considerations for Destination Folders

Network & Server Performance Considerations

Scheduling Considerations

The topic Performance Impact: Setting the Pace of a Running Collection, in the ECC Users Guide, describes methods for managing performance. The following topics in this Guide go into more detail:

Security FAQ

Performance FAQ

Networking FAQ

Ongoing Administration