Summary
In this chapter, we learnt about high availability and load balancing possibilities in Microsoft Application Virtualization as well as the requirements for extending our implementation outside the organization.
We've learned that the success of a highly available implementation starts with the correct analysis and design. This is an important matter to review since not all roles and services are available to use in a Failover Cluster or in NLB.
We've also reviewed all the necessary steps to accomplish a load balanced solution using Microsoft's NLB role. Even though it could appear as a simple procedure, there are several requirements that we can't avoid, such as Service Principal Names and accounts delegation in Active Directory.
Database mirroring is another feature in high availability for App-V, in this case for the SQL data store. Database mirroring is widely used in several scenarios for its simplicity and effectiveness, but in App-V, we must consider that there are some tasks...
