06
апр
This article describes how to monitor Windows machines “private” services such as CPU load, Disk usage, Memory usage,Services, etc. For this, we required to install an NSClient++ addon on the Windows machine. The addon acts a proxy between the Windows machine and Nagios and monitors actual services by communicating with the check_nt plugin. The check_nt plugin already installed on the Nagios Monitoring Server, if you followed our Nagios installation guide.
We assume that you’ve already installed and configured Nagios server according to our following guides.
Mar 04, 2010 In order to monitor a Windows desktop or server with Nagios, you must first install on agent on the target machine. This guide takes you through the steps of installing and configuring the Windows agent (NSClient) in preparation for monitoring the machine with Nagios XI or Nagios Core. Install nagios client on a remote windows server. The script will install Nagios client to a remote server. It copies the MSI and the INI file to the remote computer's C drive and then executes it. Once the execution is completed, it will copy the 'nsclient.ini' file to the installed folder.Pre-Requisites:- The servers are to be.
To monitor Windows Machines you will need to follow several steps and they are:
- Install NSClient++ addon on the Windows Machine.
- Configure Nagios Server for monitoring Windows Machine.
- Add new host and service definitions for Windows machine monitoring.
- Restart the Nagios Service.
To make this guide simple and easier, a few of configuration already done for you in the Nagios installation.
- A check_nt command definition already added to the command.cfg file. This definition command is used by check_nt plugin to monitor Windows services.
- A windows-server host template already created in the templates.cfg file. This template allows you to add new Windows host definitions.
The above two files “command.cfg” and “templates.cfg” files can be found at /usr/local/nagios/etc/objects/ directory. You can modify and add your own definitions that suits your requirement. But, I’d recommend you to follow the instructions described in this article and you will be successfully monitoring your windows host in less than 20 minutes.
Step 1: Installing NSClient++ Agent on Windows Machine
Please use the below instructions to install NSClient++ Agent on the Remote Windows Host. First download the latest stable version NSClient++ 0.3.1 addon source files, which can be found at below link.
Once you’ve downloaded latest stable version, unzip the NSClient++ files into a new C:NSClient++ directory.
Now open a MS-DOS command prompt from the Start Screen –> Run –> type ‘cmd‘ and press enter and change to the C:NSClient++ directory.
Next, register the NSClient++ service on the system with the following command.
Finally, install the NSClient++ systray with the following command.
Open the Windows Services Manager and right click on NSClient go to Properties and then ‘Log On‘ tab and click the check box that says “Allow service to interact with the desktop“. If it isn’t already allowed, please check the box to allow it to.
Open NSC.INI file located at C:NSClient++ directory and uncomment all the modules defined in the “modules” section, except for CheckWMI.dll and RemoteConfiguration.dll.
Uncomment the “allowed_hosts” in the “Settings” section and define the IP address of your Nagios Monitoring Server or leave it blank to allow any hosts to connect.
Uncomment the “port” in the “NSClient” section and set to default port ‘12489‘. Make sure to open ‘12489‘ port on Windows Firewall.
Finally start the NSClient++ service with the following command.
If your properly installed and configured, you should see a new icon in the system tray in yellow circle with a black ‘M‘ inside.
Step 2: Configuring Nagios Server and Add Windows Hosts
Now Login into Nagios Server and add some object definitions in Nagios configuration files to monitor new Windows machine. Open windows.cfg file for editing with Vi editor.
A sample Windows host definition already defined for the Windows machine, you can simply change the host definition like host_name, alias, and address fields to appropriate values of your Windows machine.
Following services are already added and enabled in windows.cfg file. If you wish to add some more other service definitions that needs to be monitored, you can simple add those definitions to same configuration file. Make sure to change the host_name for these all services with host_name defined in the above step.
Lastly, uncomment the windows.cfg file in /usr/local/nagios/etc/nagios.cfg.
Finally, verify the Nagios configuration files for any erros.
If the verification process throws any error messages, fix those errors until the verification process completes without any error messages. Once’ you fix those errors, restart the Nagios service.
That’s it. Now go to Nagios Monitoring Web interface at “http://Your-server-IP-address/nagios” or “http://FQDN/nagios” and Provide the username “nagiosadmin” and password. Check that the Remote Windows Host was added and is being monitored.
Nagios Monitor Windows Host
That’s it! for now, in my up-coming article I will show you how to add Printer and Switches to Nagios Monitoring Server. If you’re having any difficulties while adding Windows host to Nagios. Please do comment your queries via comment section, till then stay tuned to Tecmint.com for more such kind of valuable articles.
This is a grooving process before it was all manual but slowly we are getting a more “automated” installation process so hopefully this will keep improving in the future as well and some of the steps might go away.
High-performance Java Persistence Pdf Download - DOWNLOAD. Download High-Performance Java Persistence torrent or any other torrent has 49395 resourcessearch torrent from torrent sites- TorrentAnt.com. Persistence-the ability of data to outlive an instance of a program-is central to modern applications. Hibernate, the most popular Java. Hibernate, the most popular provider of the Java Persistence standard, offers automatic and transparent object/relational mapping, making it a snap to work with SQL databases in Java applications. Java Persistence with Hibernate, Second Edition explores Hibernate by developing an application that ties together hundreds of individual examples. Spring persistence with hibernate pdf. Note: If you're looking for a free download links of Java Persistence with Hibernate Pdf, epub, docx and torrent then this site is not for you. Ebookphp.com only do ebook promotions online and we does not distribute any free download of ebook on this site. Tags: EJB 3.0 Hibernate Hibernate 3.2 Hibernate 5 Java EE Java EE 7 Java EE 8 Java Persistence Java Persistence 1.0 Java Persistence 2 Java Persistence 2.1 Java Persistence with Hibernate Java Persistence with Hibernate 2nd Edition Java Persistence with Hibernate Second Edition JavaServer Faces JBoss JBoss Seam JSF JSR 220 JSR 299 JSR 338 Web.
Installation (Simple)¶
NSClient++ comes with an interactive installer (MSI) which is the preferred method of installation.There is also a command line option for registering (and de-registering) the service but as the Installer works pretty well it is the preferred way.
More detailed information on how to do silent installs and automated installs in large environments can be found below.For most people installing NSClient++ is simply running the MSI entering some options and clicking next.BUT this is only where the fun begins. After installing NSClient++ you need to configure it.
Configuration¶
Before you start NSClient++ you need to configure it by editing the configuration. The configuration is usually in a file called nsclient.ini.But the configuration can be stored elsewhere as will (for instance registry is a great place on Windows).
To check where the configuration is stored you can trun the following command:
Now this configuration can include other configuration files so you need to check that as well. So it is possible to include the registry from the ini file and vice versa.For details on the configuration options check the the reference documentation
Windows Firewall¶
- Windows firewall exception for NRPE and check_nt is installed (optionally) by the installer. If you have another firewall then the built-in one you might have to manually add exceptions to all incoming traffic if you which to use check_nrpe and/or check_nt.
- External Firewall (optional)
Firewall configuration should be pretty straight forward:
- If you use NRPEServer (check_nrpe, NRPEListener) you need the NRPE port open (usually 5666) from the Nagios server towards the client.
- If you use the NSClientServer (check_nt, NSClientListener) you need the (modified) NSClient port open (usually 12489) from the Nagios server towards the client.
- If you use the NSCA Module (passive checks) you need the NSCA port open from the client towards the Nagios server. client:* -> Nagios:5667
- Also be aware that ports are configurable so if you override the defaults you obviously need to update the firewall rules accordingly.
- There a multitude of other protocol which you can also use with NSClient++ (including, NRPE, NSCA, Syslog, SMTP, etc etc) so please review what your firewall setup in conjunction with you NSClient++ design.
| Protocol | Source | Source port | Destination | Destination port | Comment |
|---|---|---|---|---|---|
| NRPE | Nagios | client | 5666 | The nagios server initiates a call to the client on port 5666 | |
| NSClient | Nagios | client | 12489 | The nagios server initiates a call to the client on port 12489 | |
| NSCA | client | Nagios | 5667 | The client initiates a call to the Nagios server on port 5667 | |
| NRPE-proxy | client | remote-client | 5666 | The client initiates a call to the remote client on port 5666 |
- Nagios is the IP/host of the main monitoring server
- client is the Windows computer where you have installed NSClient++
- remote-client is the “other” client you want to check from NSClient++ (using NSClient++ as a proxy)
All these ports can be changed so be sure to check your nsclient.ini for your ports.
Automated installation¶
The NSClient++ installer for windows is a standard MSI installer which means it can be installed using pretty much all deployment techniques available on the windows platform.This means that there is no built-in deploy and configuration mechanism in NSClient++ instead it fully relies on standard tools provided for the Windows platform.MSI files can be tweaked in several ways.
Configuration options¶
There are several options for deploying configuration and copying text-file is probably the worst of them.You can use group policies to push the configuration files but there are several other ways to do the same.
MSI Options¶
The MSI file can be customized during the installer. The following keys are available:
| Keyword | Description |
|---|---|
| INSTALLLOCATION | Folder where NSClient++ is installed. |
| CONF_CAN_CHANGE | Has to be set for all configuration changes to be applied. |
| ADD_DEFAULTS | Add default values to the configuration file. |
| ALLOWED_HOSTS | Set allowed hosts value |
| CONFIGURATION_TYPE | Configuration context to use |
| CONF_CHECKS | Enable default check plugins |
| CONF_NRPE | Enable NRPE server |
| CONF_NSCA | Enable NSCA Collection /OU probably need scheduler as well) |
| CONF_NSCLIENT | Enable NSClient Server (check_nt) |
| CONF_SCHEDULER | Enable Scheduler (required by NSCA) |
| CONF_WEB | Enabled WEB Server |
| NRPEMODE | NRPE Mode (LEGACY = default old insecure SSL, SAFE = new secure SSL) |
| NSCLIENT_PWD | Password to use for check_nt (and web server) |
| CONF_INCLUDES | Additional files to include in the config syntax: ; |
| OP5_SERVER | OP5 Server if you want to automatically submit passive checks via Op5 northbound API. |
| OP5_USER | The username to login with on the OP5_SERVER |
| OP5_PASSWORD | The password to login with on the OP5_SERVER |
| OP5_HOSTGROUPS | Additional hostgroups to add to the host. |
| OP5_CONTACTGROUP | Additional contactgroups to add to the host. |
Features¶
NSClient++ consists of the following features most which can be disable when doing silent installs.
| Feature Name | Title | Description |
|---|---|---|
| CheckPlugins | Check Plugins | Various plugins to check your system. (Includes all check plugins) |
| Documentation | Documentation (pdf) | Documentation for NSClient++ and how to use it from Nagios |
| DotNetPluginSupport | .net plugin support | Support for loading modules written in .dot net (Requires installing .net framework) |
| ExtraClientPlugin | Various client plugins | Plugins to connect to various systems such as syslog, graphite and smtp |
| FirewallConfig | Firewall Exception | A firewall exception to allow NSClient++ to open ports |
| LuaScript | Lua Scripting | Allows running INTERNAL scripts written in Lua |
| NRPEPlugins | NRPE Support | NRPE Server Plugin. Support for the more versatile NRPE protocol (check_nrpe) |
| NSCAPlugin | NSCA plugin | Plugin to submit passive results to an NSCA server |
| NSCPlugins | check_nt support | NSClient Server Plugin. Support for the old NSClient protocol (check_nt) |
| PythonScript | Python Scripting | Allows running INTERNAL scripts written in Python |
| SampleConfig | Sample config | Sample config file (with all options) |
| SampleScripts | Scripts | Scripts for checking and testing various aspects of your computer and NSClient++ |
| Shortcuts | Shortcuts | Main Service shortcuts |
| WEBPlugins | WEB Server | NSClient WEB Server. Use this to administrate or check NSClient via a browser or REST API |
| OP5Montoring | OP5 Monitoring | Scripts/config for the op5 monitoring system. |
Silent install¶
Now we can put all this together using the normal silent installer which is again part of the standard windows install toolkit.So if you already have a framework for managing installs use that instead of this command line.The gist of it is: msiexec /quiet /i <MSI FILE> PROPERTY=PropertyValue ..
For instance Installing (with log) NSClient++ into c:foobar using registry as configuration and not installing the Python script binaries.
Using Silent install in 0.4.4 and 0.5.0¶
You need to add two options in these version if you plan to update the configuration in a silent install:
CONF_CAN_CHANGE forces the config to become writable (if you run silently the detection never happens so this flag is never updated).MONITORING_TOOL If no monitoring tool is specified it will default to “default” and overwrite various options given on the command line.
Silent op5 install¶
To enable active checks via NRPE from OP5 you can set the MONITORING_TOOL option to OP5.
Silent op5 install (Northbound)¶
To enable passive reports via OP5s Northbound API you can set the OP5_SERVER, OP5_USER and OP5_PASSWORD options.In this case setting MONITORING_TOOL is done automatically when ever OP5_SERVER is detected.
Multiple NSClient++¶
As NSClient++ uninstalls it self if you install there are two options for running multiple NSClient++ on a machine.
- You can add multiple services for the same installation
- You can install NSClient++_Secondary binary to get two instance on the same machine
- You can manually install NSClient++ (allows any number of installs)
To add multiple service you need to first create the services: nscp service --install --name nscp2
And then edit the start command so you can override the configuration.The key to look for in the registry is HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesnscp2 and there you can modify the ImagePath:'C:Program FilesNSClient++nscp.exe' service --run --name nscp --settings ini://${shared-path}/nsclient-2.ini
Popular Posts
This article describes how to monitor Windows machines “private” services such as CPU load, Disk usage, Memory usage,Services, etc. For this, we required to install an NSClient++ addon on the Windows machine. The addon acts a proxy between the Windows machine and Nagios and monitors actual services by communicating with the check_nt plugin. The check_nt plugin already installed on the Nagios Monitoring Server, if you followed our Nagios installation guide.
We assume that you’ve already installed and configured Nagios server according to our following guides.
Mar 04, 2010 In order to monitor a Windows desktop or server with Nagios, you must first install on agent on the target machine. This guide takes you through the steps of installing and configuring the Windows agent (NSClient) in preparation for monitoring the machine with Nagios XI or Nagios Core. Install nagios client on a remote windows server. The script will install Nagios client to a remote server. It copies the MSI and the INI file to the remote computer\'s C drive and then executes it. Once the execution is completed, it will copy the \'nsclient.ini\' file to the installed folder.Pre-Requisites:- The servers are to be.
To monitor Windows Machines you will need to follow several steps and they are:
- Install NSClient++ addon on the Windows Machine.
- Configure Nagios Server for monitoring Windows Machine.
- Add new host and service definitions for Windows machine monitoring.
- Restart the Nagios Service.
To make this guide simple and easier, a few of configuration already done for you in the Nagios installation.
- A check_nt command definition already added to the command.cfg file. This definition command is used by check_nt plugin to monitor Windows services.
- A windows-server host template already created in the templates.cfg file. This template allows you to add new Windows host definitions.
The above two files “command.cfg” and “templates.cfg” files can be found at /usr/local/nagios/etc/objects/ directory. You can modify and add your own definitions that suits your requirement. But, I’d recommend you to follow the instructions described in this article and you will be successfully monitoring your windows host in less than 20 minutes.
Step 1: Installing NSClient++ Agent on Windows Machine
Please use the below instructions to install NSClient++ Agent on the Remote Windows Host. First download the latest stable version NSClient++ 0.3.1 addon source files, which can be found at below link.
Once you’ve downloaded latest stable version, unzip the NSClient++ files into a new C:NSClient++ directory.
Now open a MS-DOS command prompt from the Start Screen –> Run –> type ‘cmd‘ and press enter and change to the C:NSClient++ directory.
Next, register the NSClient++ service on the system with the following command.
Finally, install the NSClient++ systray with the following command.
Open the Windows Services Manager and right click on NSClient go to Properties and then ‘Log On‘ tab and click the check box that says “Allow service to interact with the desktop“. If it isn’t already allowed, please check the box to allow it to.
Open NSC.INI file located at C:NSClient++ directory and uncomment all the modules defined in the “modules” section, except for CheckWMI.dll and RemoteConfiguration.dll.
Uncomment the “allowed_hosts” in the “Settings” section and define the IP address of your Nagios Monitoring Server or leave it blank to allow any hosts to connect.
Uncomment the “port” in the “NSClient” section and set to default port ‘12489‘. Make sure to open ‘12489‘ port on Windows Firewall.
Finally start the NSClient++ service with the following command.
If your properly installed and configured, you should see a new icon in the system tray in yellow circle with a black ‘M‘ inside.
Step 2: Configuring Nagios Server and Add Windows Hosts
Now Login into Nagios Server and add some object definitions in Nagios configuration files to monitor new Windows machine. Open windows.cfg file for editing with Vi editor.
A sample Windows host definition already defined for the Windows machine, you can simply change the host definition like host_name, alias, and address fields to appropriate values of your Windows machine.
Following services are already added and enabled in windows.cfg file. If you wish to add some more other service definitions that needs to be monitored, you can simple add those definitions to same configuration file. Make sure to change the host_name for these all services with host_name defined in the above step.
Lastly, uncomment the windows.cfg file in /usr/local/nagios/etc/nagios.cfg.
Finally, verify the Nagios configuration files for any erros.
If the verification process throws any error messages, fix those errors until the verification process completes without any error messages. Once’ you fix those errors, restart the Nagios service.
That’s it. Now go to Nagios Monitoring Web interface at “http://Your-server-IP-address/nagios” or “http://FQDN/nagios” and Provide the username “nagiosadmin” and password. Check that the Remote Windows Host was added and is being monitored.
Nagios Monitor Windows Host
That’s it! for now, in my up-coming article I will show you how to add Printer and Switches to Nagios Monitoring Server. If you’re having any difficulties while adding Windows host to Nagios. Please do comment your queries via comment section, till then stay tuned to Tecmint.com for more such kind of valuable articles.
This is a grooving process before it was all manual but slowly we are getting a more “automated” installation process so hopefully this will keep improving in the future as well and some of the steps might go away.
High-performance Java Persistence Pdf Download - DOWNLOAD. Download High-Performance Java Persistence torrent or any other torrent has 49395 resourcessearch torrent from torrent sites- TorrentAnt.com. Persistence-the ability of data to outlive an instance of a program-is central to modern applications. Hibernate, the most popular Java. Hibernate, the most popular provider of the Java Persistence standard, offers automatic and transparent object/relational mapping, making it a snap to work with SQL databases in Java applications. Java Persistence with Hibernate, Second Edition explores Hibernate by developing an application that ties together hundreds of individual examples. Spring persistence with hibernate pdf. Note: If you\'re looking for a free download links of Java Persistence with Hibernate Pdf, epub, docx and torrent then this site is not for you. Ebookphp.com only do ebook promotions online and we does not distribute any free download of ebook on this site. Tags: EJB 3.0 Hibernate Hibernate 3.2 Hibernate 5 Java EE Java EE 7 Java EE 8 Java Persistence Java Persistence 1.0 Java Persistence 2 Java Persistence 2.1 Java Persistence with Hibernate Java Persistence with Hibernate 2nd Edition Java Persistence with Hibernate Second Edition JavaServer Faces JBoss JBoss Seam JSF JSR 220 JSR 299 JSR 338 Web.
Installation (Simple)¶
NSClient++ comes with an interactive installer (MSI) which is the preferred method of installation.There is also a command line option for registering (and de-registering) the service but as the Installer works pretty well it is the preferred way.
More detailed information on how to do silent installs and automated installs in large environments can be found below.For most people installing NSClient++ is simply running the MSI entering some options and clicking next.BUT this is only where the fun begins. After installing NSClient++ you need to configure it.
Configuration¶
Before you start NSClient++ you need to configure it by editing the configuration. The configuration is usually in a file called nsclient.ini.But the configuration can be stored elsewhere as will (for instance registry is a great place on Windows).
To check where the configuration is stored you can trun the following command:
Now this configuration can include other configuration files so you need to check that as well. So it is possible to include the registry from the ini file and vice versa.For details on the configuration options check the the reference documentation
Windows Firewall¶
- Windows firewall exception for NRPE and check_nt is installed (optionally) by the installer. If you have another firewall then the built-in one you might have to manually add exceptions to all incoming traffic if you which to use check_nrpe and/or check_nt.
- External Firewall (optional)
Firewall configuration should be pretty straight forward:
- If you use NRPEServer (check_nrpe, NRPEListener) you need the NRPE port open (usually 5666) from the Nagios server towards the client.
- If you use the NSClientServer (check_nt, NSClientListener) you need the (modified) NSClient port open (usually 12489) from the Nagios server towards the client.
- If you use the NSCA Module (passive checks) you need the NSCA port open from the client towards the Nagios server. client:* -> Nagios:5667
- Also be aware that ports are configurable so if you override the defaults you obviously need to update the firewall rules accordingly.
- There a multitude of other protocol which you can also use with NSClient++ (including, NRPE, NSCA, Syslog, SMTP, etc etc) so please review what your firewall setup in conjunction with you NSClient++ design.
Protocol Source Source port Destination Destination port Comment NRPE Nagios client 5666 The nagios server initiates a call to the client on port 5666 NSClient Nagios client 12489 The nagios server initiates a call to the client on port 12489 NSCA client Nagios 5667 The client initiates a call to the Nagios server on port 5667 NRPE-proxy client remote-client 5666 The client initiates a call to the remote client on port 5666 - Nagios is the IP/host of the main monitoring server
- client is the Windows computer where you have installed NSClient++
- remote-client is the “other” client you want to check from NSClient++ (using NSClient++ as a proxy)
All these ports can be changed so be sure to check your nsclient.ini for your ports.
Automated installation¶
The NSClient++ installer for windows is a standard MSI installer which means it can be installed using pretty much all deployment techniques available on the windows platform.This means that there is no built-in deploy and configuration mechanism in NSClient++ instead it fully relies on standard tools provided for the Windows platform.MSI files can be tweaked in several ways.
Configuration options¶
There are several options for deploying configuration and copying text-file is probably the worst of them.You can use group policies to push the configuration files but there are several other ways to do the same.
MSI Options¶
The MSI file can be customized during the installer. The following keys are available:
Keyword Description INSTALLLOCATION Folder where NSClient++ is installed. CONF_CAN_CHANGE Has to be set for all configuration changes to be applied. ADD_DEFAULTS Add default values to the configuration file. ALLOWED_HOSTS Set allowed hosts value CONFIGURATION_TYPE Configuration context to use CONF_CHECKS Enable default check plugins CONF_NRPE Enable NRPE server CONF_NSCA Enable NSCA Collection /OU probably need scheduler as well) CONF_NSCLIENT Enable NSClient Server (check_nt) CONF_SCHEDULER Enable Scheduler (required by NSCA) CONF_WEB Enabled WEB Server NRPEMODE NRPE Mode (LEGACY = default old insecure SSL, SAFE = new secure SSL) NSCLIENT_PWD Password to use for check_nt (and web server) CONF_INCLUDES Additional files to include in the config syntax: ; For instance CONF_INCLUDES=op5;op5.ini;local;local.ini OP5_SERVER OP5 Server if you want to automatically submit passive checks via Op5 northbound API. OP5_USER The username to login with on the OP5_SERVER OP5_PASSWORD The password to login with on the OP5_SERVER OP5_HOSTGROUPS Additional hostgroups to add to the host. OP5_CONTACTGROUP Additional contactgroups to add to the host. Features¶
NSClient++ consists of the following features most which can be disable when doing silent installs.
Feature Name Title Description CheckPlugins Check Plugins Various plugins to check your system. (Includes all check plugins) Documentation Documentation (pdf) Documentation for NSClient++ and how to use it from Nagios DotNetPluginSupport .net plugin support Support for loading modules written in .dot net (Requires installing .net framework) ExtraClientPlugin Various client plugins Plugins to connect to various systems such as syslog, graphite and smtp FirewallConfig Firewall Exception A firewall exception to allow NSClient++ to open ports LuaScript Lua Scripting Allows running INTERNAL scripts written in Lua NRPEPlugins NRPE Support NRPE Server Plugin. Support for the more versatile NRPE protocol (check_nrpe) NSCAPlugin NSCA plugin Plugin to submit passive results to an NSCA server NSCPlugins check_nt support NSClient Server Plugin. Support for the old NSClient protocol (check_nt) PythonScript Python Scripting Allows running INTERNAL scripts written in Python SampleConfig Sample config Sample config file (with all options) SampleScripts Scripts Scripts for checking and testing various aspects of your computer and NSClient++ Shortcuts Shortcuts Main Service shortcuts WEBPlugins WEB Server NSClient WEB Server. Use this to administrate or check NSClient via a browser or REST API OP5Montoring OP5 Monitoring Scripts/config for the op5 monitoring system. Silent install¶
Now we can put all this together using the normal silent installer which is again part of the standard windows install toolkit.So if you already have a framework for managing installs use that instead of this command line.The gist of it is:
msiexec /quiet /i <MSI FILE> PROPERTY=PropertyValue ..For instance Installing (with log) NSClient++ into c:foobar using registry as configuration and not installing the Python script binaries.
Using Silent install in 0.4.4 and 0.5.0¶
You need to add two options in these version if you plan to update the configuration in a silent install:
CONF_CAN_CHANGE forces the config to become writable (if you run silently the detection never happens so this flag is never updated).MONITORING_TOOL If no monitoring tool is specified it will default to “default” and overwrite various options given on the command line.
Silent op5 install¶
To enable active checks via NRPE from OP5 you can set the
MONITORING_TOOLoption toOP5.Silent op5 install (Northbound)¶
To enable passive reports via OP5s Northbound API you can set the
OP5_SERVER,OP5_USERandOP5_PASSWORDoptions.In this case settingMONITORING_TOOLis done automatically when everOP5_SERVERis detected.Multiple NSClient++¶
As NSClient++ uninstalls it self if you install there are two options for running multiple NSClient++ on a machine.
- You can add multiple services for the same installation
- You can install NSClient++_Secondary binary to get two instance on the same machine
- You can manually install NSClient++ (allows any number of installs)
To add multiple service you need to first create the services:
nscp service --install --name nscp2And then edit the start command so you can override the configuration.The key to look for in the registry is
...'>Install Nagios Agent On Windows(06.04.2020)HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesnscp2and there you can modify the ImagePath:\'C:Program FilesNSClient++nscp.exe\' service --run --name nscp --settings ini://${shared-path}/nsclient-2.iniThis article describes how to monitor Windows machines “private” services such as CPU load, Disk usage, Memory usage,Services, etc. For this, we required to install an NSClient++ addon on the Windows machine. The addon acts a proxy between the Windows machine and Nagios and monitors actual services by communicating with the check_nt plugin. The check_nt plugin already installed on the Nagios Monitoring Server, if you followed our Nagios installation guide.
We assume that you’ve already installed and configured Nagios server according to our following guides.
Mar 04, 2010 In order to monitor a Windows desktop or server with Nagios, you must first install on agent on the target machine. This guide takes you through the steps of installing and configuring the Windows agent (NSClient) in preparation for monitoring the machine with Nagios XI or Nagios Core. Install nagios client on a remote windows server. The script will install Nagios client to a remote server. It copies the MSI and the INI file to the remote computer\'s C drive and then executes it. Once the execution is completed, it will copy the \'nsclient.ini\' file to the installed folder.Pre-Requisites:- The servers are to be.
To monitor Windows Machines you will need to follow several steps and they are:
- Install NSClient++ addon on the Windows Machine.
- Configure Nagios Server for monitoring Windows Machine.
- Add new host and service definitions for Windows machine monitoring.
- Restart the Nagios Service.
To make this guide simple and easier, a few of configuration already done for you in the Nagios installation.
- A check_nt command definition already added to the command.cfg file. This definition command is used by check_nt plugin to monitor Windows services.
- A windows-server host template already created in the templates.cfg file. This template allows you to add new Windows host definitions.
The above two files “command.cfg” and “templates.cfg” files can be found at /usr/local/nagios/etc/objects/ directory. You can modify and add your own definitions that suits your requirement. But, I’d recommend you to follow the instructions described in this article and you will be successfully monitoring your windows host in less than 20 minutes.
Step 1: Installing NSClient++ Agent on Windows Machine
Please use the below instructions to install NSClient++ Agent on the Remote Windows Host. First download the latest stable version NSClient++ 0.3.1 addon source files, which can be found at below link.
Once you’ve downloaded latest stable version, unzip the NSClient++ files into a new C:NSClient++ directory.
Now open a MS-DOS command prompt from the Start Screen –> Run –> type ‘cmd‘ and press enter and change to the C:NSClient++ directory.
Next, register the NSClient++ service on the system with the following command.
Finally, install the NSClient++ systray with the following command.
Open the Windows Services Manager and right click on NSClient go to Properties and then ‘Log On‘ tab and click the check box that says “Allow service to interact with the desktop“. If it isn’t already allowed, please check the box to allow it to.
Open NSC.INI file located at C:NSClient++ directory and uncomment all the modules defined in the “modules” section, except for CheckWMI.dll and RemoteConfiguration.dll.
Uncomment the “allowed_hosts” in the “Settings” section and define the IP address of your Nagios Monitoring Server or leave it blank to allow any hosts to connect.
Uncomment the “port” in the “NSClient” section and set to default port ‘12489‘. Make sure to open ‘12489‘ port on Windows Firewall.
Finally start the NSClient++ service with the following command.
If your properly installed and configured, you should see a new icon in the system tray in yellow circle with a black ‘M‘ inside.
Step 2: Configuring Nagios Server and Add Windows Hosts
Now Login into Nagios Server and add some object definitions in Nagios configuration files to monitor new Windows machine. Open windows.cfg file for editing with Vi editor.
A sample Windows host definition already defined for the Windows machine, you can simply change the host definition like host_name, alias, and address fields to appropriate values of your Windows machine.
Following services are already added and enabled in windows.cfg file. If you wish to add some more other service definitions that needs to be monitored, you can simple add those definitions to same configuration file. Make sure to change the host_name for these all services with host_name defined in the above step.
Lastly, uncomment the windows.cfg file in /usr/local/nagios/etc/nagios.cfg.
Finally, verify the Nagios configuration files for any erros.
If the verification process throws any error messages, fix those errors until the verification process completes without any error messages. Once’ you fix those errors, restart the Nagios service.
That’s it. Now go to Nagios Monitoring Web interface at “http://Your-server-IP-address/nagios” or “http://FQDN/nagios” and Provide the username “nagiosadmin” and password. Check that the Remote Windows Host was added and is being monitored.
Nagios Monitor Windows Host
That’s it! for now, in my up-coming article I will show you how to add Printer and Switches to Nagios Monitoring Server. If you’re having any difficulties while adding Windows host to Nagios. Please do comment your queries via comment section, till then stay tuned to Tecmint.com for more such kind of valuable articles.
This is a grooving process before it was all manual but slowly we are getting a more “automated” installation process so hopefully this will keep improving in the future as well and some of the steps might go away.
High-performance Java Persistence Pdf Download - DOWNLOAD. Download High-Performance Java Persistence torrent or any other torrent has 49395 resourcessearch torrent from torrent sites- TorrentAnt.com. Persistence-the ability of data to outlive an instance of a program-is central to modern applications. Hibernate, the most popular Java. Hibernate, the most popular provider of the Java Persistence standard, offers automatic and transparent object/relational mapping, making it a snap to work with SQL databases in Java applications. Java Persistence with Hibernate, Second Edition explores Hibernate by developing an application that ties together hundreds of individual examples. Spring persistence with hibernate pdf. Note: If you\'re looking for a free download links of Java Persistence with Hibernate Pdf, epub, docx and torrent then this site is not for you. Ebookphp.com only do ebook promotions online and we does not distribute any free download of ebook on this site. Tags: EJB 3.0 Hibernate Hibernate 3.2 Hibernate 5 Java EE Java EE 7 Java EE 8 Java Persistence Java Persistence 1.0 Java Persistence 2 Java Persistence 2.1 Java Persistence with Hibernate Java Persistence with Hibernate 2nd Edition Java Persistence with Hibernate Second Edition JavaServer Faces JBoss JBoss Seam JSF JSR 220 JSR 299 JSR 338 Web.
Installation (Simple)¶
NSClient++ comes with an interactive installer (MSI) which is the preferred method of installation.There is also a command line option for registering (and de-registering) the service but as the Installer works pretty well it is the preferred way.
More detailed information on how to do silent installs and automated installs in large environments can be found below.For most people installing NSClient++ is simply running the MSI entering some options and clicking next.BUT this is only where the fun begins. After installing NSClient++ you need to configure it.
Configuration¶
Before you start NSClient++ you need to configure it by editing the configuration. The configuration is usually in a file called nsclient.ini.But the configuration can be stored elsewhere as will (for instance registry is a great place on Windows).
To check where the configuration is stored you can trun the following command:
Now this configuration can include other configuration files so you need to check that as well. So it is possible to include the registry from the ini file and vice versa.For details on the configuration options check the the reference documentation
Windows Firewall¶
- Windows firewall exception for NRPE and check_nt is installed (optionally) by the installer. If you have another firewall then the built-in one you might have to manually add exceptions to all incoming traffic if you which to use check_nrpe and/or check_nt.
- External Firewall (optional)
Firewall configuration should be pretty straight forward:
- If you use NRPEServer (check_nrpe, NRPEListener) you need the NRPE port open (usually 5666) from the Nagios server towards the client.
- If you use the NSClientServer (check_nt, NSClientListener) you need the (modified) NSClient port open (usually 12489) from the Nagios server towards the client.
- If you use the NSCA Module (passive checks) you need the NSCA port open from the client towards the Nagios server. client:* -> Nagios:5667
- Also be aware that ports are configurable so if you override the defaults you obviously need to update the firewall rules accordingly.
- There a multitude of other protocol which you can also use with NSClient++ (including, NRPE, NSCA, Syslog, SMTP, etc etc) so please review what your firewall setup in conjunction with you NSClient++ design.
Protocol Source Source port Destination Destination port Comment NRPE Nagios client 5666 The nagios server initiates a call to the client on port 5666 NSClient Nagios client 12489 The nagios server initiates a call to the client on port 12489 NSCA client Nagios 5667 The client initiates a call to the Nagios server on port 5667 NRPE-proxy client remote-client 5666 The client initiates a call to the remote client on port 5666 - Nagios is the IP/host of the main monitoring server
- client is the Windows computer where you have installed NSClient++
- remote-client is the “other” client you want to check from NSClient++ (using NSClient++ as a proxy)
All these ports can be changed so be sure to check your nsclient.ini for your ports.
Automated installation¶
The NSClient++ installer for windows is a standard MSI installer which means it can be installed using pretty much all deployment techniques available on the windows platform.This means that there is no built-in deploy and configuration mechanism in NSClient++ instead it fully relies on standard tools provided for the Windows platform.MSI files can be tweaked in several ways.
Configuration options¶
There are several options for deploying configuration and copying text-file is probably the worst of them.You can use group policies to push the configuration files but there are several other ways to do the same.
MSI Options¶
The MSI file can be customized during the installer. The following keys are available:
Keyword Description INSTALLLOCATION Folder where NSClient++ is installed. CONF_CAN_CHANGE Has to be set for all configuration changes to be applied. ADD_DEFAULTS Add default values to the configuration file. ALLOWED_HOSTS Set allowed hosts value CONFIGURATION_TYPE Configuration context to use CONF_CHECKS Enable default check plugins CONF_NRPE Enable NRPE server CONF_NSCA Enable NSCA Collection /OU probably need scheduler as well) CONF_NSCLIENT Enable NSClient Server (check_nt) CONF_SCHEDULER Enable Scheduler (required by NSCA) CONF_WEB Enabled WEB Server NRPEMODE NRPE Mode (LEGACY = default old insecure SSL, SAFE = new secure SSL) NSCLIENT_PWD Password to use for check_nt (and web server) CONF_INCLUDES Additional files to include in the config syntax: ; For instance CONF_INCLUDES=op5;op5.ini;local;local.ini OP5_SERVER OP5 Server if you want to automatically submit passive checks via Op5 northbound API. OP5_USER The username to login with on the OP5_SERVER OP5_PASSWORD The password to login with on the OP5_SERVER OP5_HOSTGROUPS Additional hostgroups to add to the host. OP5_CONTACTGROUP Additional contactgroups to add to the host. Features¶
NSClient++ consists of the following features most which can be disable when doing silent installs.
Feature Name Title Description CheckPlugins Check Plugins Various plugins to check your system. (Includes all check plugins) Documentation Documentation (pdf) Documentation for NSClient++ and how to use it from Nagios DotNetPluginSupport .net plugin support Support for loading modules written in .dot net (Requires installing .net framework) ExtraClientPlugin Various client plugins Plugins to connect to various systems such as syslog, graphite and smtp FirewallConfig Firewall Exception A firewall exception to allow NSClient++ to open ports LuaScript Lua Scripting Allows running INTERNAL scripts written in Lua NRPEPlugins NRPE Support NRPE Server Plugin. Support for the more versatile NRPE protocol (check_nrpe) NSCAPlugin NSCA plugin Plugin to submit passive results to an NSCA server NSCPlugins check_nt support NSClient Server Plugin. Support for the old NSClient protocol (check_nt) PythonScript Python Scripting Allows running INTERNAL scripts written in Python SampleConfig Sample config Sample config file (with all options) SampleScripts Scripts Scripts for checking and testing various aspects of your computer and NSClient++ Shortcuts Shortcuts Main Service shortcuts WEBPlugins WEB Server NSClient WEB Server. Use this to administrate or check NSClient via a browser or REST API OP5Montoring OP5 Monitoring Scripts/config for the op5 monitoring system. Silent install¶
Now we can put all this together using the normal silent installer which is again part of the standard windows install toolkit.So if you already have a framework for managing installs use that instead of this command line.The gist of it is:
msiexec /quiet /i <MSI FILE> PROPERTY=PropertyValue ..For instance Installing (with log) NSClient++ into c:foobar using registry as configuration and not installing the Python script binaries.
Using Silent install in 0.4.4 and 0.5.0¶
You need to add two options in these version if you plan to update the configuration in a silent install:
CONF_CAN_CHANGE forces the config to become writable (if you run silently the detection never happens so this flag is never updated).MONITORING_TOOL If no monitoring tool is specified it will default to “default” and overwrite various options given on the command line.
Silent op5 install¶
To enable active checks via NRPE from OP5 you can set the
MONITORING_TOOLoption toOP5.Silent op5 install (Northbound)¶
To enable passive reports via OP5s Northbound API you can set the
OP5_SERVER,OP5_USERandOP5_PASSWORDoptions.In this case settingMONITORING_TOOLis done automatically when everOP5_SERVERis detected.Multiple NSClient++¶
As NSClient++ uninstalls it self if you install there are two options for running multiple NSClient++ on a machine.
- You can add multiple services for the same installation
- You can install NSClient++_Secondary binary to get two instance on the same machine
- You can manually install NSClient++ (allows any number of installs)
To add multiple service you need to first create the services:
nscp service --install --name nscp2And then edit the start command so you can override the configuration.The key to look for in the registry is
...'>Install Nagios Agent On Windows(06.04.2020)HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesnscp2and there you can modify the ImagePath:\'C:Program FilesNSClient++nscp.exe\' service --run --name nscp --settings ini://${shared-path}/nsclient-2.ini