Newly added VMs using vSphere Web Client are visible using vSphere Client

My vCenter manages 1 Datacenter which has 1 Cluster which has 2 hosts. Very simple scenario.
When I create a VM (using vSphere Web Client), the process runs OK but I can't list the created VM using vSphere Web Client. The VM is listed using vSphere Client.
The vCenter VM and a previous created VM (not by me) is listed using Web Client but any new VMs aren't.
What am I missing?
LVL 20
strivoliAsked:
Who is Participating?
 
strivoliConnect With a Mentor Author Commented:
I've got it!
VMware vCenter Server Appliance was "5.5.0.10300 Build 1945271". I've checked for updates and updated to "5.5.0.20400 Build 2442330". After the UPDT was over (and the requested reboot), the 3 Services returning me errors are now working fine AND I see all the VMs using the Web Client.
I'll run some further checks and if everything is fine I'll close this question.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
Permissions?

Have you checked the correct permissions, and users are added to the ROOT of your vCenter Server.

Check using the vSphere Client, and also check which user account you are logged in with.
0
 
TheBDPConnect With a Mentor Sr. Sys EngineerCommented:
As Andrew stated, it's a permission issue. From vSphere client, go to Home>Roles - Check permissions.
0
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

 
strivoliAuthor Commented:
Thanks to both. I use the root account on both Web Client and Client. I've checked using the Client and it seems OK. Please have a look at the attached Screen Shot. SRV-A001 is the vCenter VM.
0
 
strivoliAuthor Commented:
The Screen Shot...
Screen-Shot-1.PNG
0
 
TheBDPSr. Sys EngineerCommented:
It appears you're logging in with the domain name vsphere.local\administrator is this the correct domain name. (Just seems off to me)
0
 
strivoliAuthor Commented:
I'm logging in with the root account. root is what I type in the user name text box in both Client and Web Client.
0
 
TheBDPSr. Sys EngineerCommented:
Is there multiple hosts? I have a feeling you're logging into a single host and only seeing the machines on that host.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
root account ?

this is an account, usually used for access to ESXi only.

unless, someone has created an account called root?

You need to assign the correct permissions, and add a user account with correct permissions.
0
 
strivoliAuthor Commented:
I've logged in the Web Client using the VSPHERE.LOCAL\Administrator account but I get the same result. I created the SRV-A002 VM but I can only see it using the Client (not the Web Client). Consider that when I log in the Client I use the vCenter IP address (which is 192.168.0.111/22). Please see the attached Screen Shot.
Both root and VSPHERE.LOCAL\Administrator are defined in SRV-A011 (which is the vCenter) and both are part of the Administrator Role on both hosts (192.168.2.1 and 192.168.2.11 are set the same).
Should I try creating a new account and giving it the Administrator Role?
Screen-Shot-2.PNG
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
just check the permissions on each VM object are also root? Permissions may not be propagated down the tree.

I would create a new account, with Administrator Role.
0
 
strivoliAuthor Commented:
The Cluster lists (please see the Screen Shot 2 attached in my previous post) 2 hosts and 7 VMs (one of these is the vCenter). All 9 objects have the same entries in the "Permissions" tab. They are identical.
I will create a new account and report back.
0
 
TheBDPSr. Sys EngineerCommented:
Okay, you cannot login to a vsphere web client with the root username. You will need to create a new account, under administrator and make sure it has rights to the entire datacenter.

Try logging into the vSphere application first with your new credentials. Then try logging into your vSphere web client: https://srv-a011/vsphere-client/

If you're logging in with IP's make sure that you're using the same IP as your vCenter Server. Whatever srv-a011 is.
0
 
strivoliAuthor Commented:
Thanks for the suggestions. I have 1 VM that works as it should and it wasn't created by me. Might it be it was created using another account (not root) and that account has been deleted? If I could find out which account it has been used, I could use it again. How can I find out which account created a specific VM?
0
 
gheistConnect With a Mentor Commented:
You need to refresh web client often. It often misses updates behind the scenes..
0
 
strivoliAuthor Commented:
This discussion fully replicates my scenario. I think there's no issue with the user (account) root being used. I think the issue happens because vCenter isn't working as it should. If you have any suggestions on how to fix vCenter, they are welcome. Thanks.
0
 
gheistCommented:
Yes, vsphere web client is of sub-standard usability.
We are almost not using it since 5.5U2 client allows us to get back access to VMs mistakenly converted to vmx-10.
0
 
strivoliAuthor Commented:
UPDATE: I use Firefox to access the Web Client. After the VMware vCenter Server Appliance UPDT I had to clear Firefox's cache.
0
 
strivoliAuthor Commented:
The solution is to apply the update to VMware vCenter Server Appliance. Sometimes, updates do help :-)
Although, you have taken the time to read my question and provide suggestions. This is why I decided to split points to all partecipants.
Thank you for helping.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.