OK, now another issue I'm experiencing using the vSphere 6.5 web client, and I'm talking today, not yesterday, but more issues in one day...
How much time does an administrator need to spend fixing web client issues, and AD integration issues, before this product works??????
Brand new 6.5 deployment, WINDOWS deployment, machine account in AD, I can log in with AD account just fine, I'm an admin, I see everything, but I can't add permissions to vCenter from AD to inventory objects, I can only add global permissions.
Can someone add some value here and smack VMware product managers and Sr mgmt in the face? I think this may be the only fix to this product that will work at this point.
"but I can't add permissions to vCenter from AD to inventory objects, I can only add global permissions." - What is the behavior when you attempt to do this? Can you attach a screenshot?
I am curious why you chose the Windows version for a new deployment, rather than the Appliance. We have 3 v6.5 appliances joined to AD with no issues. We did however have some join issues, but it turned out we had some reverse name resolution issues.
Oh we have a VCSA running 6.02... and we had so many problems with AD integration, and permissions, and other, and with a critical project underway AKA SAP refresh, we didn't want to mess around with it any longer and take risks of having it hold us up. that's why.
So, we chose windows because all of our windows based vCenter installations work fine, UNTIL NOW that is, now that we are at 6.5 and are forced into the web client for everything, which is a far cry from production ready, even after all these reiterations..
Today alone I have experienced the following:
1) content was blocked because it was not signed by a valid security certificate when logging into VCSA 6.02
2) Can't add permissions from AD to vCenter 6.5 inventory
3) Client integration plugin issues, got it working in chrome, but not IE
4) After finally getting logged into VCSA via chrome after playing around with the URL to get past the first issue mentioned above, I then launched a new tab in the browser to access vCenter 6.5 and it states you don't have flash installed, but it is in fact and installed, otherwise I wouldn't be logged in to VCSA 6.02... It appears the installation of the client integration plugin needed to deploy OVF I have been seeing a bunch of bogus issues like what I'm stating above.
This is an absolute nightmare.. god bless you for trying to keep up and fix this. you work is much appreciated, you deserve a pay raise in advance of this..
I had the same issue.
for me update to build 5318154 (6.5 d) solved the problem.
Can you let us know if upgrading to 6.5d resolves your "add permission" issue as well?
Well I will say the AD integration seems much improved in VCSA 6.5 than in 6.x from my experience. Though I will say the AD Ldap integration in v6.5 is a step back from v6.0. I dont remember the specifics, I believe it had to do with using the Global Catalog. When we couldnt get VCSA 6.5 to join with AD properly is when we discovered that when we tried to use AD ldap like we did with VCSA v6. We discovered someone had hosed our reverse names on some Domain Controllers when that got fixed it all worked, assigning permissions too of course.
As to your other issues:
1. Unsure on that one.
2. I am sure you have checked all this, but you are joined properly and such correct? Can the SSO query users in your AD?
3. This is always breaking in browser updates, I am not sure who is to blame here
4. I think this is problem with the pepperflash on your system. I had the same issue with Chrome and Pepperflash. My pepperflash was not getting updated on my Mac for some reason. Google about that please.
Also I do not work for VMware. I just jumped in to offer my two cents. I have never tried v6.5 Windows, but maybe I can still help.
Thanks! I have no choice but to get this resolved.. input much appreciated! Hope to see you at VMworld and buy you a beer.
Our backup product isn't certified for 6.5d at this time, 6.5b is supposed to work with it, but even that is another issue, EMC\Dell has to provide some hotfixes for us to get into Networker 9.1.1 so v6.5b is even supported.. I'm not certain I can move this up to 6.5d just yet, but certainly it is a consideration if backup product supports it.
#4 I think you can fix. Im quite certain its an issue with your pepperflash on your box, or lack of pepperflash that Chrome needs.
Would it be possible to try out the 6.5d upgrade in test? I just want to make sure we have a path forward for your issue, because if there's still a bug we want to know ASAP to fix it. Of course that would be a big time investment, including being able to actually replicate the error first, so I understand if it's not possible.
I hate to bring in another issue, but they seem to be coming at me one after the next..
Adding NFS datastore in 6.5.... OUCH!
In early days, we added NFS datastore 1 host at a time.
in 5.1 VMware introduced the "host accessibility" option in the wizard allowing us to check the box for which hosts in the cluster to add the NFS datastore to
Now, in 6.5 web client, I added NFS datastore but the "host accessibility" option didn't exist , so I assume we are back to 1 host at a time...
BUT - when trying to add NFS datastore to 2nd host in my cluster it barked at me stating the name already exists in the datacenter..
Is there a resolution for this? Perhaps I'm doing something wrong?
Hi Labsy2, try unchecking the Settings->Show only recent objects toggle and this will display all vms, datastores and portgroups in the navigator.
In my opinion you can go trough datastors view-> datacenter righ mouse -> add nfs -> choose hosts
hosts and clusters -> datacenter focus right click all vc actions -> add datastore
nfs datastore in datastore view -> host accessibility -> add hosts
hope this help