RG04A – Integrating Citrix XA6.5 Prelaunch with WM

By Lasse T. Homann

 

Recently I’ve been looking at how to get RES Workspace Manager working with Session Prelaunch in XenApp 6.5. As I was unable to find anything specific on the topic, I had to roll up my sleeves and figure it out for myself:

A bit of background information: XenApp 6.5 offers the Session Prelaunch feature, which basically initiates a silent connection to the XenApp server, the moment that you log on to your local desktop. For the end-user this means lightning fast access to published applications. You can read more about it on the Citrix blog here. To get started, you need to configure a RES Managed application on the XenApp environment, so fire up the RES console on one of the XenApp boxes where you’ve installed the full product. Remember, you must have the Advanced Administration module enabled, either in eval mode or fully licensed for Citrix integration to be enabled in WM.

Create a new app for the executable C:\Program Files (x86)\Citrix\system32\CtxPreLaunch.exe like show below. In my example, the managed app is named RES WSM PreLaunch.

rg04a-pic1

rg04a-pic2Be sure to uncheck “Create Start Menu shortcut” as we don’t want users to be firing up this app themselves. Now go to the Properties|Publishing tab of the app and ensure that it’s being published to XenApp. This may take a moment or two. Once this is done, go to your XenApp AppCenter console and find the newly created published application.

Rightclick on the published app, then chose Other Tasks and select Create pre-launched application. This will create a new separate published app with the prefix PreLaunch, thus the full name of the new published app will be “PreLaunch RES WSM PreLaunch”.

Next, copy the command line from the RES-created published app (the one you did first):

rg04a-pic4

And paste it into the Prelaunch published app, created by the Citrix AppCenter console:

 rg04a-pic3

You now have a prelaunced application, which initially launches the RES Workspace Manager, which in turn launches the ctxprelaunch.exe executable. The session will now be able to rapidly launch additional apps. At this point you may consider adding the server(s) to worker groups if necessary.

Editor’s note: In addition to the above, in order to obtain a completely silent launch of the RES managed app, you may want to consider disabling the splash screens in RES Workspace Manager. In order to do so, go to Composition|Desktop|Lockdown & Behavior and type the word ‘splash’ in the instant search field:
 nosplash

Also, be advised that if you hide the main splash screen, this will affect every agent connected to this RES datastore, and you cannot make exceptions with workspace containers either.

 

3 Comments

  • By Brian Skovgren Klausen, February 6, 2013 @ 01:12

    Regarding the splash and the fact that it disables all splash screens, it’s my experience that TS/RDS does not adhere to that setting in Lockdown and Behaviour.
    However, there is a reg key to disable it on an pr. machine basis – obviously this can be deployed through AM :).

  • By RESguru, February 6, 2013 @ 01:19

    Hi Brian, this is interesting. If this is something which you can consistently replicate, I’m quite sure our software engineers would like to see that. Am I to understand that RES WM splash screens are still shown on RDS even though they have been disabled under Lockdown&Behavior?

  • By Brian Skovgren Klausen, February 7, 2013 @ 07:38

    Hi Max. Yeah as far as I remember. I actually worked with Lasse on this particular project (as an external consultant), and as far as I remember we did have this issue.
    Either that, or we just didn’t want to disable the splash globally, but only for our XenApp application servers. The more I think about it, I think it was the last reason actually :-).

Other Links to this Post

RSS feed for comments on this post. TrackBack URI

Leave a comment

You must be logged in to post a comment.