Nagios Support Forum

i've finally found a bit of time to look into deploying NSClient better than it currently is.

we currently deploy the following method (via SCCM):
1st: msiexec /i nscp.msi /qn
2nd: %installdir%\nscp.exe settings --switch http://webserver/nsclient/nsclient.ini

This downloads the http nsclient.ini file into the %installdir%\cache\ folder.
nsclient does not know about the \cache\ location so i have to manually copy the ini file in the root of the installdir. this obviously doesn't keep the live config file up to date.

I've tried "NSCP-0.5.2.35-x64.msi" CONFIGURATION_TYPE="ini:C:\Program Files\NSClient++\cache\nsclient.ini", but fails to create the boot.ini as it appears to check if file exists, else failed install.
it also appears the CONFIGURATION_TYPE doesn't work with http so unable to use that for first stage install for it to get the webserver config. (CONFIGURATION_TYPE="http://webserver/nsclient/nsclient.ini")

I feel like i missing something obvious with getting this to work, but the NSClient docs are fairly weak and not found much info searching.
Any ideas?

*** As NSClient++ is not our product (we don't know the code or write it) you will get better NSClient++ support from the NSClient++ support forums specifically related to their functionality

I think you need to use these:
So:
According to this:

Using Silent install in 0.4.4 and 0.5.0

https://docs.nsclient.org/installing/

CONF_CAN_CHANGE forces the config to become writable (if you run silently the detection never happens so this flag is never updated)

Based on the information provided (and from NSClient++'s doc) your options are:

1. Construct the MSI command to use to do all the things you want in your final config, restart service
-- I don't think their intent is to let you specify where to copy the config from only that you can set where it pulls from
2. Silent install it only, replace the nsclient.ini file after via another method, restart the service
3. Possibly use the CONF_INCLUDES