Virtualization

To C:. Drive Q: is the (default) target for sequenced apps. Have you read any documentation on AppV?

Cool, that is what I thought (and now I've read). Another question for you. How do you rate App-V to ThinApp and the Altiris tool (which used to be called SVS)? Do you prefer one over the other and if so why? Thank you.

I couldn't comment on AppV versus ThinApp, although my understanding is that they're not quite the same thing. As for Altiris, given the state of the Wise product line, I wouldn't bet the farm on a single technology coming from them. Actually, I wouldn't bet a single hay bale.

from what I've seen of VMWare ThinApp, it creates one executable that contains everything that's comprised in an application. Major advantage is that it's an agent-less solution, meaning you only need the exe, you don't need some agent on your PC that supplies the application to you.

App-V packages on the other hand are meant to be used in conjunction with a distribution system (App-V Management Server or SCCM server) and require you to install an agent on the client machines (App-V client or SCCM advanced client). This is more involved but does create more options when it comes to the actual distribution of the application data to the machines (read: on-demand streaming of application data).

What they do have in common is that they both create an 'isolated' version of the application, that can run completely separated from the underlying OS and other apps..

In the end though, like Ian said, they're not quite the same thing.

PJ

App-V packages on the other hand are meant to be used in conjunction with a distribution system (App-V Management Server or SCCM server) and require you to install an agent on the client machines (App-V client or SCCM advanced client).

With SCCM, you actually still need both App-V Client and SCCM Client; SCCM just drives App-V Client in the background.

/Kalle