To make that task a bit easier, I wrote the Event-O-Matic script. It’s a GUI that allows you to pick a number of events, and the script will generate the PowerShell code, and place it in the clipboard. The Event-O-Matic script was mentioned during our VMworld 2013 US session VSVC4944.

Update November 9th 2022:

• removed PSSnapin loaded test

Update September 7th 2013:

• added at least PowerShell v3 test
• added PowerCLI core pssnapin loaded test

The script presents a GUI based on Windows Forms. The PowerShell code to generate the GUI was created by the Sapien PrimalForms Community Edition.

Due to the size of the script, I did not place the complete script inline in this post, but rather I provided a download link. Make sure to “unblock” the script after you downloaded it, to avoid problems with the PowerShell execution policy.

[wpfilebase tag=file id=28]

The use of the script is quite easy (we think). A short overview of a typical session:

1. Start the script
2. In the vSphere Server text-box enter the name or IP address of an ESXi or a vCenter server.
3. Click the Connect button.
   1. If the connection is successful, the line below the vSphere Server text-box will display the version of the vSphere Server.
   2. The Events box will list all the events that exist on the vSphere server.
   3. The number of events that are found will be displayed just above the Events box.
4. When you hover over a specific event, the description of the event (if present) will be displayed in a pop-up box.
5. You can also use the Name and Description radio-buttons to switch between the eventname and it’s description.
6. You can search for text that should appear in the Name or Description field. Enter the text in the Search text box and click Search. The Events window will now only show the events that have the specific text in the Name of in the Description field.
7. When you select an event by clicking on it, the event will appear in the Selected box.
8. When you click on an event in the Selected box, the event will be removed.
9. When all the required events are selected, click the Generate Code button. The code will be stored in the clipboard.
10. By default the code generator uses the Get-VIEvent cmdlet, but by selected the Get-VIEventPlus switch, you can generate code that uses the Get-VIEventPlus function. See my Get the vMotion/svMotion history post for the Get-VIEventPlus function.
11. The Finish button is self-explaining I assume.

During our VMworld US 2013 session, we showed a short video that demonstrated the use of the script.

Enjoy !

Siw stands for Server in Waiting. We selected that term since we liked the sound of it, no double entendre should be suspected

Some of these issues, that most of you probably know:

• Connect-VIServer can be slow
• The 1st cmdlet in a session is slow
• Keep the PowerCLI version aligned on all the stations were it is used
• Have powerfull stations to run scripts against “big” vSphere environments

The idea is that you would have a “workhorse” station, with enough resources to cope with the bigger vSphere environments. On this workhorse station you set up a number of robust sessions, and when you need to run a PowerCLI script on a client, you would connect from the client to such a robust session, and execute your script in that robust session.

To make the creation and usage of these robust sessions in combination with PowerCLI easier, I created a number of functions.

The Functions

function New-SiwSession {

<#  
.SYNOPSIS  Creates a number of robust PowerCLI sessions   
.DESCRIPTION The function will create a number of
  robust remote sessions on a specific server. The
  remote sessions will be initialised to run PowerCLI
  scripts
.NOTES  Author:  Luc Dekens  
.PARAMETER ComputerName
  The hostname of the server where the robust PowerCLI
  sessions will be created
.PARAMETER Credential
  A PSCredential object that contains the credentials for
  the robust session.
.PARAMETER SiwType
  The name prefix for the robust PowerCLI sessions
.PARAMETER NumberOfSessions
  The number of robust PowerCLI sessions that shall be
  created. The maximum number is 99.
.PARAMETER vServer
  The name of the vSphere server to which the robust PowerCLI
  session shall connect
 .PARAMETER vCredential
  The PSCredential object that will be used to connect to the
  $vServer server. If $null, the session credentials will be
  used

.EXAMPLE
  PS> New-SiwSession -ComputerName $tgtServer -Credential $cred `
  >> -SiwType "PowerCLI" -NumberOfSessions 3 -vServer "vCenter"
#>

  param(
    [String]$ComputerName,
    [System.Management.Automation.PSCredential]$Credential,
    [String]$SiwType,
    [ValidateRange(1,99)] 
    [Int]$NumberOfSessions,
	[String]$vServer,
    [System.Management.Automation.PSCredential]$vCredential
  )

  if(!$vCredential){$vCredential = $Credential}
  $pclStartUp = {
    param($vServer,$Credential)

    Add-PSSnapin VMware.VimAutomation.Core
    Set-PowerCLIConfiguration -DisplayDeprecationWarnings $false -Confirm:$false | Out-Null
    Connect-VIServer -Server $vServer -Credential $Credential | Out-Null
    Get-Datacenter | Out-Null
  }

  $newSiwOption = @{
    IdleTimeout = -1
    NoMachineProfile = $true
    SkipCACheck = $true
    SkipCNCheck = $true
    SkipRevocationCheck = $true
  }
  $SiwOptions = New-PSSessionOption @newSiwOption 

  $newSiwSession = @{
    ComputerName = $ComputerName
    Credential = $Credential
    EnableNetworkAccess = $true
    Name = $null
    SessionOption = $SiwOptions
  }

  1..$NumberOfSessions | %{
    $newSiwSession.Name = $SiwType + ("-{0:d2}" -f $_)
    $SiwSession = New-PSSession @newSiwSession
    $pclInit = @{
      Session = $SiwSession
      ScriptBlock = $pclStartUp
      ArgumentList = $vServer,$Credential
    }
    Invoke-Command @pclInit
    Disconnect-PSSession -Session $SiwSession -Confirm:$false | Out-Null
  }
}

function Get-SiwSession {

<#  
.SYNOPSIS  Returns a robust PowerCLI session
.DESCRIPTION The function will return an available robust
  PowerCLI session. If no robust sessions are available,
  function  will return $null
.NOTES  Author:  Luc Dekens  
.PARAMETER ComputerName
  The hostname of the server where the robust PowerCLI
  sessions will be created
.PARAMETER Credential
  A PSCredential object that contains the credentials for
  the robust session.
.PARAMETER SiwType
  The name prefix for the robust PowerCLI sessions
.EXAMPLE
  PS> Get-SiwSession -ComputerName $tgtServer -Credential $cred `
  >> -SiwType "PowerCLI"
#>

  param(
    [String]$ComputerName,
    [System.Management.Automation.PSCredential]$Credential,
    [String]$SiwType 
  )

  $getSiwSession = @{
    ComputerName = $ComputerName
    Credential = $Credential
  }

  Get-PSSession @getSiwSession |
  Where {$_.Name -match "^$($SiwType)" -and $_.Availability -eq "None"} |
  Get-Random
}

