|
|
App-V Management Server Overview
Microsoft Application Virtualization Management System includes Microsoft System Center Application Virtualization Management Console and Microsoft System Center Application Virtualization Management Service. Administrators use Microsoft System Center Application Virtualization Management Console (a Microsoft Management Console, or MMC, snap-in) to configure Microsoft System Center Application Virtualization Management Servers. Using Microsoft System Center Application Virtualization Management Console, administrators can add and remove applications, change File Type Associations (FTAs), and assign access permissions and licenses to users and groups. Microsoft System Center Application Virtualization Management Service is the communication conduit between Microsoft System Center Application Virtualization Management Console and the Microsoft Application Virtualization SQL data store.
App-V Management Server:
App-V Management Servers perform a critical role in the App-V infrastructure. They are the servers that have direct connectivity to the client workstations. The Management Server role must be deployed in the same location and, if possible, on the same fast LAN as the SQL Server role in order to ensure good connectivity between the Management Server and the App-V configuration information that is stored in the SQL Server database. In locations where fault tolerance is not required, the Management Server can be deployed to the same server as SQL Server and the Management Server Service.
Fault tolerance is achieved by load balancing Management Servers. There are two network load balancing options available: software-based NLB and hardware load balancer.
App-V Management Server delivers Microsoft Application Virtualization-enabled applications on-demand to App-V Client for Desktops. One or more App-V Management Server can share a single Application Virtualization SQL data store. App-V Management Server authorizes and authenticates requests and provides the security, metering, monitoring, and data gathering that you need. The server uses Active Directory and supporting tools to manage users and applications.
.jpg)
|
|
Figure: App-V Management System
The App-V Management Server handles user requests for application data and streams that data on demand to authorized users using RTSP or RTSPS protocols. In most configurations using this server, one or more Management Servers share a common data store for configuration and package information.
The App-V Management Server use Active Directory Groups to manage user authorization. In addition to Active Directory Domain Services, these servers have SQL Server installed to manage the database and data store. The App-V Management Server is controlled through the App-V Management Console, a snap-in to the Microsoft Management Console.
Because the App-V Management Server stream applications to end-users on demand, these servers are ideally suited for system configurations that have reliable, high-bandwidth LANs.
|
App-V Management Server also called Microsoft Application Virtualization Server, which hosts virtualized application packages and streams them to the client computers for local execution. It also authorizes requesting clients and logs their application usage.
.jpg)
|
|
Figure: App-V Management Console
VASs perform a critical role in the App-V infrastructure. They are the servers that have direct connectivity to the client workstations; they are also responsible for streaming applications to the clients. The VAS role must be deployed in the same location and, if possible, on the same fast LAN as the SQL Server role in order to ensure good connectivity between the VAS and the App-V configuration information that is stored in the SQL Server database. In locations where fault tolerance is not required, the VAS can be deployed to the same server as SQL Server and the Management Web Service.
Fault tolerance is achieved by load balancing VASs. Some load balancing solutions will provide fault tolerance at the machine level. That is, if the entire machine fails, the load balancing cluster will no longer send requests to that system. However, application failures are not recognized, so client requests will still be sent to the affected server. Other load balancing solutions will provide higher levels of fault tolerance by recognizing when the application layer has stopped responding. This will ensure that the remaining servers will continue to handle the streaming functionality in the event that a server fails. N+1 or greater VAS redundancy is required to provide fault tolerance.
The VAS service can use a Network Load Balancing system to provide additional fault tolerance to the system. The VAS is not cluster aware nor has it been tested on a server cluster, so this configuration is not supported at this time. There are two network load balancing options available: software-based NLB and hardware load balancer.
|
|
|
|
|
