VMware Horizon Community
jrVMguy
Contributor
Contributor
Jump to solution

View Composer Issue

I am looking for some help with an issue that we are running into with View Composer. At the end of this post is a blurb from the bottom of page 108 on the view administration guide.

Our domain is not fully qualified (we do not control the domain and have limited management ability) and we are unable to enter the information in the View Composer Settings screen. We have tried a couple different ways to enter the domain name (IP and the name we see) and we get back that it is a bad domain name every time.

I have checked the posts here looking for someone that may have had this issue in the past but I didn't find anything.

Has anyone run across this before and have any insight for me regarding this issue ?

Our environment:

IBM HS20 blades (3) with Intel processors
ESX 3.5 u4
Virtual Center 2.5 u4
View 3.0.1-142034
composer 1.0.0-126338
View Connection server 3.0.1-142034

Deploying Linked Clone Desktops from View Manager

View Manager can only deploy linked clone desktops if it is able to communicate with a properly configured VirtualCenter host that is running the View Composer service.

In addition, your Active Directory forest must have a fully qualified domain name, for example, example.com-you cannot use View Composer in environments where the domain controller has an unqualified name.

Tags (3)
Reply
0 Kudos
1 Solution

Accepted Solutions
jklimczak1
Enthusiast
Enthusiast
Jump to solution

Yes after I upgraded to 3.1 that fixed the issue....

View solution in original post

Reply
0 Kudos
5 Replies
jklimczak1
Enthusiast
Enthusiast
Jump to solution

I had the same issue.... I installed 3.0.1 updated to 3.1 and that helped. You can try to uninstall composer.. Make sure your dns is also right

Reply
0 Kudos
jrVMguy
Contributor
Contributor
Jump to solution

DNS is working correctly as I can get to the server by name or IP.

Did upgrading to 3.1 fix the problem ? Like I said in the original

post, we have very limited abilities in our domain.

If the upgrade fixes the issue I would give it a try but I don't want to

introduce a "secondary issue" into the mix at this time.

We are able to deploy VMs from a template with no problems and they work

great so far, but we want to try linked clones and this part of the

setup is stopping us.

Reply
0 Kudos
jklimczak1
Enthusiast
Enthusiast
Jump to solution

Yes after I upgraded to 3.1 that fixed the issue....

Reply
0 Kudos
jrVMguy
Contributor
Contributor
Jump to solution

I am downloading the 3.1 version now and will give that a try.

Reply
0 Kudos
jrVMguy
Contributor
Contributor
Jump to solution

The upgrade to the 3.1 version of View (composer, connection server, agent) fixed the issue for me.

Thank you very much !

Reply
0 Kudos