Using ThinApp in a terminal server and Citrix environment is more or less identical to running ThinApp in VDI, from a design point of view. The few considerations you have to make for VDI is true for terminal servers (TS) as well. One thing that might complicate a TS implementation is the fact that you are often running it on a 64-bit operating system. You may have to tweak your packages to support a 64-bit environment. If you are using Citrix XenApp, you publish a ThinApp package in the same way you would publish any other application on your XenApp server. When you are asked to browse to your application, simply paste the path to your package's entry point on the network share and you're good to go.

I definitely recommend streaming ThinApp packages onto your terminal server/XenApp. In that case, management and support are so much easier. You can place the network share on the same high-speed backbone as your TS environment, so network performance is rarely a bottleneck. Your servers will be more or less clean from application installations, which will make them very stable. Server updates and patches are only performed for the operating system and Citrix components. No patching of the application is required to be performed on your servers. Application updates are handled using the in-place update method. In using streaming, your whole Citrix environment has only one instance of the application. Updating this one single instance will immediately update the application to all your users.

Using ThinApp on Citrix will dramatically lower your time to market - no more time consuming manual tweaking in order to get applications installed on each of the servers within a farm. No more time consuming regression tests. Simply verify the functionality of your package, and off you go. thinreg.exe in the login script will handle your user entitlement. If you use Active Directory group membership for entitlement, thinreg.exe will register, for example, Adobe Reader 8 to one group of users and Adobe Reader X to another. Both groups can be logged in on the same physical terminal server and still have their own file type registrations and their own start menus. thinreg.exe registers on a per user basis by default. You should not use the thinreg.exe/a switch, which would register machine wide.