Follow this insane project https://t.co/3Ey40ZvcEq
This article provides the steps to migrate the Service Console and VMkernel port from Standard Switches to a Distributed Switch as describes in KB 1010614. This should be a piece of cake if it's working. But it keeps pop-up an error like this: Call "HostNetworkSystem.UpdateNetworkConfig" for object "networkSystem-8482" on vCenter Server "vCenter.mikes.lan" failed.
No worries, there is another KB article which describes: Can't migrate management interface to vDS on ESXi 5.0. Saved you would think. When you enable coredump functionality, you can specify which vmk interface should be used (most likely the management network which is vmk0). This means the portgroup cannot be deleted, even if you remove the interface from there, and the migrate process fails. After trying this KB it ain't working for me.
In my believe I tried everything but had no luck. Together with VMware support which took more then 4 hours to come with a workaround. It is quite a difficult solution with detours, but it works!
I assume you've done this KB 1010614 which is not working for you.
I assume you've done also this KB with no number which is not working for you. (search google for: Can't migrate management interface to vDS on ESXi 5.0 )
Create a temporary management vmkernel (management network) from DCUI using a vmnic which is free to use. I use VMNIC 4. At the end I will use VMNIC0 for the console. If that's your intention too, don't use VMNIC0 now. Give it a free IP address to prevent conflicts. I use the IP 172.16.1.235 VLAN 99 which will be added as vmk0
Connect the host to vCenter server using this IP (172.16.1.235)
Create a 2nd temporary management vmkernel (mgmt-temp) using VMNIC 4. Again use a free IP address like 172.16.1.229 VLAN 99 which will be vmk1. Go to the VI Client Host and Clusters > Configuration > Networking > Properties
Choose VMkernel and click Next
Fill in your credentials as shown above and check the management traffic port group
Fill in your IP credentials and click Next and Finish
Disconnect and remove this host from vCenter server and connect with the IP above (vmk1). This is necessary in order to release vmk0.
Delete the portgroup (management network) vmk0. Go to the VI Client Host and Clusters > Configuration > Networking > Properties > and select the management network port group and remove it. Ignore warnings.
Connect the host to the vDS and configure the management vmkernel port with the final correct IP 172.16.5.10 VLAN 5 in my case. This is the ultimate aim. Go to the VI Client Networking >
Click Add Host...
Select the Host together with the vmnics you want to connect to dvSwitch0 (in my case)
Hit Next, Next and Finish
Check if your dvSwitch0 uplinks are in order. If not, remove them and reorder them. It would be neat if dvUplink1 is related to vmnic0 and so on. Step 2 is to add the final Management Console IP to vmk0 by Adding a new VMkernel management Port group
Disconnect and remove the host from vCenter server
Re-connect the host to vcenter server using the right DNS credentials. In my case esx10.mikes.lan (esx10 should have a dns record 172.16.5.10). Probably you see now no uplinks in the vDS. Re-add the host to the vdSwitch0 as explained in point 8. This is necessary because you add your host with a different IP address.
Delete the portgroup (mgmt-temp) vmk1 and the standard vSwitch that contains it
Begin configuring the portgroups as they should be
If there is any other way to do this I would be very happy to hear!