Ok then how about this. Display the logical disk letter as Green , Yellow, or Red depending on percentage of Free Space. Then the user can go look for themselves as to what is the issue? And along those lines a number of Failed events in application, security, system events in red for the past 24 hours? I come in Monday morning I see red in this viewer I know AI need to go to the logs to see what is up. I see green I know life is ok on this server move along…
From: [email protected] [mailto:[email protected]] On Behalf Of Micheal Espinola Jr Sent: Tuesday, October 20, 2015 1:54 PM To: [email protected] Subject: Re: [NTSysADM] Looking for feedback/ideas on a script I wrote Its prudent. I normally check for freespace with other scripts, but it couldnt hurt to display a warning here if below a threshold percentile for the purposes of this script. I'm shying away from this being a stats display, because its not the purpose of the script to document the system - only to caution/warn the me - or whichever tech - is about to touch the system. I forgot to mention that I'll be putting this up on GitHub when its done. -- Espi On Tue, Oct 20, 2015 at 10:25 AM, David McSpadden <[email protected]<mailto:[email protected]>> wrote: I would add free space % for those logical disks. That is me though. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Micheal Espinola Jr Sent: Tuesday, October 20, 2015 1:22 PM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] Looking for feedback/ideas on a script I wrote So, for a couple of years I've been toying with a script that I run when I go to touch a system for any kind of maintenance. Its purpose is to reasonably quickly give me some stats about what I'm looking at - hopefully notifying me of any immediate concerns that I should have regarding anything I might plan on doing. Well, I've decided to polish this turd and see what else I can cram in here, only using built-in features of Windows: [http://i.imgur.com/fXSABV0.png] Additional information is displayed based on other things found, errors encountered, etc. The CHKDSK performed is a read-only check, after which the log file is parsed for detection of issues. By default it will check all fixed drives, but this can be altered with command-line parameters. Reboot detection is highly accurate, checking multiple identifiers. I typically run this remotely and have a report sent back to me beforehand. Any thoughts, ideas, desires in a script like this would be appreciated! -- Espi This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email.
