Can somebody please share the patch?
We need a solution for this issue right now.
Would you mind sending me a copy of the patch? Thanks.
VMware is able to share the patch.
Please open a SR and you will get the patch directly from VMware.
The official KB is offline because VMware will release a new build soon.
So it's been more than a month now, the problem is still there. No official KB and no patch. WTF, VMware???
I've spend over 8 hours setting up a new VDP instance before seeing this post. Thank you for posting the workaround, which is to set the VDP to a standard vswitch instead of a dvswitch. That got it working here too. How could this have gone through and been released with this bug?? Does VMware not test these solutions before they are released? Especially this which geared at enterprises, chances are they are not using a standard vswitch. Very frustrating and makes me doubt VMware's releases at times.
Please open a official SR at VMware to get the patch.
If you have a supported environment U are save.
VMware will release a new build of VDP soon.
The frustration comes from the fact that this thread is about the only "official" way to get information about this pretty major bug. There should be an active KB article with updated information (eg. open an SR to get a hotfix / awaiting 6.1.3 release / or whatever) and the product download should have a warning pointing to the KB. Too many hours wasted by customers only to finally find this thread and understand why.
I am having the same issue, been looking at this for over a week now.
originally told it was a certificate issue ... obviously not....
new build on latest software, so originally thought it was the build side as works fine unless pointing to vDS, systems do not even need to be turned on or connected, just the vhardware needs to be set to a vDS to have it stall.
I will be raising a call with VMware as still looks like they have not released anything for this issue.
Anything new on this problem? Does anybody can share patch resolution because it's not available???
i did the patching also and restarted webclient. So i'am able to connect now to VDP's. but seeing speed differences between vCenter 5.5/6.0
once clicking on the VDP Plugin on 5.5 until 2 secs i could choose between the VDP Appliances.
if i do same on 6.0 U2 > i could wait >30secs to see the Appliances. didn't had that with 5.5 before. (No performance issues there. Thinking PSC is not the best Solution)
So i hope next version is back more stable > as currently i regret did upgrade to vCenter 6.0.
PS: not sure if it's allowed to post non-officially Patches
I've had the issue with the VDP plugin not showing in the vSphere Client since the upgrade to 18.104.22.168 on vCenter 5.5U3a. Been working with VMware for a week to get it resolved. They supplied the patch file, which was only 2kb different than the .war file already there. Dropped it in and restarted vsphere client. Still didn't show. Now we're looking at perms for that file since it's owned by root, but in 5,5U3a I'm not showing the vsphere-client as a user. Waiting to hear back now. It's been escalated to EMC.
Do you have the SR number for this one?
Here is my SR# 16112176705.
Thanks for the link to your site. I actually tried this yesterday but the vsphere-client user does not exist in 5.5 vCenter.