Ctrlk
Support

Installing Collector on Windows

1

Double-click the appropriate Nexthink Collector installer executable file for generating either:

  • A silent installer: Nexthink_Collector_Installer_Silent.exe

  • An installer that opens a command-line window: Nexthink_Collector_Installer.exe

2

Specify the configuration settings of the Nexthink instance that will receive the data under Nexthink Appliance settings:

Address

Use the URL of your Nexthink instance, sometimes referred to as the destination URL.

Data over TCP

Select the option to send data over a TCP channel.

Ports (TCP)

443

Ports (UDP)

This feature must not be selected when using the Nexthink cloud platform.

DNS

Tick the option Prefer IPv6 if you want the Collector to favor the use of IPv6 over IPv4 to communicate with the instance.

3

Set the General settings. Optionally tick the box for any additional setting. In particular:

  1. Installation options that are not shown in the dialog box take their default value. Check Install configuration tool to modify them later with the Collector configuration tool. In the case of an update, the values of the non-visible settings are preserved from the previous installation.

  2. Check the option Web and Cloud Data if you have purchased the Web and Cloud product. Furthermore, click the button Settings to the right of this option to open a dialog box where you can list the domains for which you want to store the full URL paths of web requests. That is, for every web request that falls under one of the specified domains, Collector reports the full URL path and not just the domain.

  3. Check the option Use the assignment service if you have activated the rule-based assignment of Collectors.

  4. Select the activation of the Engage features depending on the target operating system:

    • Enable except on servers: Collector launches campaigns only on devices that do not run a server operating system.

    • Enable on all devices: Collector launches campaigns on devices with any type of operating system.

    • Disable: Collector ignores campaigns.

  5. Select the Script execution policy for remote actions that Collector will run on the device:

    • Signed by a trusted publisher or by Nexthink (default): Collector runs on the device, only those remote actions with a PowerShell script that is signed either by Nexthink or by a company whose certificate is listed in the Trusted Publishers certificate store.

    • Signed by a trusted publisher: Collector runs on the device, only those remote actions with a PowerShell script that is signed by a company whose certificate is listed in the Trusted Publishers certificate store.

    • Disabled: Collector runs no remote action on the device.

    • Unrestricted: Collector runs any remote action on the device, regardless of the digital signature of its script.

  6. Optional: Type in an integer number (0—2147483647) as Collector tag to identify the group of Collectors generated with the installer. The Collector tag is useful for defining the entities to build up hierarchies.

  7. Optional: For more flexibility in the identification of Collectors, type in a label (maximum 2048 characters) as Collector string tag to identify the group of Collectors generated with the installer. The Collector string tag is useful for defining the entities to build up hierarchies.

  8. Choose the Customer Key file that protects the connection to the Nexthink instance.

  9. Specify a couple of directories:

Output directory

Select Browse to select the folder in which the executable files of both Collector install and uninstall will be created.

Optional: Logs directory

Type in the network place where Collector deployed with this method must save the installation logs.

4

Optionally provide the custom proxy settings of Collector under the Proxy configuration section:

  1. Select Automatic proxy to provide a PAC file for the automatic configuration of the proxy settings.

PAC address

URL of the PAC file

  1. Select Manual proxy to manually provide the proxy settings.

Proxy address
FQDN of the proxy

Proxy port

Port number to which the proxy is listening

5

Click Create to trigger the generation of three files:

  • Executable file to install the Collector: NEXThink_Collector<Nexthink_Experience_FQDN>.exe

  • Executable file to uninstall the Collector: NEXThink_Collector_Uninstaller<Nexthink_Experience_FQDN>.exe

  • Text file with the list of the settings used to create the executable installer: NEXThink_Collector<Nexthink_Experience_FQDN>.exe.txt

6

Select OK to close the dialog box.

Exit code
Description

0

Success; reboot is not required

-1

Success; reboot is required

3

Failure; the Collector installation started but msiexec failed

other

Failure; the actual value corresponds to a Windows internal error code

Exit code
Description

0

Success; reboot is not required

-1

Success; reboot is required

1

Success; Collector was not found and nothing was uninstalled

3

Failure; Collector uninstallation started but msiexec failed

other

Failure; the actual value corresponds to a Windows internal error code

Parameter
Description

DRV_IP

Provide the FQDN of the Nexthink instance. URL structure: <customer_name>.data.eu.nexthink.cloud

CRD_PORT

Value: 443

CRD_KEY

Provide a customer key that has been provided to you by your Nexthink representative. Open the key file in text editor, copy the entire text and paste it to the MSI editor as the property value.

DATA_OVER_TCP

Enable to send end-user data over the TCP channel of Collector

Parameter
Description

VDI_PLATFORM_TYPE

Force the detection of Citrix or Azure Virtual Desktop (AVD) / Cloud PC (CPC) if there are multiple agents in a given VM.

Values:

  • Auto: Auto detection using agent registry keys when available

  • AVD: Forces AVD detection; prevents Windows365 detection

  • AWS: Forces AWS detection

  • Citrix: Forces Citrix detection

  • Horizon: Forces Horizon detection

  • Windows365: Forces Windows 365 / CloudPC detection

  • Missing or unknown value: Auto detection using agent registry keys when available

VDI_CLIENT_PLUGIN_PING_ADDRESS

Set the host to ping from the client to calculate ISP and WAN latency. This information is pushed from the VM to the client. Populated NQL data model field: client.network.wan_latency

