Part-1: Working with Event Logs using PowerShell Part–2 : Working with Event Logs using PowerShell :- Get-EventLog Welcome to the part 3 of the “PowerShell and Event Log” post, In my previous post we shows the usages of “Get-EventLog” cmdlet. Today we are going to use some more advance and cool features of the… Continue reading Part–3 : Working with Event Logs using PowerShell :- Get-EventLog
In my previous blog post,, i had tried to cover the basics of “Event Logs”, and in https://amandhally.com/2013/11/12/part-1-working-with-event-logs-using-powershell/previous post we had also saw the use of “Show-EventLog” cmdlet. There is no benefit of PowerShell if we are exploring “Event Logs” using GUI tools. So let’s start working on PowerShell console. There are two main… Continue reading Part–2 : Working with Event Logs using PowerShell :- Get-EventLog
PowerTip of the Day, from PowerShell.com: You might know the more.com tool: when you pipe output to more.com, the output is displayed page by page: PS> Get-EventLog -LogName System | more However, “more” can be dangerous as you see here. You will not get any results for a long time, and your CPU… Continue reading “More” Can Be Dangerous – Use Better Alternative in PowerShell
PowerTip of the Day, from PowerShell.com: In a previous tip you learned that using “more” to paginate output can be dangerous, and instead you should use Out-Host -Paging. To “update” more.com and make it behave like Out-Host with the -Paging parameter set, use a proxy function like this one: function more { param(… Continue reading Creating a “Better” More in PowerShell
PowerTip of the Day, from PowerShell.com: Your own PowerShell functions can have the same sophisticated parameters, parameter types and parameter sets that you know from cmdlets. However, it is not always obvious how to construct the param() block appropriately. A clever way is to spy on cmdlets and look how they did it.… Continue reading Spying on Parameters in Powershell
