Deploying the App-V server

  • Article

Applies to: Windows Server 2016

You can install the Application Virtualization (App-V) server components using different deployment configurations, which are described in this topic. Before you install the server features, review the server section of App-V security considerations.

Note

If you plan to use the App-V server components in your deployment, note that the version number is still listed as App-V 5.x, as the App-V server components have not changed in App-V for Windows client.

To learn more about deploying App-V for Windows client, read What's new in App-V.

Important

Before installing and configuring the App-V servers, you must specify the port or ports where each component will be hosted. You must also add the associated firewall rules to allow incoming requests to access the specified ports, as the installer does not modify firewall settings.

Download and install App-V server components

Note

If you're already using App-V 5.x, you don't need to re-deploy the App-V server components, as they haven't changed since App-V 5.0 was released.

App-V offers the following five server components, each of which serves a specific purpose in an App-V environment.

  • Management server. Use the App-V management server and console to manage your App-V infrastructure. See Administering App-V with the management console for more information about the management server.

    Note

    If you are using App-V with your electronic software distribution solution, you don’t need to use the management server and console. However, you may want to take advantage of the reporting and streaming capabilities in App-V.

  • Management database. Use the App-V management database to facilitate database pre-deployments for App-V management. For more information about the management database, see How to deploy the App-V server.

  • Publishing server. Use the App-V publishing server to host and stream virtual applications. The publishing server supports the HTTP and HTTPS protocols and does not require a database connection. To learn how to configure the publishing server, see How to install the App-V publishing server.

  • Reporting server. Use the App-V reporting server to generate reports that help you manage your App-V infrastructure. The reporting server requires a connection to the reporting database. To learn more about App-V's reporting capabilities, see About App-V reporting.

  • Reporting database. Use the App-V reporting database to facilitate database pre-deployments for App-V reporting. To learn more about the reporting database, see How to deploy the App-V server.

All five App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from either of the following locations:

In large organizations, you might want to install more than one instance of the server components to get the following benefits.

  • Fault tolerance for situations when one of the servers is unavailable.
  • High availability to balance server requests. A network load balancer can also help you achieve this.
  • Scalability to support high loads. For example, you can install additional servers behind a network load balancer.

App-V standalone deployment

The App-V standalone deployment's topology is good for small deployments or test environments. In this implementation type, all server components are installed on a single computer. The services and associated databases will compete for the resources on the computer that runs the App-V components. However, because services and associated databases will compete for the computer's resources, it's not a good idea to use the standalone deployment for larger deployments.

The following articles will give you more information about how to set up an App-V standalone deployment.

App-V server distributed deployment

The distributed deployment topology can support a large App-V client base, allowing you to more easily manage and scale your environment. When you use this type of deployment the App-V server components are deployed across multiple computers, based on your organization's structure and requirements.

Using an Enterprise Software Distribution (ESD) solution and App-V

You can also deploy packages with an ESD. Its full integration capabilities will vary depending on which ESD you use.

Note

The App-V reporting server and reporting database can still be deployed alongside the ESD to collect the reporting data from the App-V clients. However, the other three server components should not be deployed, because they will conflict with the ESD functionality.

App-V Server logs

You can use App-V server log information to help troubleshoot the server installation and operational events while using App-V. The server-related log information can be reviewed with the Event Viewer. The following line displays the specific path for Server-related events:

Event Viewer \ Applications and Services Logs \ Microsoft \ App V

Associated setup logs are saved in the following directory:

%temp%

App-V reporting

App-V reporting allows App-V clients to collect data and then send it back to be stored in a central repository. You can use this information to get a better view of the virtual application usage within your organization. The following list displays some of the types of information the App-V client collects:

  • Information about the computer running the App-V client.
  • Information about virtualized packages on a specific computer running the App-V client.
  • Information about package open and shutdown for a specific user.

The reporting information will be maintained until it is successfully sent to the reporting server database. After the data is in the database, you can use Microsoft SQL Server Reporting Services (SSRS) to generate any necessary reports.

If you want to retrieve report information, you must use Microsoft SQL SSRS, which is available with Microsoft SQL. SSRS must be deployed separately to generate the associated reports, as it isn't automatically installed during App-V server installation.

For more information, see About App-V reporting and How to enable reporting on the App-V client by using Windows PowerShell.

Other App-V server resources