<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)">  <title>Running Windows batch files through NRPE</title> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="country-region"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/>  <style>  </style> </head> <body lang=EN-CA link=blue vlink=purple> <div class=Section1> I don’t think that Nagios/nscp is geared to what you want it to do. Instead, I would suggest that a Scheduled Task might be more appropriate (or use something like SMS to push out an update on demand/on a schedule, if you have it in place).<o:p></o:p> <o:p> </o:p> Cheers<o:p></o:p> <o:p> </o:p> <div> <o:p></o:p> Steve Onotsky<o:p></o:p> Server Support Technologist<o:p></o:p> Broadridge<o:p></o:p> Investor Communication Solutions, <st1:country-region w:st="on"><st1:place w:st="on">Canada</st1:place></st1:country-region><o:p></o:p> <st1:Street w:st="on"><st1:address w:st="on">5970 Chedworth Way</st1:address></st1:Street><o:p></o:p> <st1:place w:st="on"><st1:City w:st="on">Mississauga</st1:City> <st1:State w:st="on">ON</st1:State> <st1:PostalCode w:st="on">L5R 4G5</st1:PostalCode></st1:place><o:p></o:p> Tel: (905) 507-5328<o:p></o:p> Fax: (905) 507-5312<o:p></o:p> Inet: <a href="mailto:steve.onotsky@broadridge.com">steve.onotsky@broadridge.com</a><o:p></o:p> <o:p></o:p> Quis custodiet ipsos custodes?<o:p></o:p> - Juvenal, Satires, VI, 347<o:p></o:p> <o:p></o:p> </div> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> From: Leleux, Jeremy J [mailto:jjleleux@sunlandconstruction.com] Sent: May 19, 2009 10:15 To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] Running Windows batch files through NRPE<o:p></o:p> </div> <o:p> </o:p> Hi All,<o:p></o:p> I’m running Nagios 3.0.6/CentOS 5.2 for my Nagios server. Its monitoring my Windows Servers, all 2003, I have NSClient++ on those servers and its working fine. My problem is that I’m trying to centralize the configs on the NSClient++’s w/ the help of batch files. I have setup commands to allow me run the scripts w/ the help of check_nrpe, but they will not run.<o:p></o:p> Here is the contents of one of my batch files, nscpp_config.bat, to update the NSClient++ config:<o:p></o:p> @echo off<o:p></o:p> xcopy \\10.10.0.50\public\Departments\Infor~1\Scripts\nscpp_copy.bat C:\Progra~1\NSClient++ /Y<o:p></o:p> exit<o:p></o:p> When I try to run this command from my Nagios Server, I get an “Invalid Drive Specification Error”. And here is my config line to allow the command in NSClient++:<o:p></o:p> cp_script=nscpp_config.bat<o:p></o:p> If someone else has done this in past, please let me know how you have done this.<o:p></o:p> Respectfully,<o:p></o:p> Jeremy Leleux<o:p></o:p> IT Administrator<o:p></o:p> Sunland Construction, Inc.<o:p></o:p> Corporate Division<o:p></o:p> Office: 337.550.2142<o:p></o:p> Fax: 337.546.0245<o:p></o:p> <st1:City w:st="on"><st1:place w:st="on">Mobile</st1:place></st1:City>: 337.580.6062<o:p></o:p> Email: jjleleux@sunlandconstruction.com<o:p></o:p> </div> </body> </html> <pre>This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.