re: Exploring the PowerShell PSDiagnostics Module

Serhad MAKBULOĞLU — Fri, 23 Nov 2012 12:27:58 GMT

useful script, thanks.

re: Exploring the PowerShell PSDiagnostics Module

_Emin_ — Fri, 23 Nov 2012 08:49:57 GMT

Hi,

I hope that you enjoy your trip in Europe.

I enjoyed your post as I've been recently troubleshooting a PS remoting issue.

But, can you pls be more specific about the version of Powershell and the plateform you've been using for these commands. I can only see in the title of the image that it's powershell V3 and that some syntaxes are V3 only.

The following log doesn't exist on Windows 7: Microsoft-Windows-PowerShell/Admin

It has been introduced on W8/WS2012 platforms. You don't get it even if you install the WMF 3.0 on Windows 7.

The content of the PSDiagnostics cmdlets has also changed.

On V2, you have: (dir Function:Enable-PSTrace).Definition

$Properties = Get-LogProperties ($script:psprovidername + $script:analyticlog)

$Properties.Enabled = $true

Set-LogProperties $Properties

To enable Eventlog logging, instead of using wevtutil, you can do with admin privileges for example:

$log = New-Object -TypeName System.Diagnostics.Eventing.Reader.EventLogConfiguration -ArgumentList "Microsoft-Windows-NDIS/Diagnostic"

$log.isEnabled = $true

try {

$log.SaveChanges()

} catch {

Write-Warning -Message "Failed to save changes because $($_.Exception.Message)"

}