Contents
1. NEXThink Collector V4.0.0.79
1.1. Fixed Issues
1.1.1. Collector
Correct SMB share unavailable (with Juniper) if the driver stack (IrpStackSize) is set to 1.
1.2. Supported operating systems
- Windows 2000 SP4 - 32 bits
- Windows 2003 Server (for Citrix / Terminal Services server) - 32 and 64 bits
- Windows 2008 Server (for Citrix / Terminal Services server) - 32 and 64 bits
- Windows XP - 32 and 64 bits
- Windows Vista - 32 and 64 bits
- Windows 7 - 32 and 64 bits
2. Collector V4.0 Deployment
2.1. Before You Begin
As is the case with all software installation, it is recommended to back up all critical information on the target equipment.
2.2. Software Requirements
- UDP communication allowed between target workstation and NEXThink Engine.
- The Collector V4.0 is compatible with one of the operating systems listed above.
- To install the Updater/Collector MSI, the minimum version 3.0 of the Windows installer (msiexec) is required.
2.3. Dependency Matrix
|
Engine 3.2 |
Engine 4.0 |
Collector 3.2 |
OK |
OK |
Collector 4.0 |
- |
OK |
2.4. Installation Procedure
MSI packages are provided, allowing installation, upgrades and uninstallation of the Collector. Detailed instructions can be found on our documentation website http://doc.nexthink.com/.
Any upgrade or removal of the Collector requires a computer restart for changes to become effective.
2.5. Upgrade Considerations
The installer will handle the upgrading process. There is no need to configure the deployment tool for uninstalling previous versions before deploying the present Collector version.
If you are using Updater Add-ons, this component will make the upgrade of the Collector in Finder tab named - Collector Management -.
2.6. What's new in V4
Some new improvements:
- Manage the installation of the Collector with Updater Add-ons.
- Known applications ran from an USB stick. (improvement from Win7)
- Optimization of the load of data sent.
- Retrieve Anti-virus informations.
- Detection of the health of your HDD.
- Printers usage into your network.
- Computer and Application Performance monitoring.
- Detect the user activity.
3. Known Limitations
Issues |
Workaround |
MSI issue on some systems. This problem can occur when one uninstalls manually the old MSI version and install the new version of the Collector (#2519) |
None. |
SMB traffic isn't accurate on some systems (FAQ Collector) |
None. |
Other known issues: http://doc.nexthink.com/doc/KnownIssues
4. Technical Support
For technical support, please post your queries at http://support.nexthink.com, or consult our documentation website http://doc.nexthink.com/.
5. Software Versions History
5.1. NEXThink Collector and Updater V4.0.078
5.1.1. Enhancements
5.1.1.1. Collector
Addition of log rotation when enabling a new option name for the logging: DRV_LOGSIZE (default value: 32 (Mb), range for value: 1 -> 512 (Mb))
- Microsoft Windows Services for UNIX 3.5 : We prevent the installation of the collector if 2 KB aren't installed (i.e., if the service is not patched)
- VPN/Juniper : We detect now the Juniper VPN and reorder PNP_TDI
5.1.1.2. Updater
Addition of log rotation when enabling a new option name for the logging: UPD_LOGSIZE (default value: 32 (Mb), range for value: 1 -> 512 (Mb))
- Addition of a new parameter in MSI GUI for enabling or not HTTPS
5.1.2. Fixed Issues
5.1.2.1. Collector
Antivirus (McAfee) : A wrong information was reported when using McAfee Agent
Antivirus (TrendMicro) : A wrong information was reported on fields "Last antivirus update", "Antivirus Definitions"
- Antivirus (Symantec) : A wrong information was reported when using Orchestration server ("Last antivirus update")
- Antivirus : We were still reporting data even when Sophos or SEP AV were uninstalled
- Installer : A problem occurred when a dns entry with more than 15 characters was specified
- Print : Document Path with more than 62 characters weren't reported
- Symantec End Point Protection 12 failed to install when Collector V3 or V4 was installed
5.2. NEXThink Collector V4.0.070 and Updater V4.0.065
5.2.1. Fixed Issues
- BSOD occurred when the Workstation service started with some delay. This problem occurred when data was sent the 2nd time (after 3 hours).
- Collector service was crashing if a smb/shared printer was reporting a job with empty data
- Under some circumstances, the printer/printing information wasn't completely accurate (#3562, #3591, #3595, #3619, #3620, #3625)
- The Collector-rundll32 was creating too many handles (#3516)
