Last week I had the task to update our VMware View environment from 7.0 to 7.11, a sizeable dot release upgrade. 7.11 was released in December 2019. This included the upgrade of Connection Server, Security Servers, Composer and the View Agent installed on desktop pools.<\/p>\n
The issue I run into was post upgrade. The View Connection Server could not validate the certificate from View Composer. Composer is installed side by side with the Windows version of VCenter (in the VCSA deployment of VCenter composer is standalone). Upon logging into VCS and clicking on the View Composer status, you get a message box with “There was an error indentifying the validity of the server”. When you try to accept the thumbprint like in past versions you get another error message saying that the certificate is unable to be read at this time.<\/p>\n
This issue is related to how the View Composer installer works. The newer installer will replace the existing View Composer certificate with a newly generated certificate with the FQDN of the host you have it installed on. So if my View Composer cert CN was SERVER01 before upgrading, the installer will replace it with SERVER01.company.com (the fqdn of the server). This means that VCS cant connect to the composer because the server name in the VCS ldap database does not match the new CN of the newly generated cert.<\/p>\n
I spent about an hour or so trying to find this fix, which has been blogged about across the web a fair bit. I also tried to re-enable TLS 1.0 within View Composer which with the newer version you cannot do because the registry key is locked down (you get a permissions access denied error message).<\/p>\n
So heres how to fix the issue:<\/strong> The composer cert will have the NETBIOS name of the VCenter Server instead of the FQDN. Such has https:\/\/SERVER01:18443<\/p>\n Update the ldap attribute for the View Composer host URL:<\/strong> I hope this helps anyone else who has ran into this issue. Some other links about this issue are here<\/a> and here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" Last week I had the task to update our VMware View environment from 7.0 to 7.11, a sizeable dot release upgrade. 7.11 was released in…<\/p>\n","protected":false},"author":2,"featured_media":525,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17],"tags":[72,111,177,194,198],"class_list":["post-517","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware","tag-composer","tag-horizon","tag-tls","tag-view","tag-vmware"],"acf":[],"yoast_head":"\n
\nBefore making any changes make sure you have a valid backup of your View environment.<\/em>
\nFirst off find the name of the existing composer cert in the View LDAP databse:
\n1. Stop the Composer service.
\n2. Open CMD and change directory to the Composer installation directory.
\n3. sviconfig -operation=ReplaceCertificate -delete=false
\n4. Press 0 to abort.<\/p>\n
\n1. On the View Connection Server, Start -> run -> adsiedit.msc
\n2. In the connection settings:
\n Name: anything you want.
\n Connection Point: dc=vdi,dc=vmware,dc=int
\n Computer: localhost:389
\n Press Ok.
\n3. Expand the directory
\n4. Expand OU=Properties then the OU=VirtualCenter
\n5 Right-click on chose properties on the object within VirtualCenter
\n6 Locate an attribute pae-SVIURL edit this attribute and put the name found when viewing the Composer certificate. (In this example it would be https:\/\/server01.company.com:18443)
\n7. Click ok and exit ADSIEdit.
\n8. Co to the Connection Server and refresh, you\u2019ll notice the Composer value has changed to that which we have modified and you\u2019ll be able to validate the certificate normally.<\/p>\n