Import vCenter server certificate on the Xendesktop 7.6

Import vCenter server certificate on the Xendesktop 7.6

I was trying to integrate a vcenter server to a Xendesktop 7.6 environment.
And received the "Cannot connect to the vCenter server due to a certificate error" message.


After a quick google it seemed this issue could be resolved quickly by copying the certificate from the vcenter server to the delivery controller, or import the certificate by browsing to your vcenter web client and import the certificate from there.

Well first I tried to download the cert from the vcenter server by connecting filezilla to the vcenter server (see my previous post). Downloading was succefull, importing the certificate to the Trusted Root Certification Authorities store succeeded also, but the error remained.

Then I opened up the Internet explorer, browsed to the vSphere webclient page and looked at the certificate.

The CA Root Certificate was not trusted because it wasn't in the trusted Root Certification Authorities store. I clicked on View Certificate.


And installed the CA root certificate by clicking Install certificate.
That did the trick!

Connect Filezilla to vCenter Server

Connect Filezilla to vCenter Server

I needed to connect to my vCenter server to get the certificates that are installed for use on my Xendesktop 7.6  farm. I have established the connection by using Filezilla.

Open Filezila
Click on File, Site Manager

Click on new Site

Give your new site a name, for example Vcenter
Add the host name of your vcenter server or ip address
Protocol: SFTP-SSH File Transfer Protocol
Logon Type: Ask for password
User: Root

Click on connect. If your connection fails and you have checked your password then open an webbroser and browse to your VMware vCenter Server Appliance. For example https://vcenter.yourdomain.local:5480

Login to the server

Enable Administrator SSH Login enabled

Thinapp - Application crashes after launch, added Workingdirectory= to package.ini

I had to Thinapp an simple application. I just had to copy the application executable and a couple of configuration files to the "c:\program files\MyApplicationDirectory"  folder.
The application could be started by double clicking the executable. I captured these steps, and build the Thinapp.

Next step, start the thinapp and inform the user that the application was ready for use. Done? Wrong!
The application crashed as soon as the thinapp was started.

I opened the cmd.exe entrypoint browsed to the application directory, run the executable and it worked!? So what this application was missing was an working directory setting. I edited the package.ini by adding the WorkingDirectory= line:

[MyApplication.exe]
Source=%ProgramFilesDir%\MyApplicationDirectory\MyApplication.exe
WorkingDirectory=%ProgramFilesDir%\MyApplicationDirectory

And it worked!

Thinapp - Locked Sandbox

Do you want to rebuild your thinapp or do you want to delete your Thinapp sandbox, but you get an error that the folder or file is in use?

The tool that I use frequently for troubleshooting is the part of the great Sysinternals suite and is called Process Explorer. Process Explorer gives you an detailed view of processes running on your system.
You can download sysinternals process Explorer here link



Start the process explorer application, click on Find, Find Handle or Dll.
Search for .rw, these are the Thinapp virtual registry files, and/or search for the application executable name.



Kill the process(es) that keeps your thinapp locked.
Now you should be able to delete your sandbox or rebuild your Thinapp.