AutoLaunch in XenApp 5.x Web Interface
Web Interface 5.x has an build-in autolaunch feature that automatically starts Desktops. You can enable this function within the webinterface.conf. Add the line AutoLaunchDesktop=On somewhere in the Webinterface.conf and for users who have only a published desktop, the published desktop wil start automaticly.
This is good but what about where I have published apps I want to have accessible within the desktop I want to launch, if I have streamed or published apps in addition to a desktop then I can’t autolaunch the desktop. Interestingly XENDesktop ignores these other apps and still autolaunches the VIrtual Desktop.
How do I make XENApp behave like XENDesktop, Have it autolaunch the desktop and allow me to see the published or streamed apps via my Xenapp plugin without this stopping the desktop launching
A challenge
Thanks – DJ
Hi David,
I don’t know if you ever heard of RES Powerfuse. RES Powerfuse is a workspace management tool that could make this happen for you. Just have a look at http://www.ressoftware.com.
Great feature…. unfortunately if you are using Silo’s or have more then one published application this isn’t working.
Then what????
Even if there is an application called Desktop it’s not working.
So it’s back to WI 4.5 for this customer.
Hi Jon,
it’s possible to customize the WI 5.x site to autlolaunch ‘any’ app – not only a published desktop.
1. Make sure the user only have one application published
2. Edit \wwwroot\Citrix\XenApp\conf\Webinterface.conf to include AutoLaunchDesktop=On
3. Modify \wwwroot\Citrix\XenApp\app_code\PagesJava\com\citrix\wi\pages\site\AppList.java
to exclude the check for ‘is this a desktop’, almost in the end of the file, starting with header like this:
// Check whether there is only a single launchable resource, and it
// is a desktop.
if ((singlePublishedItem != null) && (singlePublishedItem instanceof ApplicationInfo)) {
ApplicationInfo appInfo = (ApplicationInfo)singlePublishedItem;
// ****************************
// COMMENT OUT NEXT LINE
// if (appInfo.getAppIsDesktop()) {
// Auto desktop launch is going ahead
// Set up a direct launch of the desktop resource
LaunchUtilities.setSessionLaunchApp(wiContext, appInfo.getId());
LaunchUtilities.setSessionDirectLaunch(wiContext, true);
// Pass on any query string parameters that were intended
// for the app list page. They should apply to the direct
// launch page instead.
String directLaunchUrl = Constants.PAGE_DIRECT_LAUNCH;
String queryString = getWebAbstraction().getRequestQueryString();
if (queryString != null) {
directLaunchUrl += “?” + queryString;
}
getWebAbstraction().clientRedirectToUrl(directLaunchUrl);
continuePageProcessing = false;
// ****************************
// COMMENT OUT NEXT LINE
// }
}
Hi Tom,
Thanks for the cool tip. Looks like a good solution.
Hello Edwin or Tom
Can someone change the code of AppList.java so I can start one perticuliar application for every user? We need this to launch our intranet automaticly. No problem if there are any costs
Remko
I like Tom’s idea. Is there no way, however, to allow one app to autolaunch when the user logs into the WI when the user has multiple published applications tied to their user?
I have a published application that needs to be running before other apps are launched so that inter-program hooks function.
If anyone has any suggestions/ideas, I’d appreciate them.
~David.
I have the same requirement – to autolaunch a specific application. Any additional thoughts on the code changes necessary to add this feature. We rely on this capability and will need to abandon our 5.x implementation.
Thanks,
Scott
Everythings possible.
1.
If you are using WI 4.6 or earlier release there is a tip here:
http://www.thomaskoetzing.de/index.php?option=com_content&task=view&id=65&Itemid=104
2.
If You are using WI5.x, we’ll need to do a check in the previous posted code, and query if, as an example, the application includes the string “AUTOLAUNCHME”, or perhaps only the description includes a specific tag to look for, before autolaunching.
3.
Create a loginscript on your servers, checking for membership of a group, and the just launch it for the user.
4.
Use 3 part SW, like PowerFuse, and use the autolaunch feature
One thing I found with the above mention autolaunch function, is that it’s not compatible with Workspace Control, that is, If a user is already logged in and is running a desktop, the autolaunchfeature will not reconnect to the same desktop, but launch another.