Reply to Message

View discussion in a popup

Replying to:
edgrigson
Enthusiast
Enthusiast

Interestingly Luc's earlier comment about not needing to change the VM properties doesn't seem correct. If I change the

portgroup name (using Get-Host | Get-VirtualPortGroup |

Set-VirtualPortGroup -Name) and then check the VM settings the entry

for the relevant network card name is indeed blank. The problem is that

if I restart the VM (or even if I power off then back on) the NIC still

shows a blank entry and is disconnected. This means if you don't follow up and rename the portgroup settings for the VMs they'll drop off the network on the next reboot. I'm testing this on vSphere

4.0U1.Here's another thread with a similar conclusion.

It also means the 'network' view in the VI client is

misleading - both the old and new network (portgroup) names are shown

and the VMs are shown (correctly) as being attached to the old network.The fix is to change the host portgroups using Luc's code and then update all the VMs to reflect the correct portgroup name - Al Renouf has already covered how to update multiple VMs, see this thread.

Regards,

Ed

Reply
0 Kudos