Welcome a new face to the team


3TSeV8RqYou are about to see new and exciting blog posts arrive from a fresh face on the team.  Please do join me in welcoming the new Technical Marketing expert on all things PowerCLI – Kyle Ruddy.

Kyle works as part of our Technical Marketing team, being responsible for vSphere Operations Management and will also cover APIs / SDKs and CLIs.

Kyle has been a big fan of PowerCLI, and automation in general, having technically reviewed PowerCLI books, presented PowerCLI based VMUG sessions, and been a strong community contributor. Kyle’s focus will be to continue evangelizing PowerCLI and its use to help VMware customers increase their productivity and consistency and to bring you the latest and greatest in news and new ways to use PowerCLI.

During his spare time, Kyle enjoys golfing, SCUBA diving, and most motorsports activities.


You can find Kyle’s personal blog at and can contact him on twitter via @kmruddy


5 comments have been added so far

  1. Hello

    A request

    One feature that I would like to see added to PowerCLI “New-VM” is the ability to add CPU and Cores during deployment so that the VM doesn’t have to be rebooted to apply these after deployment. I know the “Set-VM” contains this but it would be better added to “New-VM” as well.

    for changing cores I use this example but requires the VM to be shutdown.

    $VMname = VMname
    $spec = New-Object –Type VMware.Vim.VirtualMAchineConfigSpec –Property @{“NumCoresPerSocket” = $_.cores}


Leave a Reply

Your email address will not be published. Required fields are marked *