From 921559e1dcca5a6d534b2ff1f6d85e7309699e57 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Fri, 2 Feb 2018 16:46:11 -0800 Subject: [PATCH] Created Application comaptability article --- .../revision-heidi/appv-capacity-planning.md | 6 +- ...lanning-for-high-availability-with-appv.md | 114 ++++++++++++++++++ 2 files changed, 117 insertions(+), 3 deletions(-) create mode 100644 windows/application-management/app-v/revision-heidi/appv-planning-for-high-availability-with-appv.md diff --git a/windows/application-management/app-v/revision-heidi/appv-capacity-planning.md b/windows/application-management/app-v/revision-heidi/appv-capacity-planning.md index de9e9e20df..dcb94aa781 100644 --- a/windows/application-management/app-v/revision-heidi/appv-capacity-planning.md +++ b/windows/application-management/app-v/revision-heidi/appv-capacity-planning.md @@ -870,11 +870,11 @@ The number of clients a streaming server can support can be significantly increa ## Combining App-V server roles -Discounting scaling and fault-tolerance requirements, the minimum number of servers that a location with Active Directory connectivity needs is one. This server will host the management server, management server service, and Microsoft SQL Server roles. This means that you can arrange server roles in any combination you like, as they don't conflict with one another. +Discounting scaling and fault-tolerance requirements, the minimum number of servers that a location with Active Directory connectivity needs to function is one. This server will host the management server, management server service, and Microsoft SQL Server roles. This means that you can arrange server roles in any combination you like, as they don't conflict with one another. -Ignoring scaling requirements, the minimum number of servers that a fault-tolerant implementation needs is four. The management server and Microsoft SQL Server roles support placement in fault-tolerant configurations. The management server service can be combined with any of the roles, but remains a single point of failure. +Ignoring scaling requirements, the minimum number of servers that a fault-tolerant implementation needs to function is four. The management server and Microsoft SQL Server roles support placement in fault-tolerant configurations. The management server service can be combined with any of the roles, but remains a single point of failure. -Although there are many fault-tolerance strategies and technologies you can use, not all are applicable to a given service. Additionally, if App-V roles are combined, certain fault-tolerance options may no longer apply due to incompatibilities. +Although there are many fault-tolerance strategies and technologies you can use, not all are applicable to a given service. Additionally, if App-V roles are combined, the resulting incompatabilities could cause certain fault-tolerance options to stop working. ## Related topics diff --git a/windows/application-management/app-v/revision-heidi/appv-planning-for-high-availability-with-appv.md b/windows/application-management/app-v/revision-heidi/appv-planning-for-high-availability-with-appv.md new file mode 100644 index 0000000000..5bdd43bddf --- /dev/null +++ b/windows/application-management/app-v/revision-heidi/appv-planning-for-high-availability-with-appv.md @@ -0,0 +1,114 @@ +--- +title: Planning for High Availability with App-V Server +description: Planning for High Availability with App-V Server +author: MaggiePucciEvans +ms.pagetype: mdop, appcompat, virtualization +ms.mktglfcycl: deploy +ms.sitesec: library +ms.prod: w10 +ms.date: 04/19/2017 +--- +# 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](appv-deploy-appv-databases-with-sql-scripts.md). + +## 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: + +* [Achieving High Availability and Scalability - ARR and NLB](http://www.iis.net/learn/extensions/configuring-application-request-routing-arr/achieving-high-availability-and-scalability-arr-and-nlb) describes how to configure IIS 7.0. + +* [Network load balancing overview]() will tell you more about how to configure Microsoft Windows Server. (FIX LINK) + + This information also applies to IIS NLB clusters in Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012. + +>[!NOTE] +>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](https://technet.microsoft.com/library/hh831491.aspx). (FIX LINK) + +## 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](appv-deploying-the-appv-sequencer-and-client.md). +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](appv-add-or-upgrade-packages-with-the-management-console.md). +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: + +* [Create a failover cluster](https://technet.microsoft.com/library/dn505754(v=ws.11).aspx). +* [Use cluster shared volumes in a failover cluster](https://technet.microsoft.com/library/jj612868(v=ws.11).aspx). + +## 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: + +* [Prepare a mirror database for mirroring (SQL Server)](https://technet.microsoft.com/library/ms189053.aspx) (FIX LINK) +* [Establish a database mirroring session using Windows Authentication (SQL Server Management Studio)](https://msdn.microsoft.com/library/ms188712.aspx) (FIX LINK) + +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 = ```. 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 = ```: + +>[!IMPORTANT] +>This topic describes how to change the Windows registry by using Registry Editor. If you change the Windows registry incorrectly, you can cause serious problems that might require you to reinstall Windows. You should make a backup copy of the registry files (System.dat and User.dat) before you change the registry. Microsoft cannot guarantee that the problems that might occur when you change the registry can be resolved. Change the registry at your own risk. + + +1. Login 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>**. + +4. Restart management service using the IIS console. + + **Note**   + Database Mirroring is on the list of Deprecated Database Engine Features for Microsoft SQL Server 2012 due to the **AlwaysOn** feature available starting with Microsoft SQL Server 2012. + +Click any of the following links for more information: + +* [Prepare a Mirror Database for Mirroring (SQL Server)](https://technet.microsoft.com/library/ms189053.aspx). + +* [Establish a Database Mirroring Session Using Windows Authentication (SQL Server Management Studio)](https://technet.microsoft.com/library/ms188712(v=sql.130).aspx). + +* [Deprecated Database Engine Features in SQL Server 2012](https://msdn.microsoft.com/library/ms143729(v=sql.110).aspx). + +## 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)](https://technet.microsoft.com/library/hh510230.aspx). + +## Have a suggestion for App-V? + +Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). + +## Related topics + +[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)