You have to add a fqdn Domain Name. Not the NetBios Name.
So add MYDOMAIN.WHATEVER should work.
Frank
FQDN = NetBIOS Name = mydomain.
MYDOMAIN.WHATEVER also doesn't work, SSO said that server must join this domain, not MYDOMAIN. Single-lable domain names is not a best practice but they works well in 5.1.
JimKnopf99 wrote:
You have to add a fqdn Domain Name. Not the NetBios Name.
If this is an old Windows 2000 Domain this does not need to be the Netbios, as Windows 2000 allowed single label Domain names without a . ( Official notation would be MYDOMAIN. )
operando : Long story short: Don't use those single label domain names. SSO won't be the only software that will punish you for using it. Things like Exchange etc. won't work with it either.
Regards
The only workaround that I found:
1. Create a new domain with proper multi-label FQDN.
2. Add it to SSO as authorization source.
3. Establish trust relationship between old and new domains.
Possible solution
Use vCenter Server 5.5.0a.
vCenter Server Appliance 5.5.0a still does not work with a SLD.
This issue is resolved in vCenter Server 5.5.0a. For more information about this version, see the VMware vCenter Server 5.5.0a Release Notes. You can download the latest vCenter Server release from the VMware Download Center.
Note: The issue still persists with the vCenter Server Appliance 5.5.0a. Do not use a Single Label Domain when deploying the vCenter Server Appliance 5.5.x.