I readed that post too (wasn’t mine), so I’ll wait for the v4 to come out.
As in other thread, I’d like to have the possibility to get an external NSC.ini if present in the install source dir.
In this way, without modifying your original msi package (less direct metodology), we could deploy our custom config and start the service automatically.
Also, another feature I’d like would be the possibility to reload the config automatically every x minutes (or, at least, some part of it). The feature could be very useful while deploying new commands: with GPO File preference I already update the config file on all my servers. Obviously, this function makes the previous one useless, but maybe is a bit more difficult to implement.
0.4.x has support for loading ini files from a remote server during start up.
Another option is the custom installers I build for sponsors normally contain 3 ini files.
1. being the normal which includes:
2. A company specific one for the company which includes a:
3. A user customization one for customer overrides.
I think maybe I should switch the regular installer to using a similar scheme some day?