Microsoft App-V

It was originally developed by Softricity, a company based in Boston, Massachusetts, acquired by Microsoft on July 17, 2006.

It removes the need for traditional local installation of the applications, although a standalone deployment method is also supported.

Microsoft released Version 5 of App-V in late November 2012, which is a third generation major redesign of the entire platform.

Although little online information exists about the company today,[9] this product provided streaming services with very limited virtualization support.

The product is available as part of System Center Virtual Machine Manager, and is typically used to spin up new instances of servers on a demand-driven basis.

The App-V 5.x clients contains a PowerShell API that is ultimately used by both of the server modes above.

It is sometimes desirable to use this API directly at the client, either manually or using additional tooling developed by third parties.

All three of these options use a couple of common components: The App-V 4.x system architecture is composed of the following components: In 2009 Microsoft offered a new way to implement App-V with enhancements to System Center Configuration Manager.

In this case, the sequenced packages are delivered using an external technique, such as an Electronic Software Delivery system or manual deployment.

The package is also configured for streaming operations, where portions of files may be delivered on an as-needed basis to clients.

The App-V client receives virtual application package definitions in several ways.

It also may be sent instructions via a client API, which is used by System Center deployments, the virtual msi, and stand-alone methods.

User settings are stored in the local system itself using redirection to ensure that the cached copy of the application is not changed.

In some cases, this allows for the deployment of applications that are not multi-user aware to be used on Remote Desktop Shared Host systems.