Configuring and using the standalone mode
As we know, another great option, when we can't (or just won't) use an App-V Management Server, is the standalone mode.
Working in standalone mode, we don't need anything more than the App-V Desktop Client to stream the applications from a local resource (such as a folder on the client's computer) or from a remote resource (such as a file server available on the network).
Since there's no server in charge of the publication process, in standalone mode, App-V clients cannot be aware that there are new applications available. This gives us three possibilities for importing applications:
Standalone without streaming: Here, we deploy the MSI file manually or using Group Policy. The MSI file contains the OSD and ICO files; in this scenario, the installer also uses the SFT file stored locally, on the client machine.
Standalone with SMB streaming: Here, we deploy MSI files using only the manifest file, and we can have the SFT placed on a file server for SMB...
