Planning for high availability with App-V Server

Applies to: Windows 10, version 1607

Microsoft Application Virtualization (App-V) system configurations can take advantage of options that maintain a high available service level.

The following sections will he following sections to help you understand the options to deploy App-V in a highly available configuration.

Support for Microsoft SQL Server clustering

You can run the App-V Management and Reporting databases on computers running Microsoft SQL Server clusters. However, you must install the databases using scripts.

For deployment instructions, see How to deploy the App-V databases by using SQL scripts.

Support for IIS network load balancing

You can use Internet Information Services' (IIS) network load balancing (NLB) to configure a highly available environment for computers running the App-V Management, Publishing, and Reporting services that are deployed through IIS.

Review the following articles to learn more about configuring IIS and NLB for computers running Windows Server operating systems:


The IIS NLB functionality in Windows Server 2012 is generally the same as in Windows Server 2008 R2. However, some task details have changed in Windows Server 2012. To learn how to work with these changes, see Common management tasks and navigation in Windows.

Support for clustered file servers when running SCS mode

Running App-V Server in Shared Content Store (SCS) mode with clustered file servers is supported.

To enable SCS mode configurations, follow these steps:

  1. Configure the App-V client to run in SCS mode. For more information, see Deploying the App-V Sequencer and Configuring the Client.
  2. Configure the file server cluster, configured in either the scale out mode (which started with Windows Server 2012) or the earlier clustering mode, with a virtual SAN.

The following steps can be used to validate the configuration:

  1. Add a package on the publishing server. To learn how to add a package, see How to add or upgrade packages by using the Management console.
  2. Perform a publishing refresh on the computer running the App-V client and open an application.
  3. Switch cluster nodes mid-publishing refresh and mid-streaming to ensure failover works correctly.

Review the following articles to learn more about configuring Windows Server failover clusters:

Support for Microsoft SQL Server mirroring

Using Microsoft SQL Server mirroring, where the App-V management server database is mirrored utilizing two SQL Server instances, for App-V management server databases is supported.

Review the following to learn more about how to configure Microsoft SQL Server mirroring:

The following steps can be used to validate the configuration:

  1. Initiate a Microsoft SQL Server Mirroring session.
  2. Select Failover to designate a new master Microsoft SQL Server instance.
  3. Verify that the App-V management server continues to function as expected after the failover.

The connection string on the management server can be modified to include failover partner = <server2>. This will only help when the primary on the mirror has failed over to the secondary and the computer running the App-V client is doing a fresh connection (say after reboot).

Use the following steps to modify the connection string to include failover partner = <server2>:


This process involves changing the Windows registry with Registry Editor. If you change the Windows registry incorrectly, you can cause serious problems that might require you to reinstall Windows. Always make a backup copy of the registry files (System.dat and User.dat) before changing the registry. Microsoft can't guarantee that problems caused by changing the registry can be resolved, so change the registry at your own risk.

  1. Log in to the management server and open regedit.
  2. Navigate to HKEY_LOCAL_MACHINE \ Software \ Microsoft \ AppV \ Server \ ManagementService.
  3. Modify the MANAGEMENT_SQL_CONNECTION_STRING value with the failover partner = <server2> value.
  4. Restart management service using the IIS console.


Database Mirroring is on the list of deprecated database engine features in SQL Server 2012 due to the AlwaysOn feature available starting with Microsoft SQL Server 2012.

Click any of the following links for more information:

Support for Microsoft SQL Server Always On configuration

The App-V management server database supports deployments to computers running Microsoft SQL Server with the Always On configuration. For more information, see Always On Availability Groups (SQL Server).