New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion for Windows installer Configuration Screen #133
Comments
Also, it will be nice to have SSL setting in screen and also way to pass in command line, like we do it for token Thanks |
Good ideas guys. These would definitely make a good addiiton to the Windows installer. @varnar, I'm not sure what you mean by SSL settings? Which SSL settings? |
I mean pass in command line which version of SSL to use |
Thank you very much |
I think it might be easier to pass the settings in 2 pages instead of one. The problem we were having (why there's two bars on one line that makes it look kind of cluttered) is caused by the size of the window that you are allowed to use. If we split the two sections into two separate pages, one for Active settings and one for Passive settings we can not only fit more settings on them but we could easily make some more short descriptions. |
I think that will be better overall, it will make it clearer for sure. |
We are getting ready to release 1.8.0 so this will probably not be happening until the next version of NCPA. |
In the latest commits I have added more setup features/configuration in the windows installer, including setting up passive checks, listener and passive agent settings, etc. |
On this screen, it might be a little clearer if the Active and Passive headings had a little more description. Like:
Active Specifications (NCPA)
This setting is to allow remote machines to connect to it to perform active checks.
Passive Specifications (NRDP) Configure this machine to send passive check results to a Nagios server.
Also perhaps an extra line feed / horizontal line that seperates the two sections. To a newbie it looks like all settings may be required.
The text was updated successfully, but these errors were encountered: