I am trying to push a web interface here at my new job. I loved the central management of this setup, however I am concerned about licensing.
If I remember correctly, the anon session that is used to post the Web Interface requires a Citrix Concurrent License. Then once someone signs in, and launches an application, another concurrent license is used for that user account.
Is it fair to say, that to use thin clients that post to web interface (IE citrix session) automatically requires a citrix concurrent license (when posting IE anonymously) so in essence one thin client with one user will require 2 Citrix concurrent licenses?
thanks for debunking or confirming.
Maybe I don't fully understand what you are doing but Citrix and TS (on win 2003) uses User based licenses. So each user should be able to log in and open as many sessions as they want.
In my Environment I set the thin clinet to use the internet Browser. When you boot up the thin it launches the WI and brings up the logon page. From there the user enters in their credentials and logs into Citrix. I don't think the actual license gets used until they click on a published application.
There would be no reason using WI would burn more licenses.
Senior Administrator (Citrix)USI HoldingsNo matter where I am i'm never where I want to be.
We want to use the IE session on Citrix to present the Web Interface., not the built in browser on the thin clients as we do not want to run CE, XPe, and the like. We would publish this, so that the Wyse Thin Clients using the Wyse OS would post this IE session (anonymously or with a generic logon) at boot up.
With 200 Thin Clients, there would be 200 Anon Sessions presenting the logon screen of WI. This was the setup at a few hospitals I have worked in the past. I am just trying to confirm or rebuke that this setup would be 2 citrix concurrent licenses.
Citrix uses concurrent user licensing, TS can be either per user or by device. We run the later.
Hi David,
I would be interested in discussing how you currently configure your thin clients for connection. What you're looking to do is a very common configuration as it requires the least scripting and handles the application enumeration and presentation of shortcuts for you. Actually, this is probably the most common deployment strategy. I don't particularily prescribe to this method for internal (LAN) connection, as (IMO) it's much better suited when integrated into an application gateway. Highly debatable no doubt. Depends on what you're after. Fast deployment or simplicity, robustness, and reliability. I can tell you this. IIS being what it is, you should think about setting-up MS clustering and NLB, or at least NLB (two WI's) e.g. more complexity and requires more skill to troubleshoot issues.
From what I can garner from your posts, you're running Wyse S10 (or earlier) Thin Clients. You have ~200 devices. You want to publish the Web Interface as content and you want the Thin Clients to auto-logon to this content using an anonymous account?
I used to do something very similar. I can relay some experiences if you're interested, but to answer the crux of your question. No, you won't consume two licenses (technically yes - 1-TS license, 1-Citrix license). Once the device gets assigned a license, any subsequent connections to published applications, be it on another server, is allowed (providing they have permissions and authenticate) because the currently assigned license is validated at the Data Store.
Hope this helps,
Samuel A. RodriguezSr. Systems Administrator
Thanks Sam.
In the past, I have used Wyse s10's and the previous blazers. They posted via FTP to a toned down default.ica but the wyse version. Most of these posted to our internal WI where we did use NLB. I also had our exam rooms posting to a subfolder via DHCP reservations for single sign on to our EMR.
I loved the central setup of this, and it kept support to a minimum. If I remembered correctly, the ANONs that were posting these applications pulled a Citrix Concurrent License for ANON001, 002, etc. Once the user signed into the WI with their domain credentials and launched an application it would pull a subsequent Citrix Concurrent License, as it was a different user. That user could launch multiple apps under the one license, but there was still a license consumed by the Anon for the WI.
I just got in touch with my previous admin to confirm that it in fact was 2 citrix licenses, which my budget notes from that employer tells me that we did have to allocate licensing for the new thins.
Perhaps there was a configuration issue with the Wyse OS or Citrix, but we did end up pulling a Citrix Licesnse for the Anon Session, and then another for the domain user session.
Yes, we did basically the same thing. Custom ica file referenced from the FTP section in the appropriate DHCP Reservations for that subnet. -THAT's centralized management IYAK. 'Course it's a good idea to install their Thin Client management console (Rapport) too. Had many 1200LE's in the environment. Steadily being replaced by S30's.
I see your point now (not as clear in your first posts). I didn't see this behavior because the core application (Meditech) was published with Anonymous access. Of course, the application itself requires explicit logon credentials. So I didn't see your issue.
I was going to suggest performing a test at "0-dark-thirty" when there were minimal users on the system and you could logon to WI, & launch into an application while observing the licenses being issued from the console.
Take a look here as well: http://support.citrix.com/article/CTX159159
http://www.freewysemonkeys.com/modules.php?name=Downloads&d_op=viewdownload&cid=1
From what I understood, the license model is connection based (client device) not user based. Butt I've been wrong before!
Have a great holidays!
It would make sense that 2 licenses are in use in this scenario since you're essentially doing a double hop to launch your applications. The thin client launching published IE would use a CCU, then apps launched off of published IE (using whatever TS they are connected to acting as the client) would use another CCU. In this double hop scenario, it's not session sharing, since there are different clients here.
If you can, configure your thin clients to launch the WI page from the client to avoid running out of licenses or having to purchase extras.
Also, as a heads up, you can always call Citrix, free of charge for these types of questions. Since this is more informational versus troubleshooting, it's not considered technical support. Just go into the customer service, licensing queue. 800-424-8749 (I recently had to call to confirm a question regarding how many CCUs are used if apps are launched from WI and streamed at the same time.)Hope this helps!
Actually, I can't say for sure if what I wrote above is true. I've been playing around with this in the lab and I did have a test scenario where I launched published IE (pointing to a WI site) anonymously then launched published notepad explicitly (from published IE)and it used the same CCU when both apps/ notepad and IE were published on the same server. If I published notepad on more than one server, session sharing did not take place in my test and it did use 2 CCUs. I'd call Citrix to make sure.
If you have the option of user the thin client browser and ica client you'd be assured just one CCU.
Just and added $.02!
Best,
Thanks Katie.
The Wyse OS is fantastic, you would think that if I were serving up a Citrix Product anonymously, that it would not consume 2 licenses. Either Wyse or Citrix should figure that out....easier said than done I know.
I was roadblocked by the economy and budget cuts, so I will not be able to move to this model just yet....but there is always 2010!
Thanks everyone for your inputs.