# Vmware ESXI v7.03 issue with network portgroup name same on both standard and dv switches

**URL:** <https://forum.ansible.com/t/vmware-esxi-v7-03-issue-with-network-portgroup-name-same-on-both-standard-and-dv-switches/36987>\
**Category:** Ansible Project\
**Tags:** vmware\
**Created:** [August 15, 2022, 2:01pm UTC](https://forum.ansible.com/t/vmware-esxi-v7-03-issue-with-network-portgroup-name-same-on-both-standard-and-dv-switches/36987 "2022-08-15T14:01:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jason\_B](https://avatars.discourse-cdn.com/v4/letter/j/7993a0/32.png) [@Jason\_B](https://forum.ansible.com/u/Jason_B)\
**Post date:** [August 15, 2022, 2:01pm UTC](https://forum.ansible.com/t/vmware-esxi-v7-03-issue-with-network-portgroup-name-same-on-both-standard-and-dv-switches/36987/1 "2022-08-15T14:01:57Z")

</div>

We recently upgraded our venter to 7.03 and ESXI systems to v7.03 and this issues has started rearing its ugly head. Basically the scenario is as follows:

- Standard Switch with a port-group name that is the same as Distributed Switch port-group name exists
- When deploying a new VM via vmware\_guest module - the VM is deployed to the Standard Switch, and not the Distributed Switch.

Example:

WormHoleNet on Standard Switch  
WormHoleNet on Distributed Switch

Deployment code:

---

<div class="post-metadata">

**Author:** ![Jason\_B](https://avatars.discourse-cdn.com/v4/letter/j/7993a0/32.png) [@Jason\_B](https://forum.ansible.com/u/Jason_B)\
**Post date:** [January 20, 2023, 8:26pm UTC](https://forum.ansible.com/t/vmware-esxi-v7-03-issue-with-network-portgroup-name-same-on-both-standard-and-dv-switches/36987/2 "2023-01-20T20:26:44Z")

</div>

I found that the solution was to update my custom execution environment – which applied the latest VMware SDK.