function Abort-SiwSession {

<#  
.SYNOPSIS  Aborts robust PowerCLI sessions   
.DESCRIPTION The function abort all robust PowerCLI
  sessions on a server.
.NOTES  Author:  Luc Dekens  
.PARAMETER Session
  The handle of the session that needs to be aborted.
.EXAMPLE
  PS> Abort-SiwSession -Session $pcliSession
#>

  param( 
    [CmdletBinding()]
    [Parameter(Mandatory=$true,ValueFromPipeline=$true)]
    [System.Management.Automation.Runspaces.PSSession]$Session
  )

  $session | %{
    $cimInstance = @{
      ComputerName = $_.ComputerName
            ClassName = "Win32_Process"
      Filter = "Name Like 'wsmprovhost.exe'"
    }
    Get-CimInstance @cimInstance |
    Invoke-CimMethod -MethodName Terminate -Confirm:$false
  }
}

Annotations

Line 38: The function allows a request to create up to99 robust PowerCLI sessions. But keep in mind that PowerShell itself has a throttle limit of 32 sessions. In other words PowerShell handle the instructions in the first 32 sessions and place the other remote sessions in wait.

Line 45-52: These are the lines that set up the robust session as a PowerCLI session.Line 49: The robust session can’t handle PowerCLI warning messages correctly, so we suppress those.

Line 51: This random PowerCLI cmdlet avoids the delay you normally see on the 1st PowerCLI cmdlet that is executed in a new session.

Line 54-60: The session options.

Line 63-69: The parameters used to create the remote session.

Line 71-81: The loop and code block that create the requested number of robust PowerCLI sessions

Line 46,77,79: Notice how the values for the PowerCLI code block are passed to the remote session.

Line 80: The remote session is immediately disconnected.

Line 107: Since you can only connect to a robust session with the same credentials as the ones which created the session, the function requires these as a parameter as well.

Line 118: To avoid over-using the 1st robust session that is returned, the function will return a “random” available session.

Line 146: Since this function is/was primarily used to “kill” unresponsive functions, it uses the Win32_Process instance that corresponds with a robust session on that target remote server.

Sample Usage

Since the hard work for setting up and using robust PowerCLI sessions is done in the functions, the use of these robust PowerCLI sessions is quite simple.

First you create a number of sessions.

$tgtServer = "SRV1"
$vCenter = "VCENTER"

$pswdSecure = ConvertTo-SecureString -String $pswd -AsPlainText -Force
$cred = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $username,$pswdSecure

# Create 3 Siw sessions
New-SiwSession -ComputerName $tgtServer -Credential $cred -SiwType "PowerCLI" -NumberOfSessions 3 -vServer $vCenter

Once the sessions are created, you connect to one of the available ones to run your PowerCLI code.

# Use one of the sessions to run PowerCLI code on SRV1
$session = Get-SiwSession -ComputerName $tgtServer -Credential $cred -SiwType "PowerCLI"

Connect-PSSession -Session $session | Out-Null
Invoke-Command -Session $session -ScriptBlock {Get-VMHost}
Disconnect-PSSession -Session $session | Out-Null

# Drop the sessions
Get-PSSession -ComputerName $tgtServer -Credential $cred | Remove-PSSession

Should something go wrong and the robust PowerCLI session is stuck, you can try the abort function to kill the session.

# Abort the sessions
Get-PSSession -ComputerName SRV1 -Credential $cred | Abort-SiwSession

Enjoy!