mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-29 13:47:23 +00:00
Merge remote-tracking branch 'refs/remotes/origin/8442312-app-v'
This commit is contained in:
commit
6d98423bb0
@ -30,8 +30,8 @@ To start using App-V to deliver virtual applications to users, you’ll need to
|
||||
|
||||
| Component | What it does | Where to find it |
|
||||
|------------|--|------|
|
||||
| App-V server components | App-V offers five server components that work together to allow you to host and publish virtual applications, generate usage reports, and manage your App-V environment. For information about the server components, see [Deploying the App-V Server](appv-deploying-the-appv-server.md).<br><br>**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. | The App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from:<br> - The [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/en-us/subscriptions/downloads/default.aspx#FileId=65215). You must have a MSDN subscription to download the MDOP ISO package from the MSDN subscriptions site.<br> - The [Volume Licensing Service Center](https://www.microsoft.com/en-us/licensing/default.aspx) if you're using [Windows 10 for Enterprise or Education](https://www.microsoft.com/en-us/WindowsForBusiness/windows-product-home).<br><br>See [Deploying the App-V Server](appv-deploying-the-appv-server.md) for more information about installing and using the server components.
|
||||
| App-V client and App-V Remote Desktop Services (RDS) client | The App-V client is the component that runs virtualized applications on user devices. The client enables users to interact with icons and file names to start virtualized applications. | The App-V client is automatically installed with Windows 10. <br>For information about enabling the client, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md). |
|
||||
| App-V server components | App-V offers five server components that work together to allow you to host and publish virtual applications, generate usage reports, and manage your App-V environment. For information about the server components, see [Deploying the App-V Server](appv-deploying-the-appv-server.md).<br><br>**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. | The App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from:<br><br> - The [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/en-us/subscriptions/downloads/default.aspx#FileId=65215). You must have a MSDN subscription to download the MDOP ISO package from the MSDN subscriptions site.<br><br> - The [Volume Licensing Service Center](https://www.microsoft.com/en-us/licensing/default.aspx) if you're using [Windows 10 for Enterprise or Education](https://www.microsoft.com/en-us/WindowsForBusiness/windows-product-home).<br><br>See [Deploying the App-V Server](appv-deploying-the-appv-server.md) for more information about installing and using the server components.
|
||||
| App-V client and App-V Remote Desktop Services (RDS) client | The App-V client is the component that runs virtualized applications on user devices. The client enables users to interact with icons and file names to start virtualized applications. | The App-V client is automatically installed with Windows 10, version 1607. <br><br>For information about enabling the client, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md). |
|
||||
| App-V sequencer | Use the App-V sequencer to convert Win32 applications into virtual packages for deployment to user devices. Devices must be running the App-V client to allow users to interact with virtual applications. | Installed with the [Windows Assessment and Deployment kit (ADK) for Windows 10, version 1607](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit). |
|
||||
|
||||
For more information about these components, see [High Level Architecture for App-V](appv-high-level-architecture.md).
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Migrating to App-V from a Previous Version (Windows 10)
|
||||
description: Migrating to App-V from a Previous Version
|
||||
description: Migrating to App-V for Windows 10 from a previous version
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -9,17 +9,14 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Migrating to App-V from a Previous Version
|
||||
# Migrating to App-V from previous versions
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
With Microsoft Application Virtualization (App-V), you can migrate your existing App-V 4.6 or App-V 5.0 infrastructure to the more flexible, integrated, and easier to manage App-V infrastructure.
|
||||
However, you cannot migrate directly from App-V 4.x to App-V for Windows 10—you must migrate to App-V 5.0 first. For more information on migrating from App-V 4.x to App-V 5.0, see [Migrating to App-V server from a Previous Version](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/migrating-to-app-v-51-from-a-previous-version)
|
||||
|
||||
**Note**
|
||||
Packages for App-V for Windows 10 are exactly the same as packages for App-V 5.0. There has been no change in the package format between the versions and therefore, there is no need to convert App-V 5.0 packages to App-V for Window 10 packages.
|
||||
|
||||
For information about the differences between earlier versions of App-V, see the **Differences between App-4.6 and App-V 5.0 section** of [About App-V 5.0](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/about-app-v-50).
|
||||
When you upgrade your existing App-V environment to App-V for Windows 10, version 1607, you'll experience more flexibility, integratation, and ease of management. You can upgrade from any App-V 5.x release, however, you cannot upgrade directly from App-V 4.x to App-V for Windows 10; you must upgrade to App-V 5.x first. For more information about upgrading to App-V for Windows 10, see [Upgrading to App-V for Windows 10 from an existing installation](appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md)
|
||||
|
||||
>**Note**
|
||||
THe package format for App-V packages created with App-V 5.x has not changed in App-V for Windows 10. As a result, you don't need to convert packages.
|
||||
|
||||
## <a href="" id="bkmk-pkgconvimprove"></a>Improvements to the App-V Package Converter
|
||||
|
||||
|
@ -9,7 +9,7 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Move the App-V Server to Another Computer
|
||||
# How to move the App-V server to another computer
|
||||
|
||||
|
||||
Use the following information to create a new management server console in your environment.
|
||||
@ -17,7 +17,7 @@ Use the following information to create a new management server console in your
|
||||
## To create a new management server console
|
||||
|
||||
|
||||
The following list displays the steps necessary to create a new management server console:
|
||||
Follow these steps to create a new management server console:
|
||||
|
||||
1. Install the management server on a computer in your environment. For more information about installing the management server see [Deploying the App-V server](appv-deploying-the-appv-server.md).
|
||||
|
||||
|
@ -9,13 +9,15 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Planning to Deploy App-V
|
||||
# Planning to Deploy App-V for Windows 0
|
||||
|
||||
You should consider a number of different deployment configurations and prerequisites before you create your deployment plan for App-V. This section includes information that can help you gather the information that you must have to formulate a deployment plan that best meets your business requirements.
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
There are a number of different deployment configurations and requirements to consider before you deploy App-V for Windows 10. Review this topic for information about what you'll need to formulate a deployment plan that best meets your business requirements.
|
||||
|
||||
## App-V supported configurations
|
||||
|
||||
Describes the minimum hardware and operating system requirements for each App-V components. For information about software prerequisites that you must install before you install App-V, see [App-V Prerequisites](appv-prerequisites.md).
|
||||
Describes the minimum hardware and operating system requirements for each App-V components. For information about software that you must install before you install App-V, see [App-V Prerequisites](appv-prerequisites.md).
|
||||
|
||||
[App-V Supported Configurations](appv-supported-configurations.md)
|
||||
|
||||
|
@ -9,12 +9,13 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# App-V Prerequisites
|
||||
# App-V for Windows 10 Prerequisites
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Before installing App-V, ensure that you have installed all of the following required prerequisite software.
|
||||
Before installing App-V for Windows 10, ensure that you have installed all of the following required prerequisite software.
|
||||
|
||||
For a list of supported operating systems and hardware requirements for the App-V Server, Sequencer, and Client, see [App-V Supported Configurations](appv-supported-configurations.md).
|
||||
For a list of supported operating systems and hardware requirements for the App-V server, sequencer, and client, see [App-V Supported Configurations](appv-supported-configurations.md).
|
||||
|
||||
## Summary of software preinstalled on each operating system
|
||||
|
||||
|
@ -13,15 +13,15 @@ ms.prod: w10
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
The following is a known issue in Microsoft Application Virtualization (App-V) in Windows 10, version 1607:
|
||||
The following is a known issue in Application Virtualization (App-V) for Windows 10, version 1607:
|
||||
|
||||
**MSI packages generated by the App-V sequencer (version 5.1 and earlier) fail to install on computers with the in-box App-V client**
|
||||
**Windows Installer packages (.msi files) generated by the App-V sequencer (version 5.1 and earlier) fail to install on computers with the in-box App-V client**
|
||||
|
||||
When MSI packages are generated by an older sequencer (App-V versions 5.1 and earlier), they include a check to ensure the App-V client is installed before allowing the MSI package to install. Now that the App-V client is installed automatically when you upgrade user devices to Windows 10, version 1607, the pre-requisite check fails and causes the MSI to fail.
|
||||
MSI packages that were generated using an App-V sequencer from previous versions of App-V (App-V versions 5.1 and earlier) include a check to validate that the App-V client is installed on client devices before allowing the MSI package to install. Now that the App-V client is installed automatically when you upgrade user devices to Windows 10, version 1607, the pre-requisite check fails and causes the MSI to fail.
|
||||
|
||||
**Workaround**:
|
||||
|
||||
1. Install the latest App-V sequencer, which is part of the Windows Assessment and Deployment Kit (ADK) for Windows 10, version 1607. See [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit). For more information, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
|
||||
1. Install the latest App-V sequencer, which you can get from the Windows Assessment and Deployment Kit (ADK) for Windows 10, version 1607. See [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit). For more information, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
2. Ensure that you have installed the **MSI Tools** included in the Windows 10 SDK, available as follows:
|
||||
|
||||
@ -48,4 +48,4 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
|
||||
## Related topics
|
||||
|
||||
[About App-V](appv-about-appv.md)
|
||||
[What's new in App-V for Windows 10](appv-about-appv.md)
|
||||
|
@ -12,9 +12,9 @@ ms.prod: w10
|
||||
# About App-V Reporting
|
||||
|
||||
|
||||
Microsoft Application Virtualization (App-V) includes a built-in reporting feature that helps you collect information about computers running the App-V client as well as information about virtual application package usage. You can use this information to generate reports from a centralized database.
|
||||
Application Virtualization (App-V) includes a built-in reporting feature that helps you collect information about computers running the App-V client as well as information about virtual application package usage. You can use this information to generate reports from a centralized database.
|
||||
|
||||
## <a href="" id="---------app-v-5-1-reporting-overview"></a> App-V Reporting Overview
|
||||
## <a href="" id="---------app-v-reporting-overview"></a> App-V Reporting Overview
|
||||
|
||||
|
||||
The following list displays the end–to-end high-level workflow for reporting in App-V.
|
||||
@ -33,7 +33,7 @@ The following list displays the end–to-end high-level workflow for reporting i
|
||||
|
||||
3. If you are not using an electronic software distribution system such as Configuration Manager to view reports then you can define reports in SQL Server Reporting Service. Download predefined appvshort Reports from the Download Center at <http://go.microsoft.com/fwlink/?LinkId=397255>.
|
||||
|
||||
**Note**
|
||||
>**Note**
|
||||
If you are using the Configuration Manager integration with App-V, most reports are generated from Configuration Manager rather than from App-V.
|
||||
|
||||
|
||||
@ -52,14 +52,14 @@ The following list displays the end–to-end high-level workflow for reporting i
|
||||
|
||||
6. When the App-V client receives the success notification, it empties the data cache to conserve space.
|
||||
|
||||
**Note**
|
||||
By default the cache is cleared after the server confirms receipt of data. You can manually configure the client to save the data cache.
|
||||
>**Note**
|
||||
By default, the cache is cleared after the server confirms receipt of data. You can manually configure the client to save the data cache.
|
||||
|
||||
|
||||
|
||||
If the App-V client device does not receive a success notification from the server, it retains data in the cache and tries to resend data at the next configured interval. Clients continue to collect data and add it to the cache.
|
||||
|
||||
### <a href="" id="-------------app-v-5-1-reporting-server-frequently-asked-questions"></a> App-V reporting server frequently asked questions
|
||||
### <a href="" id="-------------app-v-reporting-server-frequently-asked-questions"></a> App-V reporting server frequently asked questions
|
||||
|
||||
The following table displays answers to common questions about App-V reporting
|
||||
|
||||
@ -124,10 +124,10 @@ The following table displays answers to common questions about App-V reporting
|
||||
|
||||
|
||||
|
||||
## <a href="" id="---------app-v-5-1-client-reporting"></a> App-V Client Reporting
|
||||
## <a href="" id="---------app-v-client-reporting"></a> App-V Client Reporting
|
||||
|
||||
|
||||
To use App-V reporting you must install and configure the App-V client. After the client has been installed, use the **Set-AppVClientConfiguration** PowerShell cmdlet or the **ADMX Template** to configure reporting. The reporting feature cmdlets are available by using the following link and are prefaced by **Reporting**. For a complete list of client configuration settings see [About Client Configuration Settings](appv-client-configuration-settings.md). The following section provides examples of App-V client reporting configuration using PowerShell.
|
||||
To use App-V reporting you must enable and configure the App-V client. After the client has been installed, use the **Set-AppVClientConfiguration** PowerShell cmdlet or the **ADMX Template** to configure reporting. The reporting feature cmdlets are available by using the following link and are prefaced by **Reporting**. For a complete list of client configuration settings see [About Client Configuration Settings](appv-client-configuration-settings.md). The following section provides examples of App-V client reporting configuration using PowerShell.
|
||||
|
||||
### Configuring App-V Client reporting using PowerShell
|
||||
|
||||
|
@ -11,12 +11,13 @@ ms.prod: w10
|
||||
|
||||
# App-V Supported Configurations
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
This topic specifies the requirements to install and run App-V in your environment.
|
||||
This topic specifies the requirements to install and run App-V in your Windows 10 environment.
|
||||
|
||||
## App-V Server system requirements
|
||||
|
||||
This section lists the operating system and hardware requirements for all of the App-V Server components.
|
||||
This section lists the operating system and hardware requirements for all of the App-V server components.
|
||||
|
||||
### Unsupported App-V server scenarios
|
||||
|
||||
|
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# Upgrading to App-V for Windows 10 from an existing installation
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
If you’re already using App-V and you’re planning to upgrade user devices to Windows 10, you need to make only the following few adjustments to your existing environment to start using App-V for Windows 10.
|
||||
|
||||
1. [Upgrade user devices to Windows 10](#upgrade-user-devices-to-windows-10). Performing an in-place upgrade automatically installs the App-V client and migrates users’ App-V applications and settings.
|
||||
|
Loading…
x
Reference in New Issue
Block a user