Collector Installation Guide (📺)

Install on premise Collectors for Windows File Share and iManage Work.

How To Video:

ActiveNav Cloud supports two on premise collectors: Windows File Share and iManage Work. The system requirements and installation steps for both collector types are the same. 

NOTE: We do not recommend installing more than one Collector on a server. Each Collector service should be installed on a dedicated virtual or physical machine. The service should not be installed alongside other applications or server roles (such as Active Directory, mail server, file server, web server, etc.). User access to the host server should be minimized for security isolation and performance reasons.

We also recommend that the server is configured with end point protection to ensure any attack surface is minimized and that robust anti-malware and firewall protection is configured to protect the server from malicious attacks.

Installation Pre-Requisites

ActiveNav Cloud Configuration

Ensure you have considered your Collector Groups configuration. See  Managing Collector Groups for more detail. You will need the Collector Install ID for your target Collector Group.

Once your Collector is installed, you will require credentials. For Windows File Share, see Adding Basic Credentials. For iManage Work, see Adding iManage Work Credentials

Hardware and OS

  • Windows Server 2019
  • 4 CPU
  • 8 GB RAM
  • 100 GB Data Volume - temp space used during discovery

File Locations

Windows File Share
  • C:\Program Files\ActiveNav\Collector
  • C:\ProgramData\ActiveNav\Collectors\Logs

iManage Work

  • C:\Program Files\ActiveNav\Collector-iManageWork
  • C:\ProgramData\ActiveNav\Collectors\Logs-iManageWork

Network Readiness

The server hosting the Collector must allow outbound connectivity to the ActiveNav Cloud service. The ports and hosts required for each deployed instance are defined in the table below.

Description Port Numbers Host(s) - EUS2 Instance Host(s) AUSE instance
ActiveNav Cloud - User Interface 443 (HTTPS) eus2.cloud.activenav.com ause.cloud.activenav.com
ActiveNav Cloud - API endpoint 443 (HTTPS) api.eus2.cloud.activenav.com api.ause.cloud.activenav.com
ActiveNav Cloud -Collector Storage Accounts 443 (HTTPS) stancoleus2.blob.core.windows.net stancolause.blob.core.windows.net
ActiveNav Cloud -Tenant-specific key vault 443 (HTTPS) kv-an-col-{Identifier}-eus2.vault.azure.net kv-an-col-{Identifier}-ause.vault.azure.net
Microsoft login service 443 (HTTPS) login.microsoftonline.com login.microsoftonline.com
Azure AppInsights Telemetry 443 (HTTPS) dc.applicationinsights.azure.com
dc.applicationinsights.microsoft.com
dc.services.visualstudio.com
dc.applicationinsights.azure.com
dc.applicationinsights.microsoft.com
dc.services.visualstudio.com
Azure Service Bus 443 (HTTPS), 5671 (AMQP), 5672 (AMQP) sb-an-col-eus2.servicebus.windows.net,
sb-an-colplat-eus2.servicebus.windows.net
sb-an-col-ause.servicebus.windows.net,
sb-an-colplat-ause.servicebus.windows.net

The simplest solution will be to enable outbound access to the HTTPS port for any host, and to add explicit access to the AMQP ports for the Azure ServiceBus hosts. If you wish to maintain the tightest configuration possible you will need to request your tenant specific key vault host before installation to be able to make all necessary configuration changes.

If you are unsure about the access to these ports you can use PowerShell on the Collector host system to check connectivity by running the Test-NetConnection command for each host and port.

The example below shows evaluation of connectivity for the required ports for the sb-an-col-eus2.servicebus.windows.net Azure ServiceBus endpoint.

Test-NetConnection sb-an-col-eus2.servicebus.windows.net -Port 5671
Test-NetConnection sb-an-col-eus2.servicebus.windows.net -Port 5672
Test-NetConnection sb-an-col-eus2.servicebus.windows.net -Port 443

In the results you should check for the "TcpTestSucceeded: True" indication:



If you are not able to configure access using the hostnames for the required endpoints you can use a tool such as nslookup to resolve the hostname to an IP address. However it is possible that service changes within Azure lead to the underlying IP address changing and impacting on Collector connectivity.

Repository Access

The server also requires outbound network connectivity to the target repositories on their respective ports: Windows File Shares use SMB/CIFS (port 445), and iManage Work Collector uses HTTPS (443). We recommend the server is co-located (i.e., in the same data center, office, or cloud region) on a gigabit speed network with the target repositories.

Collector Installation

  1. Download the Collector installation package.
    1. Log into ActiveNav Cloud as an Administrator. Under the Discovery menu, select the Collectors page.
    2. Choose the tab for the collector type you wish to install, Windows File Share or iManage Work.WFSCollectorsiManageCollectors
    3. Click the Release Note button to retrieve the latest information about the installation.
    4. Click the Download button to retrieve the MSI.
  2. Copy the Collector Install ID from the Collector Group where you want to register your new collector.
  3. Once the download is complete, double click the MSI file to start the installation.
  4. Paste the Collector Install ID into the Collector Registration ID <validate this name> field and add a descriptive Collector Name.iManageCollectorInstall
  5. On the next screen, click the Install button to begin the installation.
  6. You may be prompted by Windows User Account Control to allow changes to the server. Click Yes to proceed.
  7. The installation may take up to 10 minutes to complete as the software must register with the ActiveNav Cloud service. Once the installation is complete, click the Finish button to close the setup application.
  8. The new collector will be listed in the target Collector Group.iManageCollectorsPopulated