Remote Console Bug is Creating a vSS instead of connecting to a existing vDS port group

[greglamb]

We have discovered a bug that we would like to report. When creating a network adapter and then attaching it to a vDS port group from within the Remote Console when pressing OK vCenter actually creates a vSS without any uplinks. This bug is easily re-creatable in our environment.

We created a VMware SR 3762996 to report the bug however it has been 5+ weeks without a response.

A newly created VM

1. Launch Remote Console
2. Manage - Virtual Machine Settings
3. Remove the NIC (no NICS remaining)
4. OK
5. Manage - Virtual Machine Settings
6. Add - Network Adapter, Network Connection - select a VLAN (port group on a vDS is displayed), connect at power-on
7. Finish
8. Within the Guest-OS the network adapter is displayed as disconnected
9. From the Remote Console - Manage - Virtual Machine Settings the Network Adapter device status: connected (is not selected)
10. Select Connected; error: Failed to connect virtual device ethernet0
11.From the vSphere Web Client. vCenter - Networking View a new vSS is created with the vDS port group name.
12. From the Remote Console - Manage - Virtual Machine Settings, remove the network adapter, OK
13. From the vSphere Web Client. vCenter - Networking View - the vSS is removed

From the vSphere Web Client - VM and Templates view - VM - Edit Settings, adding the network adapter and selecting the vDS Port Group behaves correctly.

For some reason the Remote Console is creating a vSS named the vDS port group when adding a network adapter.

vCenter - version: 6.0.0.18326 / Build: 3339083
VMware Remote Console - version: 8.0.0
Guest OS: Microsoft Windows Server 2012 (64-bit)
Compatibility: ESXi 6.0 and later (VM version 11)
VMware Tools: Running, version:10240 (Current)

[Czernobog]

Bumping this because the bug is still there in VMRC 9.0.

It's a real shame, but the VMRC is to dangerous to use now, since someone can easily break the connection. I've opened a SR and am curious what the resonce will be.

On a sidenote, trying to remediate the issue with the Web Client did not work for me, I had to use the fat client.

[roman79]

Hi greglamb,

Thank you for this post. It saved me a lot of time with troubleshooting an issue.

I can confirm it happens in my environment with vCenter Server 6.0 U2a and VMware Remote Console 9.0.0 build-4288332.

I have opened the case with VMware and will keep you posted on its progress.

[CQuartetti]

I believe the SR that greglamb is referring to is 16995905905. This issue has been fixed and will be released in VMRC 10.0.

[roman79]

Hi CQuartetti,

Thank you for an update. It is good to know that things are moving forward.

In regards to the issue, the SR # 16310979512 was opened from my account.

Could you share ETA for VMRC 10.0 to be released?

Thanks,

[CQuartetti]

VMRC 10.0 was released 2017-06-01 with the fix for this issue.

The Windows and Mac apps will auto-update themselves. Otherwise the current version can always be found here: Download VMware Remote Console

[roman79]

Hi CQuartetti ,

Thank you for letting us know - appreciate it.

The only issue is that VMRC doesn't show to which vDS port group the VM is connected.

It would be great to have this one fixed in the future releases of the console.

Regards,

[CQuartetti]

The only issue is that VMRC doesn't show to which vDS port group the VM is connected.

We would have liked to fix that for 10. It's being tracked by ticket #1480673 for all desktop products and platforms. Linux and macOS products show the portgroupKey in some places. The fix will show the proper display name.