Have you ever stared down the barrel of endless repetitive clicks in VMware vSphere, knowing you’re in for hours of mindless work? Recently, I faced a scenario where I needed to update hundreds of virtual NICs across just as many virtual machines. Manual changes would have been soul-crushing, so I turned to VMware PowerCLI and transformed this monotonous task into a 5-minute automated script. Here’s how I did it.<\/p>\n\n\n\n
Picture this: You have dozens, maybe hundreds, of VMs, each with multiple network adapters needing reassignment to a new distributed port group. The manual process looks something like this:<\/p>\n\n\n\n
The task was not just time-consuming but error-prone. I knew there had to be a better way.<\/p>\n\n\n\n
PowerCLI is VMware’s powerful scripting toolkit that supercharges PowerShell to manage your VMware environment programmatically. Here\u2019s how to get started:<\/p>\n\n\n\n
Open PowerShell as Administrator and run:<\/p>\n\n\n\n
Install-Module -Name VMware.PowerCLI -Scope CurrentUser\n<\/code><\/pre>\n\n\n\nAccept the prompts, and voil\u00e0! You’re ready to automate.<\/p>\n\n\n\n
\n\n\n\nThe Journey to Automation Nirvana<\/h3>\n\n\n\n
My path to automating network changes wasn\u2019t without its hiccups. Let me walk you through the evolution of my approach.<\/p>\n\n\n\n
First Attempt: The Naive Approach<\/h4>\n\n\n\n
Initially, I wrote a script to update only “unassigned” network adapters. Logical, right? Wrong. What PowerCLI considered \u201cunassigned\u201d didn\u2019t always match what I saw in the vSphere UI.<\/p>\n\n\n\n
Second Try: The Brute Force Method<\/h4>\n\n\n\n
I decided to reassign all the adapters, regardless of their current state. While functional, this approach overwhelmed vCenter, leading to failed operations.<\/p>\n\n\n\n
Final Solution: The Smart Approach<\/h4>\n\n\n\n
The breakthrough came with a more intelligent script that:<\/p>\n\n\n\n
\n- Validates host state before making changes.<\/li>\n\n\n\n
- Introduces delays between operations to keep vCenter happy.<\/li>\n\n\n\n
- Includes robust error handling and logging.<\/li>\n\n\n\n
- Verifies changes to ensure accuracy.<\/li>\n<\/ul>\n\n\n\n
\n\n\n\nThe Magic Script That Does It All<\/h3>\n\n\n\n
Here\u2019s the polished script that saved the day:<\/p>\n\n\n\n
\n\n\n\n<#\n.SYNOPSIS\n This script connects to vCenter, finds all VMs matching specific criteria, \n and assigns unassigned virtual NICs to a specified Distributed Port Group.\n\n.DESCRIPTION\n 1. Connects to vCenter Server.\n 2. Searches for VMs in \"Datacenter Immaculate Constellation\" -> \"DELL-R720-CLUSTER\" -> Host \"192.168.88.5\".\n 3. Filters only VMs that are powered off.\n 4. Assigns all empty NICs to \"TRUNK-space-holder-Arista-DPort-Group\".\n 5. Prints progress and errors to the console.\n\n.NOTES\n Tested with PowerCLI 12+ on vCenter 8.\n#>\n\n# ---[ 1. Setup and Connect to vCenter ]---\nWrite-Host \"Starting script...\"\n\n# Enable PowerCLI logging\n$logPath = Join-Path $PSScriptRoot \"powercli_log.txt\"\nWrite-Host \"Enabling PowerCLI logging to: $logPath\"\nSet-PowerCLIConfiguration -Scope User -LogLevel Warning -InvalidCertificateAction Ignore -Confirm:$false | Out-Null\nStart-Transcript -Path $logPath -Force\n\nWrite-Host \"Connecting to vCenter...\"\n\ntry {\n # Update with your vCenter server name and credentials\n Connect-VIServer -Server \"vcenterserver.dc1.local\" -User \"YOUR_USERNAME\" -Password \"YOUR_PASSWORD\"\n Write-Host \"Successfully connected to vCenter.\"\n}\ncatch {\n Write-Host \"ERROR: Failed to connect to vCenter. Error details:\"\n Write-Host $_\n return\n}\n\n# ---[ 2. Locate the Datacenter, Cluster, and Host ]---\nWrite-Host \"Locating Datacenter, Cluster, and Host...\"\n\ntry {\n $datacenterName = \"Datacenter Carlton II\"\n $clusterName = \"DELL-R720-CLUSTER\"\n $hostName = \"192.168.88.5\"\n\n # Get the Datacenter object\n $dc = Get-Datacenter -Name $datacenterName -ErrorAction Stop\n \n # Get the Cluster object in that Datacenter\n $cluster = Get-Cluster -Name $clusterName -Location $dc -ErrorAction Stop\n\n # Get the Host object in that Cluster\n $vmHost = Get-VMHost -Name $hostName -Location $cluster -ErrorAction Stop\n\n Write-Host \"Datacenter found: $($dc.Name)\"\n Write-Host \"Cluster found: $($cluster.Name)\"\n Write-Host \"Target Host found: $($vmHost.Name)\"\n \n # Double check we're working with the correct host\n if ($vmHost.Name -ne $hostName) {\n Write-Host \"ERROR: Retrieved host does not match target host name\" -ForegroundColor Red\n Disconnect-VIServer -Confirm:$false\n return\n }\n\n Write-Host \"`nWARNING: This script will only process VMs on host $hostName\" -ForegroundColor Yellow\n Write-Host \"Other hosts in the cluster will not be affected`n\"\n\n # Get all hosts in cluster for reference\n $allHosts = Get-VMHost -Location $cluster\n Write-Host \"Hosts in cluster $($cluster.Name):\"\n foreach ($h in $allHosts) {\n if ($h.Name -eq $hostName) {\n Write-Host \" * $($h.Name) (TARGET HOST)\" -ForegroundColor Yellow\n } else {\n Write-Host \" - $($h.Name) (will not be modified)\"\n }\n }\n Write-Host \"\"\n\n # Check host state\n Write-Host \"`nChecking host state...\"\n Write-Host \"Host State: $($vmHost.State)\"\n Write-Host \"Host Connection State: $($vmHost.ConnectionState)\"\n Write-Host \"Host Power State: $($vmHost.PowerState)\"\n \n if ($vmHost.State -ne \"Connected\" -or $vmHost.ConnectionState -ne \"Connected\") {\n throw \"Host is not in a valid state for network operations. Current state: $($vmHost.State), Connection state: $($vmHost.ConnectionState)\"\n }\n}\ncatch {\n Write-Host \"ERROR: Unable to locate Datacenter, Cluster, or Host. Error details:\"\n Write-Host $_\n Disconnect-VIServer -Confirm:$false\n return\n}\n\n# ---[ 3. Find All Matching VMs ]---\nWrite-Host \"Searching for powered-off VMs...\"\n\ntry {\n $vmList = Get-VM -Location $vmHost |\n Where-Object { $_.PowerState -eq \"PoweredOff\" }\n\n if (!$vmList) {\n Write-Host \"No powered-off VMs found on host '$hostName'.\"\n return\n }\n else {\n Write-Host \"Found the following powered-off VMs on host '$hostName':\"\n $vmList | ForEach-Object { Write-Host \" - $($_.Name)\" }\n\n # ---[ 4. Assign Each Unassigned NIC to the Specified DPort Group ]---\n $dportGroup = Get-VDPortgroup -Name \"TRUNK-space-holder-Arista-DPort-Group\" -ErrorAction Stop\n if (!$dportGroup) {\n Write-Host \"ERROR: Could not find distributed port group 'TRUNK-space-holder-Arista-DPort-Group'\" -ForegroundColor Red\n return\n }\n\n Write-Host \"`nFound distributed port group: $($dportGroup.Name)\" -ForegroundColor Green\n Write-Host \"Port group key: $($dportGroup.Key)`n\" -ForegroundColor Green\n\n foreach ($vm in $vmList) {\n Write-Host \"`nProcessing VM: $($vm.Name)\" -ForegroundColor Yellow\n \n # Get all network adapters for the VM\n $nics = Get-NetworkAdapter -VM $vm\n Write-Host \" Found $($nics.Count) network adapter(s)\"\n\n foreach ($nic in $nics) {\n Write-Host \"`n Processing NIC: $($nic.Name)\"\n Write-Host \" Current Network: [$($nic.NetworkName)]\"\n \n try {\n # Check host state again before each operation\n $hostState = Get-VMHost -Name $hostName\n if ($hostState.State -ne \"Connected\" -or $hostState.ConnectionState -ne \"Connected\") {\n throw \"Host is not in a valid state for network operations. Current state: $($hostState.State), Connection state: $($hostState.ConnectionState)\"\n }\n \n # First remove the network assignment\n Write-Host \" Removing current network assignment...\" -ForegroundColor Yellow\n $nic | Set-NetworkAdapter -NetworkName \"\" -Confirm:$false -ErrorAction Stop\n Start-Sleep -Seconds 2 # Wait 2 seconds between operations\n \n # Then assign the new network\n Write-Host \" Assigning to '$($dportGroup.Name)'...\" -ForegroundColor Yellow\n $nic | Set-NetworkAdapter -Portgroup $dportGroup -Confirm:$false -ErrorAction Stop\n Start-Sleep -Seconds 2 # Wait 2 seconds after assignment\n \n # Verify the change\n $updatedNic = Get-NetworkAdapter -VM $vm | Where-Object { $_.Id -eq $nic.Id }\n Write-Host \" New Network Assignment: [$($updatedNic.NetworkName)]\" -ForegroundColor Green\n }\n catch {\n Write-Host \" ERROR: Failed to update network. Error details:\" -ForegroundColor Red\n Write-Host \" $_\" -ForegroundColor Red\n Write-Host \" Host State at time of error: $($hostState.State)\"\n Write-Host \" Host Connection State at time of error: $($hostState.ConnectionState)\"\n continue # Continue with next NIC instead of stopping\n }\n }\n \n # Wait 5 seconds between VMs to avoid overwhelming vCenter\n Write-Host \"`n Waiting 5 seconds before processing next VM...\" -ForegroundColor Blue\n Start-Sleep -Seconds 5\n }\n }\n}\ncatch {\n Write-Host \"ERROR: An issue occurred while searching for or updating VMs. Error details:\"\n Write-Host $_ -ForegroundColor Red\n}\n\n# ---[ 5. Cleanup \/ Disconnect from vCenter ]---\ntry {\n Write-Host \"`nDisconnecting from vCenter...\"\n Disconnect-VIServer -Confirm:$false\n Write-Host \"Script completed.\"\n}\ncatch {\n Write-Host \"ERROR: Could not disconnect from vCenter properly. Error details:\"\n Write-Host $_ -ForegroundColor Red\n}\nfinally {\n # Stop logging\n Stop-Transcript\n}\n<\/code><\/pre>\n\n\n\nHow It Works<\/h3>\n\n\n\n1. Initial Setup and Safety<\/h4>\n\n\n\n
The script enables logging and ignores certificate warnings for seamless execution.<\/p>\n\n\n\n
2. Smart Host State Validation<\/h4>\n\n\n\n
It checks that the host is ready for changes, avoiding issues with disconnected or powered-off hosts.<\/p>\n\n\n\n
3. Careful Network Changes<\/h4>\n\n\n\n
Network adapters are reassigned with delays to prevent overwhelming vCenter.<\/p>\n\n\n\n
4. Robust Verification<\/h4>\n\n\n\n
Each change is verified to ensure it was applied successfully.<\/p>\n\n\n\n
\n\n\n\nResults: Time Saved, Sanity Preserved<\/h3>\n\n\n\n
Here\u2019s the math:<\/p>\n\n\n\n
\n- 50 VMs with 3 NICs each = 150 changes<\/strong><\/li>\n\n\n\n
- Manual time: ~2\u20133 hours<\/li>\n\n\n\n
- Script time: ~5 minutes<\/li>\n\n\n\n
- Errors: Zero<\/li>\n\n\n\n
- Bonus: I actually enjoyed a coffee break while the script ran.<\/li>\n<\/ul>\n\n\n\n
\n\n\n\nPro Tips From the Trenches<\/h3>\n\n\n\n\n- Always validate host state<\/strong> \u2013 Ensure the host is connected and ready.<\/li>\n\n\n\n
- Introduce delays<\/strong> \u2013 Prevent vCenter from throwing errors due to rapid requests.<\/li>\n\n\n\n
- Log everything<\/strong> \u2013 You\u2019ll thank yourself later.<\/li>\n\n\n\n
- Verify changes<\/strong> \u2013 Mistakes happen, but not on your watch.<\/li>\n\n\n\n
- Graceful error handling<\/strong> \u2013 Scripts should recover from unexpected issues.<\/li>\n<\/ol>\n\n\n\n
\n\n\n\nReady to Try It Yourself?<\/h3>\n\n\n\n
Here\u2019s how to get started:<\/p>\n\n\n\n
\n- Install PowerCLI and connect to your vCenter.<\/li>\n\n\n\n
- Copy the script and update the connection details.<\/li>\n\n\n\n
- Run it.<\/li>\n\n\n\n
- Enjoy your newfound free time.<\/li>\n<\/ol>\n\n\n\n
\n\n\n\nConclusion<\/h3>\n\n\n\n
PowerCLI isn\u2019t just a tool\u2014it\u2019s a superpower for VMware administrators. Automating repetitive tasks not only saves time but also reduces errors, giving you more bandwidth for meaningful work.<\/p>\n\n\n\n
Have you automated any VMware tasks with PowerCLI? Share your stories in the comments\u2014I\u2019d love to hear how you\u2019re making VMware work smarter, not harder!<\/p>\n\n\n\n
Happy scripting! \ud83d\ude80<\/p>\n\n\n\n\n","protected":false},"excerpt":{"rendered":"