Applies to platforms | Windows |
Engine IP or DNS name.
Engine port number for the UDP channel.
Customer Key of the Engine Appliance.
Root CA of the Engine Appliance -leave blank if not using the Nexthink PKI.
Engine port number for the TCP channel.
Send end-user data over the TCP channel of the Collector (default starting from V6.24) instead of the traditional UDP channel. Set the option to disable to convey end-user data over UDP.
Install the Nxtcfg tool for changing the configuration of the Collector from the command line. 1: install, 0: do not install
Install the Collector Control Panel extension. 1: install, 0: do not install
Specifies whether the target system should be configured for generating memory dumps in case of STOP message (System crash). Its value can be 0 (disabled), 1 (full memory dump), 2 (kernel memory dump) and 3 (memory minidump). The recommended value is 2 (kernel memory dump).
Delay in seconds during initialization of the driver before the Collector starts sending UDP packets to the Engine. Maximum value: 240 (4 min)
Specifies the maximum CrashGuard count that the Collector can reach before canceling the loading of the driver at boot-time. If set to 0, the CrashGuard feature will be disabled
Delay Engine communication Socket Creation : To avoid having the traffic blocked by certain firewalls, the Collector socket layer is created during the last initialization steps. [1: enable, 0: disable]
Addition of log rotation when enabling DRV_LOGMODE for the logging [Range for value: 1 -> 512 (MB)].
Reactivate the Collector once the given time (in hours) has elapsed after it reached the maximum CrashGuard count. The max value is 8766 hours (1 year). Default is 7 days (168 hours).
Integer number to identify and organize installations of the Collector. Possible values range from 0 to 2147483647.
Character string to identify and organize installations of the Collector. Possible values are any string with up to 2048 characters.
Specifies the logging mode. Possible values are 0, 1 and 2, meaning Silent, Verbose and Debug, respectively. 2 (Debug) is not recommended.
Disables Windows enumerate functionality. Possible values are 0, 1. If set to 1, the Collector does not report when there is a Windows freeze or when the application stops responding.
(This will result in the Finder not displaying any information about "application not responding".)
“CrashGuard Protection Interval Value”. It is the time interval since boot (in minutes) after which a dirty reboot does not increase the CrashGuard. Default is 4 hours (240 min).
Maximum size of the UDP packet for transfers between the Collector and the Engine. Allowed values range from 1000 to 16384.
Period, in hours, in which the Collector checks for new installed packages and updates and reports them. Allowed values range from 0 to 24:
Gather Web and Cloud information. Default value is 1 to gather and send the data (only if you have purchased the Web and Cloud product). Set to 0 for not recording the web connections of devices.
List of comma separated host names for which to send the full URL of each web request. Requires the Web and Cloud product and the parameter DRV_WEB_AND_CLOUD_DATA to be set to 1.
Disable print notifications. Starting from version 6.18 the Collector does not report printing information by default. Set the option to enable to report printing activity and to disable to not report it.
Disable SMB print notifications. Starting from version 22.214.171.124, the Collector does not report SMB prints by default. Set the option to 0 to enable SMB print reporting (requires PRINTING enabled). Set to 1 to disable it.
Favor IPv6 over IPv4 (or viceversa) for communicating with the Engine. When the DNS lookup of the name of the Engine resolves to both IPv6 and IPv4 addresses, prefer IPv6 when set to 1 and IPv4 when set to 0.
Enable the reporting of user logon events and user interactions in virtualized and embedded (kiosk mode) environments. Set to 1 to enable.
Execution policy of remote actions. Possible values:
Disable the rule-based Collector Assignment. Starting from version 6.19 the Collector can be dynamically assigned to Engines and entities based on a set of configurable rules. Set the option to enable to activate the rule-based assignment in the Collector.
Enable the features to engage with the end-users either on all devices or only on those that are not running a server OS. Possible values:
URL of the PAC file to automatically configure the proxy settings
The FQDN or IP address of the proxy in manual proxy configuration
The port number where the proxy is listening in manual proxy configuration
chrome.exe,firefox.exe,iexplorer.exe, winword.exe,excel.exe,powerpnt.exe, outlook.exe,onenote.exe,onenoteim.exe, onenotem.exe,lync.exe,zoom.exe
The list of applications whose startup duration is measured
Setting the ARPNOREMOVE property disables the Add or Remove Programs functionality in Control Panel that removes the product. For Windows 2000, this disables the Remove button for the product from the Add or Remove Programs in Control Panel. For earlier operating systems, this has the effect of removing the product from the list of installed products on the Add or Remove Programs in Control Panel.
Set the ARPNOREPAIR property to disable the Repair button in the Programs Wizard.
Setting the ARPSYSTEMCOMPONENT property to 1 using the command line or a transform prevents the application from being displayed in the Add or Remove Programs list of Control Panel.
Setting the ARPNOMODIFY property disables Add or Remove Programs functionality in Control Panel that modifies the product. For Windows 2000, this disables the Modify button for the product in Add or Remove Programs in Control Panel. On earlier operating systems, clicking the Add or Remove Programs button uninstalls the product rather than entering the maintenance mode wizard.
Note: the Collector MSI package does not support this feature. ARPNOMODIFY must bet set to 1.
The REBOOT property suppresses certain prompts for a restart of the system. An administrator typically uses this property with a series of installations to install several products at the same time with only one restart at the end.
The ForceReboot and ScheduleReboot actions inform the installer to prompt the user to restart the system. The installer can also determine that a restart is necessary whether there are any ForceReboot or ScheduleReboot actions in the sequence. For example, the installer automatically prompts for a restart if it needs to replace any files in use during the installation.
You can suppress certain prompts for restarts by setting the REBOOT property as follows.
REBOOT = Force Always prompt for a restart at the end of the installation. The UI always prompts the user with an option to restart at the end. If there is no user interface, and this is not a multiple-package installation, the system automatically restarts at the end of the installation. If this is a multiple-package installation, there is no automatic restart of the system and the installer returns ERROR_SUCCESS_REBOOT_REQUIRED.
REBOOT = Suppress Suppress prompts for a restart at the end of the installation. The installer still prompts the user with an option to restart during the installation whenever it encounters the ForceReboot action. If there is no user interface, the system automatically restarts at each ForceReboot. Restarts at the end of the installation (for example, caused by an attempt to install a file in use) are suppressed.
REBOOT = ReallySuppress Suppress all restarts and restart prompts initiated by ForceReboot during the installation. Suppress all restarts and restart prompts at the end of the installation. Both the restart prompt and the restart itself are suppressed. For example, restarts at the end of the installation, caused by an attempt to install a file in use, are suppressed.
Starting from V6, the Collector is usually able to upgrade without the need to reboot the device. Only when migrating from V5 or when the target device interferes with the installation process (for instance, by running the Collector Control Panel extension during installation), a reboot is necessary. Set the REBOOT option in these cases to specify your choice.
For instance, if you do not want your devices to reboot right away after a V5 to V6 migration, set REBOOT=ReallySuppress. As a drawback, if you set this option, the upgrade to V6 will not be complete until the end-users reboot their devices.
In unattended execution mode, all choices are silently accepted. For example, if REBOOT=Force, the computer will automatically be rebooted after the MSI package installation.
Casing of properties
Always specify the names of the parameters (the properties) of the MSI in capital letters. If you include the properties with lower case letters in an MST, they will be considered private properties and you will not be able to modify them later from the command-line.
The operations described in this article should only be performed by a Nexthink Engineer or a Nexthink Certified Partner.
If you need help or assistance, please contact your Nexthink Certified Partner.