Apr 1, 2016

TLS Handshake Failure The TLS Version Configured May Not Match The Version Used By The Server Error

Symptoms or Error:

Receiver for Android 3.8.1 error TLS handshake failure, the TLS version configured may not match the version used by the server. 

Since version 3.7 Citrix Receiver for Android supports the TLS 1.1 and TLS 1.2 protocols, those are configurable using the user interface. The default protocol used by Citrix Receiver for Android is TLS 1.0. If your Netscaler and StoreFront are configured to use TLS 1.1 and/or 1.2 it will throw the below error, screenshot provided.


Enable TLS version 1.0 on Netscaler and/or StoreFront. If TLS version 1.0 is not used on Netscaler or StoreFront then use the following method to change TLS versions from the Receiver for Andriod.

Method: Install Receiver for Android 3.6.3, add your store, then update to the latest Receiver from Play Store, and change Settings to your configured TLS version.

In Receiver for Android select “Settings”, “TLS Version”, and then select the version used in your environment.

Reference material:

Unable to Add First Store If Store Uses Non-defaultRfAnd TLS Protocol Setting

Feb 17, 2016

How To Fix Host to Client Redirection on Windows Server 2008 R2

In the users Default Programs > Associate a file type or protocol with a program > HTTP & HTTPS > change it to Citrix Metaframe Server FTA
pictured below.

Jan 8, 2016

Installing Citrix Director 7.7 on a Standalone Server

While working on a customer site and setting up XenDesktop 7.6 I was asked to install Citrix Director on several stand-alone servers. It was a large environment sensitive to Single
Points of Failure(SPF) and required separation of the Citrix service and multiple redundant systems and sites but I digress.

Sep 11, 2015

Creating a XenDesktop Grid Enabled VM in XenServer Using PVS XenDesktop Setup Wizard

In the video I show how to create a Grid enabled VM using PVS XenDesktop Setup Wizard in XenServer. System info: XD 7.6, PVS 7.6, XenServer 6.2. 

Jun 8, 2015

PVS Troubleshoot Process Communications: Changing PVS server IPs

When validating your store(s) in Provisioning Server it says "process communication" under "Status". In my case I setup 2 PVS 7.1.3 servers for a customer which wanted me to change the server IPs. This can present a problem if you only change the IPs in Windows. The Streaming Services still retain the old IPs and you will need to run the Provisioning Services Configurations Wizard to change it.

Here is a video on how I resolved it.