Key name
Description

Platform

Controls the VDI platform type that the Collector detects or forces to use.

Location: HKEY_LOCAL_MACHINE\SOFTWARE\Nexthink\Collector\VDI

Possible values:

  • Auto: Auto detection using agent registry keys when available

  • AVD: Forces AVD detection; prevents Windows365 detection

  • AWS: Forces AWS detection

  • Citrix: Forces Citrix detection

  • Disabled: Detection disabled

  • Horizon: Forces Horizon detection

  • Windows365: Forces Windows 365 / CloudPC detection

If not set, the default value is Disabled.

  • Missing or unknown value: Auto detection using agent registry keys when available.

ClientPingAddress

Selects which IP address will be used by the connected plugin to calculate ISP and WAN latency.

Location: HKEY_LOCAL_MACHINE\SOFTWARE\Nexthink\Collector\Sessions

Any string is a valid value. Examples:

  • IPv4: x.y.z.a

  • IPv6: ::1

  • Domain: domain.com

1

Double-click the NEXThink_Collector.msi file to start the installation program.

2

After reading the welcome message, select Next.

3

Fill out the form of installation settings:

Appliance Name or IP address

FQDN of your Nexthink instance

Appliance TCP Port

443

Customer Key

Copy to this field the content of the file that holds the customer key of the Nexthink instance:

  1. Open the customer key file using Notepad.

  2. Press Ctrl+A to select all the text.

  3. Press Ctrl+C to copy the text.

  4. Back in the Customer Key field, press Ctrl+V to paste the copied key.

4

Select Next.

5

The installer is now ready and you can click Install to begin the actual installation.

6

Click Finish to close the installation wizard once it has been completed.

Parameter
Description

DRV_IP

FQDN of your Nexthink instance

CRD_PORT

443

CRD_KEY

The customer key of the Nexthink instance

Field
Description

Name

A unique name for the collection.

Comment

Optional field

Comment describing the intent of the collection.

Limiting collection

Optional field

Click Browse to select a collection that puts a limit on the members of the current collection or select All systems in order to not limit the current collection.

Key

HKEY_LOCAL_MACHINE\SOFTWARE\Nexthink\Collector\VDI

Name

IcaVideoMetricsInterval

Enabled Value

dword:00000003

Disabled Value

dword:00000000 or missing value

DRV_CRASHGUARD

The maximum number of consecutive abruptly terminated sessions after which Collector cancels the loading of its drivers. Default is five sessions.

DRV_CGPI

The time interval in minutes after system startup during which the CrashGuard protection mechanism recognizes abrupt terminations as genuine crashes. Default is 240 min (4 hours).

DRV_REACTIVATION

The waiting time, expressed in hours, from the moment that the loading of Collector is deactivated because the CrashGuard counter reached its maximum specified count until the moment it is reactivated. Default is 168 hours (7 days).

The following sections explain the Collector installation and deployment methods in detail.

See the Installing Collector documentation to learn how to decide on the installation and deployment method applicable to your infrastructure.

Before you begin

Before you begin the installation procedure, ensure you have the following things:

  • URL of your Nexthink instance, including data in the path: <instance>.data.<region>.nexthink.cloud For more information about the URL, see the Connectivity requirements.

  • One or more Windows devices on which to install Collector.

  • Administrator credentials in your Nexthink instance.

  • The Collector installation package; see the obtaining Collector section.

  • The customer key in the Customer Key.txt file, which you receive in your welcome email from Nexthink.

  • The root certificate associated with your Nexthink instance.

  • Optional: A third-party deployment tool or Unified Endpoint Manager (UEM), such as Microsoft Intune.

Ensure that no version of Nexthink Collector is running on the Windows instance. When applicable, uninstall the existing Collector version.

Installation procedure overview

This section outlines the installation procedure and the decisions you have to take before and during the process. On a high level, the procedure includes the following steps:

VDI Client Extension is enabled automatically for all devices in your environment when using VDI Experience. Ensure you are using Collector version 25.4.1 or above.

For older Collector versions, Nexthink recommends upgrading to the most recent Collector version to ensure that the VDI Client Extension is enabled without requiring redeployment.

Proceed by reading the relevant section based on the endpoint agent you selected in the previous step.

Collector installation overview

This section outlines the Collector installation process. To get started, take the small-scale setup or medium to large-scale setup installation path based on the scale of your environment.

Installing Collector for a small-scale setup

Small-scale setups include, for example, proof-of-concept scenarios and unmanaged environments.

  1. Obtain Collector

  2. Configure Collector with your client information using the Nexthink Collector Installer or the Windows Installer

  3. Install Collector on a single endpoint device

  4. Ensure a good connection to your Nexthink instance; if needed, troubleshoot by reconfiguring Collector

  5. Manually install Collector on the rest of the endpoint devices

Installing Collector for a medium to large-scale setup

Medium to large-scale setups include managed IT environments with, in many cases, thousands of endpoint devices. Select your device type from the following tabs to see the installation steps.

  1. Understand the general prerequisites

  2. Obtain Collector

  3. Configure Collector with your client information using the Windows Installer

  4. Install Collector on a single endpoint device

  5. Ensure a good connection to your Nexthink instance; if needed, troubleshoot by reconfiguring Collector

  6. Deploy Collector to the rest of the endpoint devices using a deployment method applicable to your infrastructure

Perform the deployment by following the procedures in the relevant subsections in this documentation:

Last updated

Was this helpful?