Planning for the App-V 5.0 Server Deployment
Platí pro: Application Virtualization 5.0, Application Virtualization 5.0 SP1, Application Virtualization 5.0 SP2, Application Virtualization 5.0 SP3
The Microsoft Application Virtualization (App-V) 5.0 server infrastructure consists of a set of specialized features that can be installed on one or more server computers, based on the requirements of the enterprise.
Planning for App-V 5.0 Server Deployment
The App-V 5.0 server consists of the following features:
Management Server – provides overall management functionality for the App-V 5.0 infrastructure.
Management Database – facilitates database predeployments for App-V 5.0 management.
Publishing Server – provides hosting and streaming functionality for virtual applications.
Reporting Server – provides App-V 5.0 reporting services.
Reporting Database – facilitates database predeployments for App-V 5.0 reporting.
The following list displays the recommended methods for installing the App-V 5.0 server infrastructure:
Install the App-V 5.0 server. For more information, see How to Deploy the App-V 5.0 Server.
Install the database, reporting, and management features on separate computers. For more information, see How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services.
Use Electronic Software Distribution (ESD). For more information, see How to deploy App-V 5.0 Packages Using Electronic Software Distribution.
Install all server features on a single computer.
App-V 5.0 Server Interaction
This section contains information about how the various App-V 5.0 server roles interact with each other.
The App-V 5.0 Management Server contains the repository of packages and their assigned configurations. For Publishing Servers that are registered with the Management Server, the associated metadata is provided to the Publishing servers for use when publishing refresh requests are received from computers running the App-V 5.0 Client. App-V 5.0 publishing servers managed by a single management server can be serving different clients and can have different website names and port bindings. Additionally, all Publishing Servers managed by the same Management Server are replicas of each other.
Poznámka
The Management Server does not perform any load balancing. The associated metadata is simply passed to the publishing server for use when processing client requests.
Server-Related Protocols and External Features
The following displays information about server-related protocols used by the App-V 5.0 servers. The table also includes the reporting mechanism for each server type.
| Server Type | Protocols | External Features Needed | Reporting | |
|---|---|---|---|---|
IIS server |
HTTP HTTPS |
This server-protocol combination requires a mechanism to synchronize the content between the Management Server and the Streaming Server. When using HTTP or HTTPS, use an IIS server and a firewall to protect the server from exposure to the Internet. |
Internal |
|
File |
SMB |
This server-protocol combination requires support to synchronize the content between the Management Server and the Streaming Server. Use a client computer with file sharing or streaming capability. |
Internal |
Got a suggestion for App-V?
Add or vote on suggestions here. For App-V issues, use the App-V TechNet Forum.
Viz také
Další materiály
Planning to Deploy App-V
Deploying the App-V 5.0 Server
-----
You can learn more about MDOP in the TechNet Library, search for troubleshooting on the TechNet Wiki, or follow us on Facebook or Twitter.
-----