VMWare web client

Soldato
Joined
12 Nov 2002
Posts
14,600
Location
In my own little world
I'm trying to install a test lab at home with VMWare VSphere 5.1 but it seems riddled with problems and constant workarounds compared to v5.0

I'm currently trying to register a vcenter server using the vsphere web client administration tool but keep getting the following error.

vcenter.jpg


There doesn't seem to be a consistent workaround, it seems someone else got it to work by doing this but it didn't work for me.

My assumptions were correct... kinda. Steps to get this to work:

Log in to vSphere web client as admin (admin@System-Domain, this is the default user added during install of vcenter)
Go to Administration -> SSO Users and Groups
Go to Groups tab and click on __Administrators__
Click on the little man icon to Add Princilpals
Select the local vcenter server as the identity source and search for a local user you can log in as.
Then add that user and click OK.
Log in as the local user.
You should see the vCenter listed after you log in.

Has anyone else seen and resolved this issue ? :(

MW
 
I did this install just the other week but using a windows domain group for authentication.

I'm not clear on the register part, I ran with the simple install and this wasn't required.

From what I recall once logged onto the web client I did the following

vCenter > vCenter Servers (under Inventory Lists) > Selected my server > Manage (Tab) > Permissions > + Click add permissions.

From there click add on the popup box, select the local user (I had one auto created called admin which i'm using as backup incase AD goes down)

hit add again and then ok it.

Set role as administrator and then give whatever access you require. Then ok again.

You can change the password of the local account or add a new one from the Administration > SSO Users and Groups > Users tab.

Hopefully this makes sense >.<
 
Doesn't this just mean you are missing the correct SPN dns records for the vcenter?

How do I create an SPN DNS record ?

From what I can work out is I can ADSIedit the vCenter servicePrincipalName but i'm kinda guessing what i'm adding

MW
 
Last edited:
Im half way through my lab with - 2 x vcenters vmware view implementation with full site recovery manager. i feel your pain! Everything is a work around!
 
I can't say I've had any of these issues with vCenter and 3 hosts, but I've always used vSphere Client. Are there advantages to using the web client?
 
Apparently VMware are doing away with the vSphere client, there are a few things that can be only done from the web client but currently the vSphere client has more functionality.

I've re-installed my hosts several times now, I keep changing things and getting different problems occur. It's a bit of a ball ache but the experience from the troubleshooting is becoming a quite valuable.

MW
 
Try this, apparently, this is a work around on almost anything. Instead of "vcenter2", type the IP address instead and make sure that you can ping it. :)
 
Back
Top Bottom