PowerShell Universal
Ironman SoftwareForums
Search…
v3
About
What's New in v3?
Get Started
Additional Resources
Installation
Licensing
System Requirements
Supported Browsers
Cmdlet Help
Templates
API
About
Endpoints
Security
Error Handling
Rate Limiting
Automation
About Automation
Scripts
Jobs
Schedules
Terminals
Triggers
User Interfaces
About
Dashboards
Pages
Desktop
About Desktop Mode
File Associations
Hotkeys
Pages
Protocol Handlers
System Events
Platform
Cache
Modules
Monitoring
Notifications
Published Folders
Templates
Translations
Variables
Configuration
About
API
Environments
Git
Hosting
Login Page
Management API
Persistence
Settings
Security
Repository
Running as a Service Account
Best Practices
Development
Debugging Scripts
Editor
Hangfire
Logging
Profiling
Visual Studio Code Extension
Changelog
Extension Changelog
Legacy Universal Dashboard Docs
Powered By GitBook
System Events
Launch scripts when certain events happen in Windows.
System Events in the Admin Console
System events subscribe to WMI events within Windows and run scripts. You can then take action by running scripts.

Defining a System Event

To define a system event, you can use the New-PSUSystemEvent cmdlet within the systemEvents.ps1 file. The following example triggers the systemEvent.ps1 script when a pwsh.exe process is started.
New-PSUSystemEvent -Script "systemEvent.ps1" -Environment "Default" -Credential "Default" -Type "Create" -Condition "TargetInstance isa `"Win32_Process`" and TargetInstance.Name = `"pwsh.exe`"" -Name "PowerShell Started"

Accessing Event Data

When a script is executed, you will receive a $TargetInstance parameter. This contains the WMI object that caused the event to trigger.
param($TargetInstance)
​
New-BurntToastNotification -Text "PowerShell Started! $TargetInstance"
Desktop - Previous
Protocol Handlers
Next - Platform
Cache
Last modified 2mo ago
Copy link
Outline
Defining a System Event
Accessing Event Data