vSphere 5 withoud AD

[rct]

Hello !

We have a vCenter 5 Appliance (Suse 11) configured without Active Directory (we don't have one) and it seems that Veeam Monitor is unable to login the vCenter in this situation.

Is there a way to register our vCenter anyway ?

Thx

[Vitaliy S.]

Hello,

Hmm...that's interesting. Have you tried adding vCenter Server via HOSTNAME\USER_NAME? For the hostname please specify vCenter Server machine name.

Thanks.

[rct]

Hello,

Yes my machine is named vcenter01.XXXXXXXX.com
I've tried to specify "vcenter01\root" but it doesn't work. In my vCenter appliance I tried to rename the server from "vcenter01.XXXXXXXX.com" to "vcenter01". Wasn't better.
Does someone has this behaviour with vCenter 5 appliance without AD ?

Thx for the answer, i'm interested in any feedback.

[Vitaliy S.]

I have passed this information to our R&D team, we'll investigate what can be done here and I will post it back.

By the way, out of curiosity how large is your infrastructure (hosts/VMs)?

[warix]

Hello

Sorry for my post but I'm not this problem

So what is your error message

For me I introduce my vcenter name in thé host file of my veeam sever and veeam name in host of my vcenter

And try with up adress

[rct]

I have passed this information to our R&D team, we'll investigate what can be done here and I will post it back.

By the way, out of curiosity how large is your infrastructure (hosts/VMs)?

Our vCenter 5 infrastructure is 3 hosts and 30 VMs.
Thx for the answer.

Hello

Sorry for my post but I'm not this problem

So what is your error message

For me I introduce my vcenter name in thé host file of my veeam sever and veeam name in host of my vcenter

And try with up adress

It seems that your configuration don't work for me. My DNS servers are configured on both Veeam server and vCenter server so I don't think it would resolve this problem
Thx anyway.

The error message in Veeam is : "Cannot complete login due to an incorrect user name or password."
In the vCenter /var/log/messages I see another error that I think is related : "vcenter01 vpxd: pam_tally(vmware-authd:auth): pam_get_uid; no such user"

[Vitaliy S.]

Rct, we'll have a hotfix addressing this issue next week. I will update this topic once it is available. Thanks for the heads up!

[rct]

Nice !

Thx

[Vitaliy S.]

The hotfix which allows adding vCenter Server appliance without AD integration enabled is now available through our support team. Thanks!

[rct]

Thx to you !

[tcoskun]

I installed veeam monitor v 5.0.0.261, still get the same error! will there be another update for this?

[Vitaly.Mzokov]

Turgut,

Please contact our support team to get the hotfix file. Thanks.

[Vitaliy S.]

Turgut, it doesn't look like you've applied the latest hotfix which is available solely from our support team. The version you've downloaded from our website doesn't fix this problem. Thanks!

[tcoskun]

I installed the latest hotfix and the problem is solved, thanks for help.

[smile_dav]

[merged]

Hi,

I have just migrated from our Windows based vCenter to the vSphere v5 vCenter appliance, however, I couldn't add my vCenter to Veeam Monitor: when I enter the username field cannot recognize HOSTNAME\USERNAME or USERNAME. Apart from adding each ESXi host separately, are there any solutions to this?

[satheesh]

[merged]

Hi. I'm trying to add the VMware vCenter Server Appliance 5.x to the Veeam Monitor for VMware Free Edition without any success. Because the appliance isn't a normal Windows computer, nor domain joined, it just give me error when adding the username and password:

Specify username in the DOMAIN\Username format.

I tried using .\root, localhost\root, dnsname\root - but still the same error. Any thoughts?

[Vitaly.Mzokov]

Hi Satheesh,

Looks like you've ran into a known issue while using vCenter server without AD integration. Please take a look at this KB to solve your problem - http://www.veeam.com/KB1320.
Hope it helps.

VM.

[satheesh]

Hi Satheesh,

Looks like you've ran into a known issue while using vCenter server without AD integration. Please take a look at this KB to solve your problem - http://www.veeam.com/KB1320.
Hope it helps.

VM.

That worked like a charm Vitaliy - thanks!