Guide to installing on Windows via ZIP file (not MSI)?

[vpiccoli69]

Is there a guide to installing NSClient++ (any newer version) via the ZIP files as opposed to the MSI files? I'm upgrading many machines from various older version, but only two of the machines are unable to use the MSI installer. They get the dreaded "Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action NeedUninstall, entry: NeedUninstall, library: C:\Users\xxxxxxxx\AppData\Local\Temp\MSI8DCC.tmp=== Logging stopped:". You will find MANY "cures" for this issue with a Google search, but none of those cures have worked in this case.

We have tried more than 40 different methods of correcting this issue, but for some reason, none of the 64-bit MSI files will run on these 2 64-bit Windows 10 machines (that are completely up to date, update-wise).

After troubleshooting, I was able to run the old 64-bit MSI installer for the version that they are currently running to get things functioning again. FYI: these machines are running a very old version (0.3.8-x64) with a bunch of custom scripts and TCP Ports / modules. The only real reason for the upgrade is to use an acceptable level of TLS over those custom ports to secure the transmission through a firewall.

If there is a guide for how to manually install this from the ZIP file, I'd appreciate it. Thank you.

[mickem]

Hellow, First off the installer issue "should (TM)" have been fixed by https://github.com/mickem/nscp/releases/tag/0.9.2

That said if you copy the zip somewhere all you need to is add a service entry (and firewall) service entry can be added with the clie:

$ nscp service --help
Allowed options (service):

Common options:
  --settings arg         Override (temporarily) settings subsystem to use
  --debug                Set log level to debug (and show debug information)
  --log arg              The log level to use
  --define arg           Defines to use to override settings. Syntax is
                         PATH:KEY=VALUE

Common options:
  --help                 Show the help message for a given command
  --no-stderr            Do not report errors on stderr
  --version              Show version information

Service Options:
  --install              Install service
  --uninstall            Uninstall service
  --start                Start service
  --stop                 Stop service
  --restart              Stop than start service
  --info                 Show information about service
  --run                  Run as a service
  --name arg             Name of service
  --description arg      Description of service

So in essence: nscp service --install

For the firewall exception there is no automated way to add that but Windows has UI:s for adding firewall exception and if you google you can likely find a one-liner powershell command to do that.