Publishing App-V Applications

Microsoft Application Virtualization (or App-V) is an application streaming solution from Microsoft. Beginning with Parallels RAS v16.5, a support for App-V application publishing is available in the Parallels RAS console.

At the time of this writing, the App-V support implements scenarios where application provisioning is performed by means of App-V components:

• Applications are sequenced by the administrator according to Microsoft guidelines.
• Applications are stored on a network share created by the administrator (SMB, HTTPs).
• App-V Management and Publishing servers are used to publish applications for a specific AD groups that must by synced manually by the administrator with RAS publishing groups used for App-V application publishing.
• App-V client is installed and configured manually by the administrator.

The process of deploying and publishing an App-V application is as follows:

1. Package an applications using the App-V Sequencer.
2. Deploy the application to an RD Session Host using the App-V Management Console, Microsoft SCCM, etc.
3. Provision the application.
4. Verify that users can launch the application from the RD Session Host.
5. Publish the application from RAS Console (see below for instructions).
6. Launch the application from a Parallels RAS Client.

Publish an App-V application from the Parallels RAS console

To publish an App-V application:

1. In the Parallels RAS Console, select the Publishing category.
2. Click the [+] Add icon at the bottom of the right pane. The publishing wizard opens.
3. On the Select Item Type page, select the App-V application option.
4. Click Next .
5. Select the server type from which to publish an application and click Next .
6. Select a server or a group to publish from and click Next .
7. On the Installed Applications page, select one or more App-V applications and click Next .
8. Review the summary and complete the wizard.

Once an App-V application is published, it can be launched from a Parallels RAS Client.

Note: To avoid launch issues, use AutoLoad=2. More details in https://blogs.technet.microsoft.com/technetsto_sup/2013/11/12/autoload-setting-in-app-v-5-0/