VMware View 6 ThinApps vs Application Pool?

EE, thanks for reading

My question is regarding the difference between using registered ThinApps for linked clone desktops vs an RDSH Farm with the same Apps available created using the Application Pool?

The difference is virtual desktops won't have the icon available on the desktop or require a sandbox but will have it available once they login to their View Client shortcut on their desktop as shown in the pic but in production these will be things like exchange and customer work applications, not notepad etc.

I'm not sure what use case would be between the two or what the industry standard is doing so any information is appreciated.

Thanks again as always.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
The difference is that Thinapps run on the client (linked clone) App Pool runs on the server.
snyderkvAuthor Commented:
Thanks David, I get that part and mentioned that much in the second paragraph. My question is use cases i.e. why use one over the other and what the industry standard leans towards doing?
David Johnson, CD, MVPOwnerCommented:
There is no industry standard or best practice for this. Thinapps usually are run on a discrete client operating system. and it saves doing a local installation on each client machine you deploy the application ready to go and it runs in its sandbox. This puts the memory/compute load onto the client.  in a virtualized world with the client o/s and the published app are on the same server then it comes down to customization of the applicaiton itself. or for instance running 2 versions of a program i.e. outlook.

So it really coms down to business requirements and the environment involved.
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Apologies on the late reply.  I was working at VMworld all last week.

As for this question, I'm not quite sure what the question is.

I can say the same ThinApp packaged application can be configured for use in both the VDI desktop and the RDSH app pools.

For the VDI Desktop, whether you wish to have the icon of the application appear on the user's desktop or not when the ThinApp packaged application is registered (I will assume using THINREG in a login script), that configuration is simply a modification of the entry point Shortcuts= line item (note the value is plural with an "s" at the end) within the PACKAGE.INI file.  I usually just add in the %DESKTOP% value to make that happen.

For the RDSH system - when using a ThinApp package to create an Application Pool in Horizon - just register the ThinApp to the system either via the ThinApp Packaged application's MSI file or THINREG.EXE /a (make sure to use the "/a" value to register to all users on the system).  The icon appearing on the desktop is not needed to make it work as an RDSH Application Pool.

As for the use cases, the other folks above have answered that quite well... It's simply a matter of what end users need and allowing them to work in the fashion which they find best suites their needs.
snyderkvAuthor Commented:
So what would be a need case for one over the other? That's pretty much what I'm asking. As stated earlier, I've set them up and made both work.
One end user works from a desktop computer or laptop and finds it easier to use a full VDI desktop and use the applications in conjunction with each other.

Another end user is always mobile or on a non-windows desktop/laptop and finds it easier to have just the application seamlessly.

It will greatly depend on how your end users work and what their job functions demand of them.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
snyderkvAuthor Commented:
We are non mobile and don't remote in, plus we may have a few hundred apps which can be a pain to virtualize, update and require a suite of products to manage as not all apps virtualizable. That's a full time job alone so I'm trying to convince my colleagues to not do linked clones
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.