PowerShell Logo Small

Register-ObjectEvent



This is the built-in help made by Microsoft for the command 'Register-ObjectEvent', in PowerShell version 5 - as retrieved from Windows version 'Microsoft Windows Server 2012 R2 Standard' PowerShell help files on 2016-06-23.

For PowerShell version 3 and up, where you have Update-Help, this command was run just before creating the web pages from the help files.

SYNOPSIS

Subscribes to the events that are generated by a Microsoft .NET Framework object.

SYNTAX


Register-ObjectEvent [-InputObject] <PSObject> [[-SourceIdentifier] [<String>]] [[-Action] [<ScriptBlock>]] [-EventName] <String> [-Forward] [-InformationAction
{SilentlyContinue | Stop | Continue | Inquire | Ignore | Suspend}] [-InformationVariable [<System.String>]] [-MaxTriggerCount [<System.Int32>]] [-MessageData [<PSObject>]]
[-SupportEvent] [<CommonParameters>]



Search powershellhelp.space

DESCRIPTION


The Register-ObjectEvent cmdlet subscribes to events that are generated by .NET Framework objects on the local computer or on a remote computer.


When the subscribed event is raised, it is added to the event queue in your session. To get events in the event queue, use the Get-Event cmdlet.


You can use the parameters of Register-ObjectEvent to specify property values of the events that can help you to identify the event in the queue. You can also use the Action
parameter to specify actions to take when a subscribed event is raised and the Forward parameter to send remote events to the event queue in the local session.


When you subscribe to an event, an event subcriber is added to your session. To get the event subscribers in the session, use the Get-EventSubscriber cmdlet. To cancel the
subscription, use the Unregister-Event cmdlet, which deletes the event subscriber from the session.



<

RELATED LINKS

Online Version: http://go.microsoft.com/fwlink/p/?linkid=294002
Get-Event
New-Event
Register-EngineEvent
Register-WmiEvent
Remove-Event
Unregister-Event
Wait-Event

REMARKS

<

Examples


-------------------------- EXAMPLE 1 --------------------------

PS C:\>$query = New-Object System.Management.WqlEventQuery "__InstanceCreationEvent", (New-Object TimeSpan 0,0,1), "TargetInstance isa 'Win32_Process'"
PS C:\>$processWatcher = New-Object System.Management.ManagementEventWatcher $query
PS C:\>register-objectEvent -inputObject $processWatcher -eventName "EventArrived"



This example subscribes to events generated when a new process starts.

The command uses the ManagementEventWatcher object to get EventArrived events. A query object specifies that the events are instance creation events for the Win32_Process
class.










-------------------------- EXAMPLE 2 --------------------------

PS C:\>$query = New-Object System.Management.WqlEventQuery "__InstanceCreationEvent", (New-Object TimeSpan 0,0,1), "TargetInstance isa 'Win32_Process'"
PS C:\>$processWatcher = New-Object System.Management.ManagementEventWatcher $query
PS C:\>$action = { New-Event "PowerShell.ProcessCreated" -Sender $sender -EventArguments $EventArgs.NewEvent.TargetInstance }
PS C:\>register-objectEvent -inputObject $processWatcher -eventName "EventArrived" -action $action

Id Name State HasMoreData Location Command
-- ---- ----- ----------- -------- -------
2 422cfe5a-65e... Running True New-Event "PowerShe...



This example shows how to specify an action to respond to an event. When you specify an action, events that are raised are not added to the event queue. Instead, the action
responds to the event.

In this example, when an instance creation event is raised indicating that a new process is started, a new ProcessCreated event is raised.

The action uses the $Sender and $EventArgs automatic variables which are populated only for event actions.

The Register-ObjectEvent command returns a job object that represents the action, which runs as a background job. You can use the Job cmdlets, such as Get-Job and
Receive-Job, to manage the background job.

For more information, see about_Jobs.










-------------------------- EXAMPLE 3 --------------------------

PS C:\>$s = new-pssession -computername Server01, Server02
PS C:\>invoke-command -session $s -filepath ProcessCreationEvent.ps1
PS C:\>invoke-command -session $s { get-event }# ProcessCreationEvent.ps1function Enable-ProcessCreationEvent{ $query = New-Object System.Management.WqlEventQuery
"__InstanceCreationEvent", `
(New-Object TimeSpan 0,0,1), `
"TargetInstance isa 'Win32_Process'" $processWatcher = New-Object System.Management.ManagementEventWatcher $query $identifier = "WMI.ProcessCreated"
Register-ObjectEvent -input $processWatcher -eventName "EventArrived" `
-sourceIdentifier $identifier -messageData "Test" -forward}EnableProcessCreationEvent



This example shows how to subscribe to object events on remote computers.

The first command creates PSSessions on two remote computers and saves them in the $s variable.

The second command uses the FilePath parameter of the Invoke-Command cmdlet to run the ProcessCreationEvent.ps1 script in the each of the PSSessions in $s.

The script includes a Register-ObjectEvent command that subscribes to instance creation events on the Win32_Process object through the ManagementEventWatcher object and its
EventArrived event.










-------------------------- EXAMPLE 4 --------------------------

PS C:\>$timer = New-Object Timers.Timer
PS C:\>$timer.Interval = 500
PS C:\>$job = Register-ObjectEvent -inputObject $timer -eventName Elapsed -sourceIdentifier Timer.Random -Action {$random = Get-Random -Min 0 -Max 100}
PS C:\>$job.gettype().fullnameSystem.Management.Automation.PSEventJob
PS C:\>$job | format-list -property *

State :
RunningModule : __DynamicModule_6b5cbe82-d634-41d1-ae5e-ad7fe8d57fe0
StatusMessage :
HasMoreData : True
Location :
Command : $random = Get-Random -Min 0 -Max 100
JobStateInfo : Running
Finished : System.Threading.ManualResetEvent
InstanceId : 88944290-133d-4b44-8752-f901bd8012e2
Id : 1
Name : Timer.Random
ChildJobs : {}...

PS C:\>$timer.Enabled = $true
PS C:\>& $job.module {$random}60
PS C:\>& $job.module {$random}47



This example shows how to use the dynamic module in the PSEventJob object that is created when you include an Action in a event registration.

The first command uses the New-Object cmdlet to create a timer object. The second command sets the interval of the timer to 500 (milliseconds).

The third command uses the Register-ObjectEvent cmdlet to register the Elapsed event of the timer object. The command includes an action that handles the event. Whenever the
timer interval elapses, an event is raised and the commands in the action run. In this case, the Get-Random cmdlet generates a random number between 0 and 100 and saves it
in the $random variable.

When you use an Action parameter in a Register-ObjectEvent command, the command returns a PSEventJob object that represents the action. The command saves the job object in
the $job variable.

The PSEventJob object that the Register-ObjectEvent cmdlet returns is also available in the Action property of the event subscriber. For more information, see
Get-EventSubscriber.

The fourth command shows that the $job variable contains a PSEventJob object. The fifth command uses the Format-List cmdlet to display all of the properties of the
PSEventJob object in a list.

The PSEventJob has a Module property that contains a dynamic script module that implements the action.

The sixth command enables the timer.

The remaining commands use the call operator (&) to invoke the command in the module and display the value of the $random variable. You can use the call operator to invoke
any command in a module, including commands that are not exported. In this case, the commands show the random number that is being generated when the Elapsed event occurs.

For more information about modules, see about_Modules.