Storefront

image_pdfimage_print

NetScaler Responder für Storefront – Update

by

Im Artikel NetScaler Responder für Storefront habe ich darüber berichtet, wie man hinter einem Loadbalancer den Benutzer gleich auf die richtige Receiver for Web Seite weiterleiten kann. So wie es im Artikel beschrieben ist funktioniert dies wunderbar mit einem Browser, jedoch funktionieren die Accounting Services für den installierten Receiver nicht mehr.

Der Grund ist in der Expression der Responder Policy zu finden. Hier nochmals als Auffrischung die Policy vom genannten Artikel:

add responder policy Resp_Pol_to_SF-StoreWeb "HTTP.REQ.HOSTNAME.STARTSWITH(\"storefront\") && HTTP.REQ.URL.SET_TEXT_MODE(IGNORECASE).CONTAINS(\"StoreWeb\").NOT" Resp_Act_to_SF-StoreWeb

Wir müssen dieser nun noch einen Ausschluss für die installierten Receiver hinzufügen:

add responder policy Resp_Pol_to_SF-StoreWeb "HTTP.REQ.HEADER(\"User-Agent\").CONTAINS(\"CitrixReceiver\").NOT&&HTTP.REQ.HOSTNAME.STARTSWITH(\"storefront\") && HTTP.REQ.URL.SET_TEXT_MODE(IGNORECASE).CONTAINS(\"StoreWeb\").NOT" Resp_Act_to_SF-StoreWeb

So funktioniert es dann für den Browser und die installierten Receiver.

 

Skript: NS-RespStorefront

NetScaler Responder for Storefront

by

Hi Friends of NetScaler

In my last article “XML Services & Citrix Director together behind a NetScaler” I wrote about the possibility to use the same Loadbalancing (LB) vServer for XML Services and Director. But what if Storefront is installed on the same server, too?

Basically we use the same LB vServer descript in the last article again.

Add a new Host entry in your DNS server:
storefront.domain.pit = 192.168.100.30

Now we need an additional Responder policy, which
– checks the hostname (starts the hostname with storefront…?)
– checks if the URL contains not the value “StoreWeb” – indepent of case sensitive
– redirect to /Citrix/StoreWeb, if the conditions above matches:

 

add responder action Resp_Act_to_SF-StoreWeb redirect "\"/Citrix/StoreWeb\"" -responseStatusCode 302

add responder policy Resp_Pol_to_SF-StoreWeb "HTTP.REQ.HOSTNAME.STARTSWITH(\"storefront\") && HTTP.REQ.URL.SET_TEXT_MODE(IGNORECASE).CONTAINS(\"StoreWeb\").NOT" Resp_Act_to_Director

bind lb vserver lb-vsrv-PIT-XD-HTTPS -policyName Resp_Pol_to_SF-StoreWeb -priority 100 -gotoPriorityExpression END -type REQUEST

With this additional Responder Policy the next goal is reached.

 

Script: NS-RespStorefront

 

Storefront/Receiver: subscribe Apps for the User

by

Hi there

It should not be unknown anymore, but this article stay a long time in my drafts. In my courses I often be asked for a possibility to subscribe Apps for the user within Storefront.
This issue can be solved with some various ways:

“Magic” Keywords:

Since the start of Storefront can a feature called Keywords be used to modify the experience of Apps and Delivery Groups within Receiver/Receiver for Web. To subscribe apps for the user there’re following Keywords:

Keywords: Auto – the application is subscript for the user, but it can be removed

Keywords: Mandatory – the application is subscript for the user and cannot be removed

Keywords: Featured – the application will not be subscript, but it is shown with in the Featured Apps (Favourites) so it can be easy found.

XD-SF-Keywords
Two examples (Auto und Mandatory). Further more it is visible, that more than one Keyword can be used, separated by a space.

Disable User Subscription

Since Storefront 2.6 you can disable this User Subscription completely. After this the experience is like the good old times of Webinterface – the user can directly work with all application to which he has access.

XD-SF-DisableUserSubscriptions

Personally I would prefer the use of Keywords. An IT department can be sure, that the relevant (Business-)applications are directly available for the user. Rare used apps can be subscript by the user on demand.

Weitere Informationen: http://support.citrix.com/proddocs/topic/receiver-windows-42/receiver-windows-configure-app-delivery-wrapper.html

—–

ab Storefront 2.x

Storefront without Desktop/Apps Tabs

by

Hello Citrix World

Nobody knows today when it was, but Citrix introduced the Tabs (Desktop, Applications, Content) in Webinterface. There were possibilities to control this experience within the console of Webinterface to change the order of the Tabs or remove it.

In Storefront, the Tabs (Desktops, Apps) are by Design and cannot be changed within the Storefront console. If you want that all published resources are shown together you need to insert following in the description field of the Delivery Group: KEYWORDS: TreatAsApp

After that, the Tabs are removed and published Apps and Desktops are shown on the same page.

Weitere Informationen: http://support.citrix.com/proddocs/topic/dws-storefront-21/dws-plan-optimize-ux.html

—

Citrix Storefront 2.x