You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Eventing Support for PowerShell (PSEvents.dll) #1189
It is desirable to have each instance of PowerShell log ETW events to its own instance-specific event log rather than re-using the existing inbox PowerShell event log. To do this, each instance of PowerShell must register its event manifest with ETW and carry its own copy of PSEvents.dll (assuming it differs from the inbox version of the file).
Changes Required
Port PSEvents.dll to GitHub. The big step here is to create PSEvents.dll from the manifest
Generate a unique GUID and name for the event provider during each major or minor release. These values must be saved in Microsoft-Windows-PowerShell-Instrumentation.man.
Create a post-install script or cmdlet to register the event provider with ETW using wevtutil.exe
Open Issues:
wevtutil.exe should be supported on all Windows OSs, but it might now work on Nano Server. How do we support event registration in that case?
More investigation is required to determine the process for generating PSEvents.dll in GitHub. SD produces it automatically for us based on a macro.
A non-Windows eventing or logging solution should be researched as well.
Mike Richmond (@mirichmo) I don't think it's viable to change the provider guid every minor and/or major release. Monitoring teams will be reluctant to have to keep rev'ing.
As far as PSEvents generation; we did this DSC; I'll dig out the necessary build pieces.
Activity
[-]Eventing Support for Open PowerShell[/-][+]Eventing Support for Open PowerShell (PSEvents.dll)[/+][-]Eventing Support for Open PowerShell (PSEvents.dll)[/-][+]Eventing Support for PowerShell (PSEvents.dll)[/+]dantraMSFT commentedon Oct 19, 2017
Mike Richmond (@mirichmo) I don't think it's viable to change the provider guid every minor and/or major release. Monitoring teams will be reluctant to have to keep rev'ing.
As far as PSEvents generation; we did this DSC; I'll dig out the necessary build pieces.
iSazonov commentedon Jul 11, 2019
Steve Lee (@SteveL-MSFT) It seems we could close the issue.