My question is in the title : Is it possible to run vCenter 5.1 or 5.5 without SSO ?
No, vCenter Server 5.1 and later requires SSO.
I don't want to install AD because I don't need of it. It was not necessary in vCenter 5.0 and I would like to continue.
Is sometone know a solution ?
You don't need AD to have SSO.
Take a look on SSO FAQ: VMware KB: vCenter Single Sign-On 5.1 FAQ
Do I need an Active Directory or LDAP setup to use SSO?
No. SSO has its own internal user store. You can manage all principal data in it, using the SSO admin interface in the vSphere Web Client. You can also assign vCenter Server privileges to users and groups from this internal datastore. Alternatively, you can also point SSO to users residing in the OS where you deployed SSO.---
Senior Infrastructure Specialist
SSO is different, you need SSO to install VCenter setup.
SSO is required for vCenter and it's components.
Thanks for your answer.
My Win 2008 server is a "standalone" with just a DNS server installed on it.
When I try to install SSO (vCenter 5.5) I have two warnings :
- ! - Machine is not domaine joined
- ! - Certificates will usethe machine ip(xxx.xxx.xxx.xxx) insead of FQDN. It is recommender that you have a static IP adress for this to work correctly.
-> I have a static IP adress + reverse records on my hosts file.
Is it a problem ?
If I continu my install with Web vSphere Client it's impossible because I have a certificat error in my logs;
Type : Server certificate assertion not verified and thumbprint not matched
Can you help me to define what is wrong, (this update is a real nightmare)
SSO is just the possibility to configure Multiple Identity Sources . So mainly is not an Bad idea. But an Additional Layer to care about.
Between 5.1 and 5.5 they changed SSO completely. From an SQL RSA Database to an inhouse config without SQL.
So you don't need AD for SSO. as by Default it's using the Local Identity Source.
So you have same Setup then afterwards, just with SSO and Local Identity.
No Issues with that.
Thanks for your answers !
Ok my vCenter must be 5.5 or later, it's tested and it's good.
About my error, I took two actions:
- On the vCenter it was Two network cards. The main card ( DNS name of the vCenter with his IP ) was is second position. I moved up on the network manager to the first position.
- I disabled IPV6 how caused me some problems.
Now it's ok.
I didn't do a splited test to know if it was the first action or the second who fixed my issue but it works. For me the network card number is the problem nuber one. It seems to me, that I read someting on it somewhere (vmware documentation or ... ?)
Thanks again !