powercli – Love I.T., Live I.T., Embrace I.T.

How to setup a Powershell Environment to manage VMware

August 18, 2015 No Comments

Make sure .NET Framework 4.5 is installed (HERE)
Make sure that Powershell 3.0 is installed (do not use 4.0 as it breaks add-ins) (HERE)
Install vSphere PowerCLi (HERE)
open PS and run: Set-ExecutionPolicy -ExecutionPolicy unrestricted
Close and reopen PS and create a new profile by running: New-item –type file –force $profile
Run the following: Notepad $profile
Paste the following into the file:
1. Add-PSSnapin VMware.VimAutomation.Core
  Add-PSSnapin VMware.VimAutomation.Vds
  Add-PSSnapin VMware.VimAutomation.License
  Add-PSSnapin VMware.DeployAutomation
  Add-PSSnapin VMware.ImageBuilder
  Add-PSSnapin VMware.VimAutomation.Cloud
Save the PS1 file on your desktop and open a session via the shortcut.

Automation, Cloud, Command Line Shortcuts, Virtualization

Connecting direct to an Org in vCloud with PowerCLi

February 12, 2015 No Comments

I found it quite risky to connect to a vCloud instance as a SysAdmin and perform calls to a specific Org and ensure not to touch other orgs by a simple typo in my commands.

Use the following command to connect via PowerCLi direct to an org in vCD.

Connect-CIServer -Org WWW -Server XXX -Username YYY -password ‘ZZZ’

Automation, Cloud, Command Line Shortcuts, Cool Tricks and Tools, Powershell, Virtualization

A nice Slash and Burn script for vCD

August 22, 2014 No Comments

WARNING!!! This will delete ALL VMs in your vCD!!!!!

Connect to your vCD with “Connect-CIServer ” and run the following:


Stop-CIVApp * -Confirm:$false
Remove-CIVApp * -Confirm:$false
sleep 5
Remove-OrgNetwork * -Confirm:$false

Then manually delete any gateway devices and then run the following to clean up all the orgs:


Set-OrgVdc -Enabled:$false
remove-OrgVdc -Confirm:$false
Set-Org -Enabled:$false 
remove-Org -Confirm:$false

Big thanks to my colleague Grant Voss for this awesome little cleanup script.

Automation, Virtualization

Modifying an AutoDeploy rule in PowerCLi

January 29, 2014 No Comments

After some hunting I found that modification of an AutoDeploy rule wasn’t as simple as Edit-DeployRule 🙂 My coworker Joe Keegan, the God of AutoDeploy walked me through the simple steps to modify existing rules rather that deleting and replacing.

NOTE: You do NOT need to use “” or other characters around the <VALUE> EXCEPT for the Pattern Value. Otherwise, the object is found when it checks the name against the GetType.

To replace the Pattern of an existing rule:
Get-DeployRule -name <RULENAME> | Copy-DeployRule -ReplacePattern “<NEW PATTERN>”

To replace the Image, Location, or Profile of an existing rule:
Get-DeployRule -name <RULENAME> | Copy-DeployRule -ReplaceItem <NEW PROFILE NAME>