With View, you have several options regarding application provisioning: You can use traditional application provisioning techniques, you can provide remote applications rather than a remote desktop, you can distribute application packages created with VMware ThinApp, you can deploy applications as part of a View Composer or instant clone base image, or you can attach applications using App Volumes.

You might choose to provide end users with remote applications rather than remote desktops. Individual remote applications might be easier to navigate on a small mobile device.

Because linked-clone desktop pools share a base image, you can quickly deploy updates and patches by updating the parent virtual machine.

Because instant clone desktop pools share a base image, you can quickly deploy updates and patches by updating the parent virtual machine.

VMware ThinApp™ lets you package an application into a single file that runs in a virtualized application sandbox. This strategy results in flexible, conflict-free application provisioning.

VMware App Volumes offers an alternative way to manage applications by virtualizing applications above the operating system. By using this strategy, applications, data files, settings, middleware, and configurations act as separate, layered containers.

With View, you can continue to use the application provisioning techniques that your company currently uses, and you can use Mirage. Two additional considerations include managing server CPU usage and storage I/O and determining whether users are permitted to install applications.