Contents
1. How to configure Updater Settings for HTTP communication (instead of HTTPS)
1.1. Summary
If HTTP communication is enabled, NEXThink Updater will connect to the Engine using this mode and not HTTPS.
1.2. Applies To
NEXThink Engine V4 and higher
2. Configure
2.1. Webconsole
Connect to the webconsole with your credentials. (https://<IP_Engine>:99)
- Go to the section Engine/Updater
- Tick the state - Active -
- Change the Collector parameters needed (Force loading, Installation log, Add/Remove program entry, Control panel extension)
- Untick the box "SSL"
- Upload a file or tick - Use previously submitted zip file -
- Click on the Save button.
Note: The Engine will reboot to update these parameters.
2.2. Updater Client
You can install the Updater using various deployment tools; here's how to install using a logging script or an executable file.
2.2.1. Create a logging script
You can install Updater silently using a batch script which is going to install package with command line: msiexec /i package option. Use the following procedure:
From the desktop inside Windows, right-click on the desktop and choose New > Text Document.
- Open the text document and add the following lines:
CLS @ECHO OFF echo Installing NEXThink_Updater.msi msiexec.exe /qn /i \\server\share\NEXThink_Updater.msi UPD_IP=192.168.0.133 UPD_PORT=8888 UPD_HTTPS=0
- Save it to install.bat file.
Note: The share path should point to the location of the MSI package.
2.2.2. Use the NEXThink Updater Installer
After unzipping the collector-4.x.xxx.zip file, you can locate the tool "NEXThink_Updater_Installer_Silent.exe". You have an option to use the NEXThink Updater in http mode. The NEXThink Updater installer is graphical tool that eases the deployment of NEXThink Updater. It generates a standalone executable that, once executed, installs the Updater with pre-defined configuration.
The user may specify the IP address or the DNS name and the port number of the engine, HTTP/HTTPS mode used, a few deployment options, the directory where the executables should be generated and an optional logs directory where the installation log files are saved in case of failure. Note that The log directory should be accessible from all workstation.
2.3. Contact Information
If you require further assistance regarding the present case or if you want to contribute to the accuracy of published information, please open a case using http://support.nexthink.com.