Cannot add domain administrators view composer.

[WFHLD]

Hello,

For a VMware view trial I'm trying to add domain administrator accounts for the view composer, in the vmware view administrator on a single label domain, to no avail.

I know it is not best practice to use a single label domain but is it possible to get the vmware view composer working on this evil AD configuration?

I've already checked if I can ping the domain by its name, as suggested in an earlier thread.

This is working.

The logs come up with this errors:"

With Singlelabeldomain. (mention the dot) entered in the full domain name field it says: Bad user name or password

17:16:44,329 ERROR <TP-Processor2> VCBean Bad user name or password. com.vmware.vdi.admin.ui.VCBean.a(SourceFile:1002)

AxisFault

faultCode: {[http://schemas.xmlsoap.org/soap/envelope/]}Client

faultSubcode:

faultString: VMware.Sim.Fault.AdOperationErrorFault

faultActor:

faultNode:

faultDetail:

{[http://vmware.com/SviService]}AdOperationErrorFault:<AdConfigId i:nil="true"/><ErrorCode>-2147463168</ErrorCode>

With Singlelabeldomain (mention no dot) entered in the full domain name field it says: Bad domain

17:24:43,407 ERROR <TP-Processor3> VCBean Bad domain name. com.vmware.vdi.admin.ui.VCBean.a(SourceFile:1002)

AxisFault

faultCode: {[http://schemas.xmlsoap.org/soap/envelope/]}Client

faultSubcode:

faultString: VMware.Sim.Fault.AdHostsUnavailableFault

faultActor:

faultNode:

faultDetail:

{[http://vmware.com/SviService]}AdHostUnavailableFault:<AdConfigId i:nil="true"/>

Best regards, and thanks for your efforts,

Wietse

Message was edited by: WFHLD

Solved myself:

Weird behaviour of Microsoft IP stack.

Flushed dns resolver cache on VirtualCenter/Composer server, then ping singlelabeldomain. mention the dot.

Then ping singlelabeldomain without dot.

Then add domain admins in vmware view administrator.

Message was edited by: WFHLD

[admin]

For adding the administartor account the name resolution has to work properly. You need a connection between AD and View Composer / View Server which can be resolved via the FQDN

[AlbertFish]

This worked temporarily. But now it randomly has provisioning errors that say "Active Directory Server unavailable. Reflushing and pinging gets it started again temporarily but ultimately it dies.

Any ideas?

[ac57846]

I was tearing my hair out (luckily it's too short to get a grip on) with this one too.

It turns out it's a known issue. The solution is in although it doesn't mention that you need to restart the "VMware View Composer" service after making the change.

In case the KB article disappears here's the fix:

On the View Composer server, add the domain name to the domain controller's IP address mapping in the Windows hosts file: %WINDIR%\system32\drivers\etc\hosts. For example:

111.345.333.235 <domain name>

[srinivasaddagat]

even i had same issue, followed kb to add the domain entries and restarted the View Composer Service and it fixed the issue...

[Jerrylax]

followed KB link and steps mentioned in this post, the problem never solved.

we had vconnection server and V center & composer server all in the domain, we added entey in host file of the VC server, however, the

error message:"bad domain name" persist.

any suggestions?

thank you.

[Jerrylax]

thanks everyone. the problem has just been solved. its a DNS setting issue on VC server.