A couple months ago I made a post about customizing the cloud gateway.The real name for that product is Citrix Receiver for Web and is part of the StoreFront Express. Digging deeper in the Receiver for Web I found that it is really easy to modify the appearance of that site. You don’t have to change all the original files. Only just one.

Terry Duchastel has made a very clean and easy how-to about branding the site. I’ve borrowed some elements from that post and put it in this simple CSS He has made a couple of links in the logon page for helpdesk purpose. That part is skipped (because I don’t want to change the default html structure). The only thing with that type of branding, is that it will be gone when an upgrade is performed.  

Welcome back, in the previous post, we have configured the CAG and the StoreFront server to enable access to the internal XenApp/XenDesktop environment with a web browser. Now we are going to enable the environment to support internal and external access with the Self Service Plugin (Dazzle). First upgrade all receivers to the latest versions. Citrix Receiver 3.2 is necessary to get this working.

Logon to the admin panel on the CAG. Edit the logonpoint that we made in part3. Make changes so that the logonpoint looks like this:

(Click title to read more..)

When installing the Citrix Receiver you can give the following setup switch: ALLOWADDSTORE=A|N|S

• A = Always, allow adding and removing stores;
• N = Never, allow adding and removing stores;
• S = Secure (https) stores allowed.

When the client is already deployed the following registry key can be changed to change this behavior:

HKLM\SOFTWARE\Woe6432Node\Citrix\Dazzle\AllowAddStore

Welcome back, in this part I’m going to talk about the configuration between the CAG and StoreFront server. While I’m typing this blog there are some new releases. First off all the new version of the Receiver Storefront is v1.1. And there are new Citrix Receivers clients for OSX and Windows. All of my testing is done with the new versions. (As of April 2012)

I want to point out that this blog is how-to configure the StoreFront and the CAG (VPX) without the Self Service Plug-In (that blog comes later). What I’m going to show is how users connect to the environment with the help of a webbrowser (So only the Storefront StoreWeb site).

When creating a new vDisk, there is a question if you want the file to be dynamic or fixed. When choosing dynamic, the size of the VHD file would grow when demanding more space. Until the size has reached the size of the disk. In my environment I have a dynamic vDisk from 60GB. The VHD file size is 30GB. When deleting files from the vDisk this size doesn’t shrink.

In Part1 I was talking (euhh typing) about the Citrix Receiver and the Self Service Plugin. Today it’s time for the Merchandising server (I will type MS from now on). The MS is an virtual appliance which helps you deploy/update/configure/maintain the Citrix Receiver and plug-ins for Windows and OSX systems. As you can see in Part1 I want to place the MS in my LAN behind the CAG. But unfortunately this is not possible (well maybe it is but I can’t get it to work ) So there are some things you need before you can setup the MS.

Here’s a little blog post about the StoreFront Express (CloudGateway Express) behind a Citrix Access Gateway and the Merchandising server. What I want is to deliver the Self Service Plugin to the end users as easy/simple as possible.

In Part 1 I’m going to show you what the Citrix Receiver looks on Windows and OSX and how the Self Service Plugin looks. There are tiny bit’s about customizing the StoreFront.

Oké here is my lab environment: