Unexpected Shutdown Comments

We've all seen the following prompt after servers have "unexpectedly shutdown"



This is the summary of the “unexpected shutdown” comments left on our lab servers and the script I used to get them (which I'm sure could use some cleaning up/optimization). If your engineers are anything like us, I'm sure you'll find some interesting comments in your logs as well.

=========================================================================
$strCategory = "computer"

$objDomain = New-Object System.DirectoryServices.DirectoryEntry

$objSearcher = New-Object System.DirectoryServices.DirectorySearcher
$objSearcher.SearchRoot = $objDomain
$objSearcher.Filter = ("(objectCategory=$strCategory)")

$colProplist = "name"
foreach ($i in $colPropList){$objSearcher.PropertiesToLoad.Add($i)}

$colResults = $objSearcher.FindAll()

foreach ($objResult in $colResults)
{$objComputer = $objResult.Properties

$objComputer.name
$SysEvent = new-object system.diagnostics.eventlog("system", $objComputer.name)
$SysEvent.entries | ?{ $_.eventid -match "1076" } | %{$_.Message.Split("`r`n")[16]}
}

=========================================================================
Comment: vmware
Comment: really? Dirty shut down woudNOT be my prefered way to patch .
Comment: dipshit, I clicked reboot... don't know how it gets any more "planned" than that.
Comment: esx4 shit itself again
Comment: ?
Comment: I called for this you liar!
Comment: vmware explode
Comment: ?
Comment: vmware blow up.
Comment: dunno
Comment: liar! I rebooted :)
Comment: shaddap
Comment: vmware blow up.
Comment: dunno
Comment: liar! I rebooted :)
Comment: kaboom vmware
Comment: #
Comment: ;alkjsfda;sldkfj
Comment: kah-BOOM
Comment: dunno
Comment: shaddap
Comment: vmware blow up.
Comment: dunno
Comment: liar! I rebooted :)
Comment: ruh roh
Comment: JS
Comment: df
Comment: Installed new dimms
Comment: some jackass downed the blade?