Windows 10: UIAutomation Events on Powershell

I'm trying to listen UIAutomation events using Powershell, and wrote somethings like this.



$propChangeHandler= [System.Windows.Automation.AutomationPropertyChangedEventHandler]# <summary># Adds a handler for property-changed event in particular, a change in the enabled state.# </summary># <param name="element">The UI Automation element whose state is being monitored.</param>function Subscribe-PropertyChange{param[System.Windows.Automation.AutomationElement]$element[System.Windows.Automation.Automation]::AddAutomationPropertyChangedEventHandler$element, [System.Windows.Automation.TreeScope]::Element, $propChangeHandler$OnPropertyChange, [System.Windows.Automation]::AutomationElement.IsEnabledProperty}# <summary># Handler for property changes.# </summary># <param name="src">The source whose properties changed.</param># <param name="e">Event arguments.</param>$OnPropertyChange={param[System.Object]$src, [System.Windows.Automation.AutomationPropertyChangedEventArgs]$e [System.Windows.Automation.AutomationElement]$sourceElement = $src -as [System.Windows.Automation.AutomationElement] if $e.Property -eq [System.Windows.Automation.AutomationElement]::IsEnabledProperty { [System.Boolean]$enabled = $e.NewValue -as [System.Boolean] # TODO: Do something with the new value. # The element that raised the event can be identified by its runtime ID property. Write-Host"{0} is Enable" -f $sourceElement.Current.Name } else { # TODO: Handle other property-changed events. }}function Unsubscribe-PropertyChange{param[System.Windows.Automation.AutomationElement]$element if $propChangeHandler -ne $null { [System.Windows.Automation.Automation]::RemoveAutomationPropertyChangedEventHandler$element, $propChangeHandler }}



But I got a problem.

The AddautomationPropertyChangedEventHandlermethod will need a AutomationPropertyChangedEventHandler with an eventHandler as parameter as parameter, but both AutomationPropertyChangedEventHandler and eventHandler are functions.

That means functionfunctionfunction

Please find the $propChangeHandler$OnPropertyChange from the above code.

Obviously writing it as $propChangeHandler$OnPropertyChange is not correct. How can I revise?

:)

 

Export All Administrative Events to Excel

To analyze events, from the Windows Event Viewer, there is a simple way to export all Administrative Events to Excel, with PowerShell.

Exporting all Administrative Events to Excel is a simple two Step process, as described here:

Step 1 - Create the Administrative Events View .xml file

1. Open Eventviewer (%windir%\system32\eventvwr.msc)
2. Navigate to: Event Viewer (Local) > Custom Views > Administrative Events
3. In the “Actions” pane select “Filter Current Custom View”.
4. Select the the XML tab.
5. Press Ctrl+A to select all the XML code of the Custom View.
6. Open a notepad, paste the selected code and save the file to your Desktop as AdmEvtView.xml

Step 2 - Create the csv file with the events

1. Download the ExportEvtCSV.zip file, which contains the script ExportEvtCSV.ps1 and unzip it, on your Desktop.
   It's not a fancy script, just basic PowerShell commands to create a csv file on the Desktop.
2. In Windows Search, type “ISE” (without the quotes) to open “Windows PowerShell ISE” and Run as administrator
   
3. To allow running the script, change the ExecutionPolicy, for this session. To do that, in the Console pane type:
   Code:
4. In the Windows PowerShell ISE, open and run the script: ExportEvtCSV.ps1
   The script will create a csv file with a name YYYYMMDD.HHMM.csv on the Desktop
5. When done, open the newly created .csv file, format the columns as needed and optionally save it as .xlsx, if you wish.

That’s it! You now have all the Administrative Events in Excel for filtering and further analysis.

Now to the more technical hard stuff... *Confused

There is a reason for running the script from within PowerShell ISE!

It would be great if everything was also working perfectly, when running the script from an elevated PowerShell too.

We can run it from an elevated PowerShell, which means that you just follow the Step 1, as above but for the Step 2 instead of the ISE you run the script from an elevated PowerShell.

The problem is that it will work only for anybody who has en-US format for the dates. Everyone else, who has another format (i.e. en-GB, fr-FR, el-GR etc.), the dates are not translated properly by Excel (although the script uses the –UseCulture switch) and remain as text in the en-US format.

I'm not sure if this a bug of the "export-csv" cmdlet, but although it runs the way it supposed to from within the ISE, from PowerShell there is a problem with the dates format.
As I haven’t found a way to overcome this obstacle, any suggestion from the PowerShell gurus of the forum (like my good friend Shawn @Brink, for instance), is welcome.

 

Powershell and WMI Event IDs

Is there a list of possible event IDs for Powershell and WMI similar to Troubleshooting Information for Windows Events or Windows Security Log Encyclopedia

 

PowerShell is open sourced and is available on Linux/macOS

Little bit late .. PowerShell's 10th anniversary (Nov. 14)