Connecting the Citrix Receiver 3.1/3.2 client to non HTTPS Services Sites (PNAgent)
June 28, 2012 1 Comment
For you fellas that are always playing around with the latest Citrix Clients (there is actually a reason for all these different versions), you will realize that if you install 3.1 or 3.2 and attempt to utilize your XenApp Services Sites, it will only allow for HTTPS addresses. To some yes, just add an SSL cert on your WI boxes, to others, the process is a little more complicated than that due to Change Management procedures, budget, etc.
Solution:
Reconfigure your client to allow HTTP traffic via the registry.
You can not do this in the GUI, but you can hack it via the citrixadm (haven’t tried it) or the registry (Please note I am not voting for non HTTPS traffic)
- Open Regedit
- Go to HKLM\SOFTWARE\Citrix\AuthManager on a 32-bit machine or HKLM\SOFTWARE\Wow6432Node\Citrix\AuthManager on a 64-bit machine
- Under AuthManager create a new String Value (Reg_SZ) with the name ConnectionSecurityMode with the Any value as displayed below
- Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Dazzle (Funny they still call it Dazzle in the registry) on a 32-bit machine or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle on a 64-bit machine
- Under Dazzle AllowAddStore to A as showed below
No lets do an HTTP connection 😛
In XenDesktop 5 Citrix has modified how they use Citrix Provisioning Server. First of all you no legnor need to install Citrix Provisioning Server if you are deploying hosted virtual desktops. This is incorrect for two reasons:1. You didn’t need’ PVS to deploy hosted virtual deskotps in XD 4. HVD could be spun up with just the broker and VDAs.2. PVS can’ be used for HVD in XD5. It depends on the Machine Type. Pooled leverages Machine Creation Services, Streamed leverages PVS. Both of which can be used for hosted virtual desktops.