Using HTTP for StoreFront Server

In some recent lab testing I setup Citrix StoreFront to use HTTP as I was running some quick tests and didn’t need HTTPS for my test.

Unfortunely, by default, the Citrix Receiver only allows you to connect via HTTPS. If you enter an HTTP URL, it won’t allow you to save it and instead, get the following error:

“The specified server address is not secure”

StoreFront1

Once you click, “Add”, you will get the following:

“HTTP Store requires additional configuration before being added to the Citrix Receiver. Please contact your system administrator.”

StoreFront3

The fix for this is to edit/add the following Registry keys on the client your using the Citrix Receiver to connect from:

  1. Set HKLM\Software\[Wow6432Node\]Citrix\Dazzle\AllowAddStore to A to allow users to add non-secure stores.
  2. (Optional) Set HKLM\Software\[Wow6432Node\]Citrix\Dazzle\AllowSavePwd to A to allow users to save their passwords for non-secure stores.
  3. To enable the addition of a store that is configured in StoreFront with a TransportType of HTTP, add to HKLM\Software\[Wow6432Node\]Citrix\AuthManager the value ConnectionSecurityMode (REG_SZ type) and set it to Any.
  4. Exit and restart Citrix Receiver.

Source: Configure and install Receiver for Windows using command-line parameters

You should now be able to use an HTTP URL in your Citrix Receiver to connect to StoreFront successfully!

Hope this helps someone else down the road!

@chris_messer ~~> Subscribe to blog to get latest updates <~~

NVIDIA Releases Updates to NVIDIA GRID GPU line!

Today, NVIDIA announced some updates to the  line of NVIDIA GRID GPU’s for VDI. I continue to see the use cases increase for GPU’s in VDI so great to see these new releases. The increase in user density is one of the key considerations customers always ask; how many users per server/GPU? Great to see the users density continue to increase!

Here are some details from todays launch webinar and my key takeaways;

  • renamed vWorkstation license version to Quadro Virtual Data Center Workstation Software (Quadro vDWS)
  • newer P40 & P6 GPU’s do NOT have 512MB profile (min is 1Gb)
  • a new license server will be released; 5.0
  • 50% more vGPU per physical GPU (improves density!)
  • updated/newer monitoring and insight integration into VMware vRealize Operations and 3rd party’s, i.e. Liquidware Labs, Lakeside, ControlUp, eGInnovations, etc..

Updated NVIDIA GRID line:

You can see press release here.

Wyse ThinOS Fails to Auto Create Printer when using Citrix Universal Print Driver

Issue:

Wyse ThinOS fails to auto-create local/USB printers using the Citrix Universal Print Driver when connecting to XenApp 7.8 on Windows Server 2008 or 2012 servers.

The issue occurs if the local Wyse ThinOS printer “identification” field is set to use the “PCL5” driver which ThinOS is set to use by default. On Windows Server 2008 R2 and 2012 servers running Citrix XenApp 7.8, and other versions, they do not have the specific PCL5 driver, “HP Color LaserJet 4500 PCL 5”, installed by default. This specific HP driver is the PCL5 driver that the Citrix Universal Print driver uses and is not installed by defaults so it needs to be manually installed.

Resolution:

The required Windows PCL5 driver that the Citrix UPD leverages, “HP Color LaserJet 4500 PCL 5”, needs to be manually installed on the Windows Server 2008 or 2012 servers. Citrix identifies this issue in the following CTX article:

CTX140208 – Non-Windows Clients may not Autocreate Printers on Windows Server 2012 using the Citrix UPD

“As non-windows clients do not support EMF or XPS drivers, they will attempt to use PS or PCL drivers. In Windows Server 2008 R2 or Windows Server 2012, PCL5c, PCL4, and PS drivers may not be installed by default. To install them, launch the Print Server Properties window and click Windows Driver Update.”

The default Citrix UPD drivers are the following and the PCL5c is the one generally missing:

PS driver HP Color LaserJet 2800 Series PS
PCL4 driver HP LaserJet Series II
PCL5c driver HP Color LaserJet 4500 PCL 5

Details:

By default, the server does not have the “HP Color LaserJet 4500 PCL 5” installed as shown under print server properties. As shown in the registry, the Citrix UPD uses this driver to map the PCL5c driver and since its missing, auto creation from ThinOS fails.


By default, Wyse ThinOS is set to use a PCL5 driver under “Printer Identification” field so when the printer is auto created it attempts to map to the PCL5 driver on the server which is missing so auto creation fails.


By default, the Citrix UPD is set to “Use universal printing only if requested driver is unavailable” and the UPD driver preference order is set to; EMF;XMS;PCL5c;PCL4;PS.

As noted above, “non-windows clients do not support EMF or XPS” so the first driver it attempts to use is PCL5c which is not installed by default so auto creation from Wyse ThinOS PCL5 fails. If Wyse ThinOS “Printer Identification” was set to use PCL4 or PS then auto creation would succeed as those 2 drivers are installed by default.


This issue and resolution is also documented in the following PDF Technote – Wyse ThinOS and Citrix UPD Fails to Autocreate Printers.

Citrix and Skype for Business on Wyse ThinOS

One of the great new features in the release of Skype for Business on Citrix XenDesktop is the ability to use a non-Windows, Wyse ThinOS, endpoint as the client device to support new Skype features. Previously, you were limited to using a Windows endpoint running a full Windows PC or Windows Embedded thin client.

More importantly, your able to leverage the power of the Citrix Real Time Media Engine (RTME) which is embedded in the Wyse ThinOS for audio/video offload. This allows the client to offload rendering from the server VM onto the client leveraging the client CPU/memory to process audio/video. This freeing of VM resources allow greater server/desktop density and better performance as local client resources are also being used.

The key benefit of leveraging the RTME support is you eliminate the traditional VDI hair-pinning of the unified communications audio/video traffic which would route all the audio/video traffic through the virtual machines as illustrated below.

This is very well illustrated in below video.

Site feedback? chris@vditoolbox.com | Twitter | LinkedIn