vCenter Appliance joined to domain, but no domain available

[yannara]

I´ve setup vCenter Appliance 5.1 and I joined it to my AD domain, but when I try to create permissions and and link them to AD group, I can´t see my domain:

  

Any idea, why this is happening?

[a_p_]

I saw this issue twice and in both cases it worked for me join the AD domain with the username in the "[e-mail]" format followed by a reboot of the appliance.

André

[yannara]

André Pett wrote:

I saw this issue twice and in both cases it worked for me join the AD domain with the username in the "[e-mail]" format followed by a reboot of the appliance.

André

Thanks, I´ll try. Does it matter, will I do it in a web management page, or in a linux console?

[yannara]

André Pett wrote:

I saw this issue twice and in both cases it worked for me join the AD domain with the username in the "[e-mail]" format followed by a reboot of the appliance.

André

Unfortunately no, in my case if I set it like you purposed, I will get "Error: Invalid Active Directory domain."

I also tried re-join vcenter to domain few times, but end result is the same.

[a_p_]

Error: Invalid Active Directory domain

Can you please double check the DNS server settings in the appliance are correct?

André

[yannara]

André Pett wrote:

Error: Invalid Active Directory domain

Can you please double check the DNS server settings in the appliance are correct?

André

They are. I also can join vcenter to domain by entering "contonso.dom" and separate credentials, but using [e-mail] will fail with the invalid domain.

So, any other ideas what to do?

[yannara]

vmstoani has been reported as spam.

[RvdNieuwendijk]

I deleted the out-of-office reply by vmstoani.

[yannara]

Why in earth Out-of-Office replies appears to this forum? :smileyconfused:

[a_p_]

Unfortunately this is due to the option to reply to posts by email. If users - who use their work email addresses - forget to exclude the forums from the OOO messages this can happen.

I deleted the message though.

André

[V_Peter_S]

We have seen this issue and found that, provided your virtual center server is connected to the doamin, that a re-boot of the virtual center server appliance has resolved this.

We are a VMware Reginal Academy: www.cccti.edu/vmware, and had this show up when using the 5.1.0/5.1.0b versions.

One other issue we have found also is that the virtual center server appliance will not maintain the FQDN without performain a re-boot.

Hope this helps.

[djlightbulb]

As a reboot is necessary, it's a given that this has been done, in some cases MANY times....

[JmLeal]

Hello,
I have the same problem, I tried sysprep, I tried re-boot and niningun result. I keep trying and if I find the public solution here.
regards