This script adds a vmxnet3 nic to a VM to be on the same virtual Port Proup (vPG) as the first NIC attached to the VM.
\nThis came about because a team had created a lot of VMs, say 100, all using e1000 nics (Which is the default NIC when creating a Windows 2008 R2 VM from the New VM Wizard) and I needed to get them to change to the VMXNet3 NIC. As you can expect I did not jump over the moon at the idea of having to do this manually so wrote the following script to do it for me.
\nOne additional caveat is that these VM NICs were attached a VMware vNetwork Distributed Switch. I have not tested it against a Standard vSwitch.<\/p>\n
\r\n# Description: Adds an vmxnet3 nic to a vm and connects it to the same virtual\r\n# port group on a vDS as the first nic on the vm.\r\n# Author: Herschelle42\r\n# Usage 1: Add-Additional-VMXNet3NIC.ps1 <VM as [object]>\r\n# Usage 2: Add-Additional-VMXNet3NIC.ps1 (Get-VM -Name "MyVMName")\r\n# Usage 3: $vm = Get-VM -Name "MyVMName"\r\n# Add-Additional-VMXNet3NIC.ps1 $vm<\/code>\r\n\r\nProcess {\r\n#Firstly check that the parameter that has been passed is a VM object\r\nif ( $_ -isnot [VMware.VimAutomation.Client20.VirtualMachineImpl] ) {\r\nWrite-Output "Invalid input recieved: A Virtual Machine object is expected."\r\ncontinue\r\n} # end if\r\n\r\n$vmview = Get-View -viewtype VirtualMachine -filter @{"Name" = $_.Name}\r\nWrite-Output $_.Name\r\n\r\n#Get the vNetwork Port group the VM is currently attached to\r\n$dvPortGroup = $vmview.Network[0].Value\r\n#dvportgroup-191\r\n\r\n#Get the Switch UUID of the current Network interface.\r\nforeach ($item in $vmview.Config.Hardware.Device) {\r\nif($item.Backing.Port.PortgroupKey -eq $dvPortGroup) {\r\n$SwitchUUID=$item.Backing.Port.SwitchUuid\r\n#Write-output "SwitchUUID: "$SwitchUUID\r\n#f3 40 20 50 15 c0 d1 8d-02 4d f8 b4 48 9b df 06\r\n} # end if\r\n} # end foreach\r\n\r\n# Now add a new NIC of vmxnet3 to the same network.\r\n$spec = New-Object VMware.Vim.VirtualMachineConfigSpec\r\n$spec.deviceChange = New-Object VMware.Vim.VirtualDeviceConfigSpec[] (1)\r\n$spec.deviceChange[0] = New-Object VMware.Vim.VirtualDeviceConfigSpec\r\n$spec.deviceChange[0].operation = "add"\r\n$spec.deviceChange[0].device = New-Object VMware.Vim.VirtualVmxnet3\r\n$spec.deviceChange[0].device.key = -100\r\n$spec.deviceChange[0].device.backing = New-Object VMware.Vim.VirtualEthernetCardDistributedVirtualPortBackingInfo\r\n$spec.deviceChange[0].device.backing.port = New-Object VMware.Vim.DistributedVirtualSwitchPortConnection\r\n$spec.deviceChange[0].device.backing.port.switchUuid = $SwitchUUID\r\n$spec.deviceChange[0].device.backing.port.portgroupKey = $dvPortGroup\r\n$spec.deviceChange[0].device.connectable = New-Object VMware.Vim.VirtualDeviceConnectInfo\r\n$spec.deviceChange[0].device.connectable.startConnected = $true\r\n$spec.deviceChange[0].device.connectable.allowGuestControl = $true\r\n$spec.deviceChange[0].device.connectable.connected = $true\r\n$spec.deviceChange[0].device.controllerKey = 100\r\n$spec.deviceChange[0].device.addressType = "generated"\r\n$spec.deviceChange[0].device.wakeOnLanEnabled = $true\r\n\r\n$_this = Get-View -Id $vmview.MoRef\r\n$_this.ReconfigVM_Task($spec)\r\n\r\n#Destroy all variables at completion\r\n$vm=$null\r\n$vmName=$null\r\n$vmview=$null\r\n$dvPortGroup=$null\r\n$SwitchUUID=$null\r\n$spec=$null\r\n$_this=$null\r\n$item=$null\r\n\r\nWrite-Output "Script Finished"\r\n\r\n} # end process\r\n<\/pre>\nSomething important to note that this will not move any IP address configuration from the e1000 to the vmxnet3 nic, you will need to do this inside the Guest O\/S. (That could be the subject of another post.)<\/p>\n
Another thing is that before you remove the old nic from the VM, ensure you have disabled and or uninstalled the e1000 nic from within the Windows Guest OS. This is for Windows guests anyway, otherwise you will end up with devices in device manager. And if you do not removed any fixed IP address from the e1000 you will not be able to assign that same IP address to the vmxnet3 nic as it will already “be in use” according to Windows. Just a trap I fell into myself.<\/p>\n
So for the Windows VMs the following basic steps are required:
\n1. Ran my script to add a vmxnet3 nic
\n2. Open a VI Client console window and within Windows change the old Nic to DHCP
\n3. Set new nic to the fixed ip address
\n4. disable old nic
\n5. Open device manager, uninstall the old e1000 nic
\n6. Remove the old nic from the VM.<\/p>\n
Of course if the VM(s) do not have a fixed IP and only use DHCP skip some of the steps. \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"