https://blog.michellewayz.com/categories/powercli/Recent content in PowerCLI on MichelleWayZ | Michelle Goossens | BlogHugo -- gohugo.ioenCopyright © 2019-2026, Michelle Goossens.Wed, 11 Dec 2019 07:25:00 +0000https://blog.michellewayz.com/more-powercli-scripts-to-make-life-easier/Wed, 11 Dec 2019 07:25:00 +0000https://blog.michellewayz.com/more-powercli-scripts-to-make-life-easier/ <p>Hello!</p> <p>Inspired by my last blog post, here are more PowerCLI scripts to make life easier.</p> <p>Script one; get VMs on a specific host with a specific Port Group</p> <pre class="wp-block-code"><code lang="powershell" class="language-powershell">$viserver = "vCenter IP/FQDN here" $t_host = "ESXi FQDN/IP here as used in vCenter" $portgroup = "port group name here" Connect-VIServer $viserver Get-Cluster -VMHost $t_host | Get-VMHost | Get-VM | Get-NetworkAdapter | Where-Object{$_.NetworkName -like $portgroup}</code></pre> <p>Script two; get VMs on a specific host with a specific Port Group and move them over to a new Port Group</p>https://blog.michellewayz.com/easy-powercli-script-to-help-migrate-vms-from-one-network-to-the-other/Sat, 07 Dec 2019 06:00:00 +0000https://blog.michellewayz.com/easy-powercli-script-to-help-migrate-vms-from-one-network-to-the-other/ <p>Hi everyone,</p> <p>In this post I am sharing a PowerCLI script that I made in order to easily migrate VMs from one network to the other.</p> <p>There are two versions of this script, one version has a hard-coded ESXi/vCenter instance, and the other one asks for the vCenter on each run.</p> <p>Version 1 (hard coded ESXi/vCenter):</p> <pre class="wp-block-code"><code lang="powershell" class="language-powershell line-numbers">Do { $vspherehost = "ADD-ME" $src = Read-Host -Prompt "Input source network" $dst = Read-Host -Prompt "Input destination network" Connect-VIServer $vspherehost Get-VM | Get-NetworkAdapter | where{$_.NetworkName -like $src} | Set-NetworkAdapter -NetworkName $dst } while($true)</code></pre> <p>Version 2 (Asks for ESXi/vCenter on reach run):</p>