I’ll have to chew on this, thanks so much!
From: [email protected] [mailto:[email protected]] On Behalf Of Dave Lum Sent: Wednesday, August 12, 2015 2:22 PM To: [email protected] Subject: RE: [NTSysADM] Remote temperature monitoring software Sure. I actually have a couple of variations. Example1 (this is specific to the temperature probe failure threshold): Alert Management / Temperature Probe Failure (means system temp has gone above the warning threshold and is at the failure threshold) Execute application, absolute path: "<path>\server1.shutdown.cmd" Contents of server1.shutdown.cmd: powershell.exe -File "<path>\server.shutdown.ps1" Contents of server.shutdown.ps1: Send-MailMessage -to <email addresses> -Subject Server1 alert - shutdown!" -Body "Server1 has overheated and has shut down to prevent damage due to heat. IT support has been alerted via text and email and will contact one of you shortly. " -SMTPSERVER <smtp server IP> -From server.alerts@ <mailto:server.alerts@%3cmydomain> <mydomain> --------------- Example 2 (this passes variables of the alert name to PowerShell) Alert Management / Physical Disk failure Execute application, absolute path: "<path>\Server1.alert.cmd" Physical_Disk_Failure Contents of Server1.alert.cmd: powershell.exe -File "<path>\Server1.alert.ps1" %1 Contents of Server1.alert.ps1 Send-MailMessage -<email addresses> -Subject "Server1 alert!" -Body "Server1 has a system error generated by the $args hardware monitor. IT support has been alerted via text and email and will contact one of you shortly but no action is required by you at this time. Resources *possibly* affected are <list of resources like email, printers, file share>" -SMTPSERVER <Smtp server IP> -From server.alerts@ <mailto:server.alerts@%3cmydomain> <mydomain> ----------------- The “magic” in the .alert one is adding the name of the test at the end of the application path, the %1 in the .CMD file and the $args in the PS script, so when the email fires the $args is replaced with Physical_Disk_Failure or whatever you’ve put at the end of the command in Server Administrator. This lets you use one batch file but change the alert to match whatever has triggered it The server.shutdown and server.alert emails have two sets of recipients: The first set are the CTO / CIO-level staff who need wo know something is up but don’t take direct action themselves, and the 2nd group is the IT staff who need to fix the issue (in fact the PS script has a 2nd Send-MailMessage that sends a slightly different alert to the IT staff) I actually have a 3rd alert sequence called server.warning.cmd / server.warning.ps1 that alerts only the IT staff, like several of the “Warning” level alerts It can get fancier than this of course, but this should give you a start. This also assumes the OS is still running so you’ll want something separate for monitoring/alerting should the box itself dros offline (I use MaxFocus formerly GFIMax for that, and MXAlerts to monitor email functionality since the above alerts are dependent on the OS and email working). Dave From: [email protected] [mailto:[email protected]] On Behalf Of Joseph Schvarcz Sent: Wednesday, August 12, 2015 10:04 AM To: [email protected] Subject: RE: [NTSysADM] Remote temperature monitoring software Dave, Could you possible share these .cmd and ps scripts for Server Admin? I’ve been trying for the longest time to setup email alerts for temps or disk failure, that sort of thing and was never able to figure it out I wish Dell would incorporate that into OMSA.. TIA Joseph Schvarcz From: [email protected] [mailto:[email protected]] On Behalf Of Dave Lum Sent: Wednesday, August 12, 2015 11:58 AM To: [email protected] Subject: RE: [NTSysADM] Remote temperature monitoring software Curious timing as just last night I created some .CMD files and PowerShell scripts for Dell Server Administrator to email alerts when internal temperature probes hit specific thresholds (as well as failed disk in a RAID array and other alerts). I imagine HP’s and IBM have a similar free tool that can be leveraged for that as well. Another option would be to configure temperature alerts to write to a Windows event log and have a scheduled task that is triggered by an event log entry. In that case if you found a utility that simply could write to the event log based on temperature events you could trigger/alert off of that. (Scheduled tasks…task trigger = “when a specific event is logged”…choose event ID then run application …etc) Do you want to track the temperatures, or alert on them, or both? Dave From: [email protected] [mailto:[email protected]] On Behalf Of Tony Burrows Sent: Tuesday, August 11, 2015 6:13 PM To: [email protected]; [email protected] Subject: [NTSysADM] Remote temperature monitoring software In the past couple days I've had a few people ask me about monitoring temperatures in various systems ranging from desktops/laptops to servers and even ESXi hosts. Does anyone know of a tool that can do this? Preferably it would be something cloud based and reasonably priced. Asking for too much? :-) I'm open to ideas, including ones that monitor all kinds of hardware related stuff. Regards, Tony Attention: Information contained in this message and or attachments is intended only for the recipient(s) named above and may contain confidential and or privileged material that is protected under State or Federal law. If you are not the intended recipient, any disclosure, copying, distribution or action taken on it is prohibited. If you believe you have received this email in error, please contact the sender, delete this email and destroy all copies. Attention: Information contained in this message and or attachments is intended only for the recipient(s) named above and may contain confidential and or privileged material that is protected under State or Federal law. If you are not the intended recipient, any disclosure, copying, distribution or action taken on it is prohibited. If you believe you have received this email in error, please contact the sender, delete this email and destroy all copies.
