Software Deployment

Jarazul,

There are limitations on the sequencing of virtual applications with App-V, which is why MSI (or other native) installations will still be in used in an App-V shop.

Section 6 of the App-V 4.6 Sequencing Guide from Microsoft explains the reasonings behind this.

App-V is still very much in its infancy (even though it's been around for years) with regard to uptake by the big players - which is why it's probably it's only now becoming a buzz word.
I saw a demo of Softgrid (App-V before MS purchased it) over 4 years ago and the company involved didn't take it any further than a proof of concept.

'Regular' packaging is here to stay - even in a virtual world - for the time being.

Thanks,

Dunnpy

I seem to recall one client to whom a colleague and I proposed App-V making a severely strained face vis-a-vis licensing costs, too. I can no longer keep track of Microsoft's licensing options so couldn't tell you which model you need to have which effectively gets you free client licenses but this client worked out their costs at around GBP 150K. Needless to say, the project stalled at that point.

Thanks for your replies. The licensing issues are a good argument. You need Software Assurance for your Desktop OS and the MDOP, i think its about 10$ per PC per year.

We will consider the evaulation of app-v if our customer is able to meet the license requirements.

I think it's more than that! Don't quote me as I'm not an accountant but they were talking around 2 million pounds for Software assurance and MDOP here for 10000 desktops!
Hence no App-v[:'(]

Yes you have to pay, thats what i know, im a technician too, no accountant :(, the SA. Thats almost 45$ every two years. The SA is of course only valid if you have a licensed OS beneath it.

For App-V for Terminal Services, there are different licensing models / requirements.