App-V Standalone Model consists of the App-V Sequencer and the App-V Client; no additional App-V infrastructure is required. The App-V Sequencer now has an option to create an .msi file that automates the addition of the virtual application. The .msi contains metadata so an ESD system can recognize it and control the virtualized applications. Stand-alone mode requires the client to go into stand-alone mode, which only allows .msi-based updates of the virtual applications; streaming is not allowed while in stand-alone mode. This mode is meant for those rarely connected users that need the power of virtualized applications, but do not have access to a server. A Group Policy administrative template (.adm) is avaliable to manage these settings centrally through group policy.  

 Figure: App-V Standalone Client Model

The App-V Sequencer packages the publication information, shortcuts, and the install routines into a Windows Installer file (MSI), and the virtualized application in to an SFT file. The installer adds the virtual application package to the App-V Desktop Client. The publication information is configured to load applications from a local location rather than stream them across a WAN. Users can temporarily connect to a network to retrieve the Windows Installer files or can run them from a DVD.

The application can then be distributed using existing installation method, such as:
• Active Directory publishing through Group Policy objects (GPOs).
• Media distribution via USB key or CD.
• Run from a file share or Web server.
• Software management systems such as System Center Configuration Manager 2007 or Microsoft Systems Management Server  (SMS) 2003.