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

Posted on 2012-08-28
Last Modified: 2012-08-30
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!
Question by:gnivler
    LVL 36

    Expert Comment

    by:Carl Webster
    You can use one WI site to do this.  I wrote an article on how to do this.
    LVL 2

    Author Comment

    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?
    LVL 19

    Expert Comment

    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.
    LVL 19

    Assisted Solution

    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?
    LVL 2

    Author Comment

    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...
    LVL 23

    Accepted Solution

    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.

    LVL 2

    Author Closing Comment

    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

    How to run any project with ease

    Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
    - Combine task lists, docs, spreadsheets, and chat in one
    - View and edit from mobile/offline
    - Cut down on emails

    Join & Write a Comment

    After several days of searching and hunting for limited documentation, I wanted to share this guide to hopefully save someone the hassle of trying to figure this out on their own. I have tested this on Xendesktop 7.1 and PS 4.5 running simultaneous…
    How to install and configure Citrix XenApp 6.5 - Part 1. In this video tutorial we have explained step by step installation of Citrix XenApp 6.5 Server on Windows Server 2008 R2 is explained in this video. We have explained the difference between…
    This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor ( If you're looking for how to monitor bandwidth using netflow or packet s…

    755 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    26 Experts available now in Live!

    Get 1:1 Help Now