[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1880
  • Last Modified:

Is it possible to publish a XenApp 6.5 Server Desktop application to legacy thin clients?

Most of our client machines are Wyse V90L/E and they are running Program Neighborhood 10.x and 11.0.x.  The existing farm is XenApp/PS 4.5, and they use either discovery or a service site in Web Interface 5.4.  The only application is a desktop.

I am piloting a replacement farm running XenApp 6.5 and being a Citrix amateur I'm not sure if it's possible, and what might be the best approach, to getting that new desktop available to old clients.  I have a new/separate web interface for the 2nd farm, I didn't join the new server to the existing farm (not sure what is appropriate).

The web interface is high on my list except that the Wyse machines pin the CPU when browsing it in Internet Explorer, resulting in a very sluggish interface and not really something I can put into production as-is even though it technically works.

Thanks for any assistance!
2 Solutions
Carl WebsterCommented:
You can use one WI site to do this.  I wrote an article on how to do this.

gnivlerAuthor Commented:
Thanks Carl, I will read through it and have skimmed it now and bookmarked, but I'm not sure if it's on-topic.  The reason I say that is because I have a working web interface already and it makes both old and new desktops available.  Ideally I would have everyone using the web interface, but given the problems I've had with (updating) the Wyse boxes I was hoping for a different solution.  Does that make any sense?
As you're piloting xenapp 6.5, you can do the below. For now let's not disturb production:

1. You can also use your production URL for creating a new site. But if that WI is already busy and do not wish to disturb, then create a dedicated VM for Xenapp 6.5 WI, configure new sites for web and also configure xenapp sites and services (if you wish to deliver apps using citrix receiver instead of web interface)

2. Create a new farm, publish xenapp6.5 desktop, add that server to the Xenapp 6.5 WI as an XML broker.

3. Upgrade your WYSE client to latest Citrix receiver to take full advantage of latest xenapp version(even though old clients work here)

Test it out and see how it goes. If you're happy with the result, it all depends as either you may wish to go with a new URL or old URL.
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Regarding WYSE, not sure why it's taking high CPU with IE. Have you tried using with Xenapp sites and services to deliver apps directly to receiver instead of WI?
gnivlerAuthor Commented:
Thank you for the help basraj.

I have actually already completed 1 and 2, and it's working fine.  Updating the Citrix client on the Wyse machines is problematic and I'm trying to avoid going that route, but in testing the receiver or online plugin both work in and out of the web interface.

I've created custom ICA connections from a thin client using legacy PN clients and it works, but I want to automate it, if that's the best solution without updating the client software.

I'm reading up on creating/distributing custom ICA files, but if you have some resources to get me started that would be appreciated!  Assuming this idea even makes sense...
The Custom ICA files will work fine, and you can use your old PN to generate them.. Basically, this is what WI does.. it just automates the generation of custom ICA files.  

From your PN, (if memory serves), you can right click and say Create ICA file.  that's literally all you need.  And if you are publishing desktops, you don't really need anything else.  You can just put those ICA files on your Wyse terminals.  With that, you will not need a WI.  Be aware, that this is not easy for long term management.. it's just a possibility.

gnivlerAuthor Commented:
Thanks Coralon.  I wasn't able to save the ICA from PN (11.0), but I managed to save the ICA that the web interface was sending, edited it to not self-destruct and copying it to the legacy Wyse desktops does indeed appear to work.  I'm completely on board with the management issues but updating these horrible little boxes has proven to be a nightmare so a kludge is looking pretty attractive!

Final note:
My problem is solved by manually distributing the ICA file directly to the Wyse desktops, which precludes users having to configure settings and avoids updating the legacy Citrix clients.

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now