I'm thinking that it might have to do with that we moved the default location of the certificate.
Does the broker-service start at all? If not then its probably the certificate...
From the release-notes: VMware Horizon View Release Notes
"The PCoIP Secure Gateway (PSG) service identifies the SSL certificate to use by means of a server name and certificate Friendly name. You set the Friendly name value in the Windows registry on the View Connection Server or security server computer on which the PSG service is running. When the PSG service finds a certificate that has a Friendly name that matches the Friendly name value in the Windows registry, it uses that certificate only after the certificate passes a series of tests. In addition, all of the certificates in the trust chain must be installed in the Windows local computer certificate store.
The following problems related to this functionality have been resolved in this release:
- Previously, setting the Friendly name value in the Windows registry to a substring of the certificate Friendly name could cause the PSG service to select the wrong certificate. For example, a Windows registry value of "Fred" could result in the selection of a certificate that had a Friendly name of "Frederick" instead of "Fred." Now, the PSG service makes an exact case-sensitive selection of the Friendly name.
- Previously, all certificates had to be in the Personal certificates store on the Windows local computer. Now, the PSG service looks for the root certificate in the Trusted Root Certification Authorities store. Important: If you resolved this problem in a previous release by moving the root certificate to the Personal store, the intended certificate will no longer be selected after you upgrade to 5.3. You must move or copy the certificate back to the Trusted Root Certification Authorities store."
// Linjo