The most valuable feature of Microsoft App-V that I found is the possibility to bring old software back to life and publish it for users to do their jobs using those applications. Additionally, this came free with an agreement with SCCM since it did not require any additional licenses; it was an add-on to SCCM when the enterprise acquired the solution. One of the latest releases allowed for easy publishing via SCCM, making it quite flexible and easy to maintain. Once you package one app, it can be delivered to many users, creating a win-win situation because if it was packed in a capsule, the interaction with the user was minimal. The users could not break the app or ask for support because there was no support; they simply had this app in a container that would function correctly, without altering the content. The downside is that not all software worked perfectly due to how they were written—as either machine or user context—which impacted how applications could be delivered. In a virtual environment with many users on the same machine, surprises could happen. I utilize the feature of Microsoft App-V for running multiple versions of applications concurrently, where they are pushed by SCCM. We can have different populations with different versions published simultaneously, either through SCCM or Microsoft App-V. However, I'm currently contemplating whether the enterprise I'm in still uses the old App-V infrastructure or if they have completely switched to SCCM packages, as they have multiple personnel for managing SCCM and only had three individuals for the Microsoft App-V infrastructure.
