Archive

Posts Tagged ‘RfW’

Bug in Citrix Receiver 13 for Linux – cannot connect with multiple STAs – @CitrixSupport, @CitrixReceiver, #Citrix

Ok, we’ve had some issues with Citrix Receiver version 13 for Linux.. and it’s not just ONE issue. I found one that I thought I just have to share… so it’s lab Saturday for me at the office in a true geek manner with two XenClients and my favourite MacBook!

Bugg_finding_geek_Saturday

I guess that some of you have tried the Linux Receiver and knows how hard it is to get working, especially on a 64-bit distribution of Linux like Ubuntu 12.04 LTS och 13.10 LTS.

If you follow these instructions you can get it onto the device and then login through a browser (local Receiver UI may still not be full functioning!)..

https://help.ubuntu.com/community/CitrixICAClientHowTo

What I’m about to show you is that it’s not just only getting Receiver on the device and ensuring that the SSL certificates are trusted. You then have to be able to use it as well externally through a NetScaler Gateway (NSG) into StoreFront and your XenApp/XenDesktop VDA’s.

Just assume that you have a production environment that consists of a NetScaler Gateway and a StoreFront server, if you then in StoreFront have configured your NetScaler Gateway correctly and the appropriate STA configuration (with MULTIPLE STA’s) then you will notice that you can’t launch a session.

BTW, the recommendation from Citrix is to use multiple STA’s, right! See this from edocs:

For all deployments, if you are making resources provided by XenDesktop, XenApp, or VDI-in-a-Box available in the store, list on the Secure Ticket Authority (STA) page URLs for servers running the STA. Add URLs for multiple STAs to enable fault tolerance, listing the servers in order of priority to set the failover sequence. If you configured a grid-wide virtual IP address for your VDI-in-a-Box deployment, you need only specify this address to enable fault tolerance.

Important: VDI-in-a-Box STA URLs must be entered in the form https://serveraddress/dt/sta in the Add Secure Ticket Authority URL dialog box, where serveraddress is the FQDN or IP address of the VDI-in-a-Box server, or the grid-wide virtual IP address.

The STA is hosted on XenDesktop, XenApp, and VDI-in-a-Box servers and issues session tickets in response to connection requests. These session tickets form the basis of authentication and authorization for access to XenDesktop, XenApp, and VDI-in-a-Box resources.

If you want XenDesktop, XenApp, and VDI-in-a-Box to keep disconnected sessions open while Citrix Receiver attempts to reconnect automatically, select theEnable session reliability check box. If you configured multiple STAs and want to ensure that session reliability is always available, select the Request tickets from two STAs, where available check box. Read more…

#XenMobile on Android and MicroVPN issue unless you really synch Worx releases…

February 26, 2014 Leave a comment

Hi,

If you’ve worked with XenMobile and especially the AppController to deploy WorxMail and WorxWeb you know that these establish  a MicroVPN tunnel to reach internal resources when needed.

One thing that I noted today was that when you upgrade your AppController and NetScalers and people also upgrade their Worx Home app on Android you can run into an issue unless you upgrade and align your Worx Home and WorxWeb apps.

The new Worx Home 8.6.1 on Android requires that you run WorxWeb 1.3.3 from Citrix, otherwise the MicroVPN tunnel won’t be established and you won’t reach your internal resources through it.

So it’s more important than ever to ensure that you try your NetScaler, AppController and Worx apps and align their releases.. once they work then you see this great progress and tunnel being established.

Android_MicroVPN_tunnel_established

It would be nice to get a good table of which versions of each product/component that you should run and which ones that can support all use cases like; XenMobile , ShareFile on prem, ICA/HDX proxy, SSL VPN and SmartAccess for RfW and proxy! I’ve not yet found one combination that delivers everything. 😉

Happy XenMobile’ing!

//Richard

How to: #Citrix #XenMobile 8.5 MAM upgrade! Part 2 – #StoreFront, #AppController, #NetScaler

September 9, 2013 1 comment

Hi again!

If you haven’t read Part 1 then I highly recommend doing so prior to going directly to the upgrade that we’re covering in this post!

Prepare for a journey in this post about Citrix StoreFront upgrade, uninstallation, console and how messy it could be! NOT all the time, sometimes it “just works”! 😉

My little NetScaler is already upgraded to 10.1 so unfortunately I couldn’t take you on that journey as well, so we’ll start with the StoreFront upgrade from 1.2 to 2.0 in this post. These are the steps that we need to cover as highlighted in the migration guide that seems very short and straight forward:

Upgrade StoreFront 1.2 to 2.0.

  1. Logon to the StoreFront server console.
  2. Upgrade StoreFront by running the StoreFront 2.0 installer as an administrator.
  3. When the upgrade is completed, open StoreFront administration snap-in, remove CloudGateway controller from each store as this will be moved in the migration solution.
  4. Open NetScaler Gateway Properties and for each gateway defined and change the version field in settings from 9.x to 10.0.x or later.
  5. Test the configuration by logging on through web browser or Citrix Receiver.
  6. Verify if the users are able to login and authenticate to StoreFront defined stores configured.

Is it this easy?

Ok, I’ve downloaded the 2.0 installer, and I’m logged on to the server.

Before we even start the upgrade there are things that could go wrong in removal or upgrades of StoreFront. And one that I’ve seen cause a lot of headache for a lot of people out there is that they have the Windows Firewall service disabled. Though the installation and removal wants to delete or add these rules the installation will fail unless this service is running. As you can see in this picture below you see the FW rule added in StoreFront 1.2:

Windows_FW_Rules_SF1

So let’s verify that the Windows FW service is started, and it is!

Windows_FW_SVC_started

I’ll now start the installation by double-clicking the StoreFront 2.0 installer!

StoreFront_2_0_Installer

What is this popup that came directly after starting the installer?

Receiver_HTML5_popup_installation

Wait, ok so you guys at Citrix couldn’t ask me whether you could do this for me? My plan is to upgrade, so please just add a little step in your upgrade program that does this for me… change request #1 for the next SF release and it’s upgrade process! Verify pre-requisites or deal with them!

Read more…

LIMITED RELEASE – #Receiver #Storefront 1.2 Update 1 for Web Receiver Add-in

Issue(s) Fixed in This Release

  1. After enabling the requireTokenConsistency parameter in StoreFront’s store configuration file (c:\inetpub\wwwroot\Citrix\<StoreName>\Web.config) as described in Knowledge Center article CTX134965, users might not be able to access resources when logging in through Access Gateway.
  2. Attempts to authenticate to the Receiver for Web fail for users whose passwords contain certain special characters.

Continue reading and download it here!

//Richard

%d bloggers like this: