mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-20 09:17:25 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into sh-7610972
This commit is contained in:
Trudy Hakala
commit
86b2024779
@ -1,2 +1,4 @@
|
||||
# win-cpub-itpro-docs
|
||||
This repo hosts the WDG ITPro content that is published to TechNet.
|
||||
|
||||
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information, see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
|
||||
@ -1,6 +1,7 @@
|
||||
# [Surface](index.md)
|
||||
## [Advanced UEFI security features for Surface Pro 3](advanced-uefi-security-features-for-surface-pro-3.md)
|
||||
## [Customize the OOBE for Surface deployments](customize-the-oobe-for-surface-deployments.md)
|
||||
## [Deploy Surface app with Windows Store for Business](deploy-surface-app-with-windows-store-for-business.md)
|
||||
## [Download the latest firmware and drivers for Surface devices](deploy-the-latest-firmware-and-drivers-for-surface-devices.md)
|
||||
## [Enable PEAP, EAP-FAST, and Cisco LEAP on Surface devices](enable-peap-eap-fast-and-cisco-leap-on-surface-devices.md)
|
||||
## [Ethernet adapters and Surface deployment](ethernet-adapters-and-surface-device-deployment.md)
|
||||
|
||||
@ -0,0 +1,145 @@
|
||||
---
|
||||
title: Deploy Surface app with Windows Store for Business (Surface)
|
||||
description: Find out how to add and download Surface app with Windows Store for Business, as well as install Surface app with PowerShell and MDT.
|
||||
keywords: surface app, app, deployment, customize
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.pagetype: surface, store
|
||||
ms.sitesec: library
|
||||
author: miladCA
|
||||
---
|
||||
|
||||
#Deploy Surface app with Windows Store for Business
|
||||
|
||||
The Surface app is a lightweight Windows Store app that provides control of many Surface-specific settings and options, including:
|
||||
|
||||
* Enable or disable the Windows button on the Surface device
|
||||
|
||||
* Adjust the sensitivity of a Surface Pen
|
||||
|
||||
* Customize Surface Pen button actions
|
||||
|
||||
* Enable or disable Surface audio enhancements
|
||||
|
||||
* Quick access to support documentation and information for your device
|
||||
|
||||
If your organization is preparing images that will be deployed to your Surface devices, you may want to include the Surface app (formerly called the Surface Hub) in your imaging and deployment process instead of requiring users of each individual device to download and install the app from the Windows Store or your Windows Store for Business.
|
||||
|
||||
####Surface app overview
|
||||
|
||||
The Surface app is available as a free download from the [Windows Store](https://www.microsoft.com/en-us/store/apps/Surface/9WZDNCRFJB8P). Users can download and install it from the Windows Store, but if your organization uses Windows Store for Business instead, you will need to add it to your store’s inventory and possibly include the app as part of your Windows deployment process. These processes are discussed throughout this article. For more information about Windows Store for Business, see [Windows Store for Business](https://technet.microsoft.com/en-us/windows/store-for-business) in the Windows TechCenter.
|
||||
|
||||
##Add Surface app to a Windows Store for Business account
|
||||
|
||||
Before users can install or deploy an app from a company’s Windows Store for Business account, the desired app(s) must first be made available and licensed to the users of a business.
|
||||
|
||||
1. If you have not already done so, create a [Windows Store for Business account](https://www.microsoft.com/en-us/business-store).
|
||||
|
||||
2. Log on to the portal.
|
||||
|
||||
3. Enable offline licensing: click **Settings->Account Information**, and then select the **Show offline licensed apps to people shopping in the store** checkbox, as shown in Figure 1. For more information about Windows Store for Business app licensing models, see [Apps in Windows Store for Business](https://technet.microsoft.com/itpro/windows/manage/apps-in-windows-store-for-business#licensing_model).<br/> <br/>
|
||||
<br/>
|
||||
*Figure 1. Enable apps for offline use*
|
||||
|
||||
4. Add Surface app to your Windows Store for Business account by following this procedure:
|
||||
* Click the **Shop** menu.
|
||||
* In the search box, type **Surface app**, and then click the search icon.
|
||||
* After the Surface app is presented in the search results, click the app’s icon.
|
||||
* You are presented with a choice (select **Online** or **Offline**), as shown in Figure 2.<br/><br/>
|
||||
|
||||
|
||||
|
||||
*Figure 2. Select the Offline licensing mode and add the app to your inventory*
|
||||
|
||||
* Click **Offline** to select the Offline licensing mode.
|
||||
* Click **Get the app** to add the app to your Windows Store for Business inventory. As shown in Figure 3, you’ll see a dialog box that prompts you to acknowledge that offline apps can be deployed using a management tool or downloaded from the company’s inventory page in their private store.
|
||||
|
||||
|
||||
|
||||
*Figure 3. Offline-licensed app acknowledgement*
|
||||
* Click **OK**.
|
||||
|
||||
##Download Surface app from a Windows Store for Business account
|
||||
After you add an app to the Windows Store for Business account in Offline mode, you can download and add the app as an AppxBundle to a deployment share.
|
||||
1. Log on to the Windows Store for Business account at https://businessstore.microsoft.com.
|
||||
2. Click the **Manage->Inventory** menu. A list of all apps in your company’s private store is displayed, including the Surface app you added in the [Add Surface app to a Windows Store for Business account](#add-surface-app-to-a-windows-store-for-business-account) section of this article.
|
||||
3. Under **Actions**, click the ellipsis (**…**), and then click **Download for offline use** for the Surface app.
|
||||
4. Select the desired **Platform** and **Architecture** options from the available selections for the selected app, as shown in Figure 4.
|
||||
|
||||
|
||||
|
||||
*Figure 4. Download the AppxBundle package for an app*
|
||||
5. Click **Download**. The AppxBundle package will be downloaded. Make sure you note the path of the downloaded file because you’ll need that later in this article.
|
||||
6. Click either the **Encoded license** or **Unencoded license** option. Use the Encoded license option with management tools like System Center Configuration Manager or when you use Windows Imaging and Configuration Designer (Windows ICD). Select the Unencoded license option when you use Deployment Image Servicing and Management (DISM) or deployment solutions based on imaging, including the Microsoft Deployment Toolkit (MDT).
|
||||
7. Click **Generate** to generate and download the license for the app. Make sure you note the path of the license file because you’ll need that later in this article.
|
||||
|
||||
>**Note:** When you download an app for offline use, such as the Surface app, you may notice a section at the bottom of the page labeled **Required frameworks**. Your target computers must have the frameworks installed for the app to run, so you may need to repeat the download process for each of the required frameworks for your architecture (either x86 or x64) and also include them as part of your Windows deployment discussed later in this article.
|
||||
|
||||
Figure 5 shows the required frameworks for the Surface app.
|
||||
|
||||
|
||||
|
||||
*Figure 5. Required frameworks for the Surface app*
|
||||
|
||||
To download the required frameworks for the Surface app, follow these steps:
|
||||
1. Click the **Download** button under **Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe**. This downloads the Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe.Appx file to your specified folder.
|
||||
2. Click the **Download** button under **Microsoft.NET.Native.Runtime.1.1_1.1.23406.0_x64__8wekyb3d8bbwe**. This downloads the Microsoft.NET.Native.Runtime.1.1_1.1.23406.0_x64__8wekyb3d8bbwe.Appx file to your specified folder.
|
||||
|
||||
>**Note:** Only the 64-bit (x64) version of each framework is required for Surface devices. Surface devices are native 64-bit UEFI devices and are not compatible with 32-bit (x86) versions of Windows that would require 32-bit frameworks.
|
||||
|
||||
##Install Surface app on your computer with PowerShell
|
||||
The following procedure provisions the Surface app onto your computer and makes it available for any user accounts created on the computer afterwards.
|
||||
1. Using the procedure described in the [How to download Surface app from a Windows Store for Business account](#how-to-download-surface-app-from-a-windows-store-for-business-account) section of this article, download the Surface app AppxBundle and license file.
|
||||
2. Begin an elevated PowerShell session.
|
||||
>**Note:** If you don’t run PowerShell as an Administrator, the session won’t have the required permissions to install the app.
|
||||
3. In the elevated PowerShell session, copy and paste the following command:
|
||||
```
|
||||
Add-AppxProvisionedPackage –Online –PackagePath <DownloadPath>\ Microsoft.SurfaceHub_10.0.342.0_neutral_~_8wekyb3d8bbwe.AppxBundle –LicensePath <DownloadPath>\ Microsoft.SurfaceHub_8wekyb3d8bbwe_a53ef8ab-9dbd-dec1-46c5-7b664d4dd003.xml
|
||||
```
|
||||
|
||||
Where `<DownloadPath>` is the folder where you downloaded the AppxBundle and license file from the Windows Store for Business account.
|
||||
|
||||
For example, if you downloaded the files to c:\Temp, the command you run is:
|
||||
````
|
||||
Add-AppxProvisionedPackage –Online –PackagePath c:\Temp\ Microsoft.SurfaceHub_10.0.342.0_neutral_~_8wekyb3d8bbwe.AppxBundle –LicensePath c:\Temp\ Microsoft.SurfaceHub_8wekyb3d8bbwe_a53ef8ab-9dbd-dec1-46c5-7b664d4dd003.xml
|
||||
```
|
||||
|
||||
4. The Surface app will now be available on your current Windows computer.
|
||||
Before the Surface app is functional on the computer where it has been provisioned, you must also provision the frameworks described earlier in this article. To provision these frameworks, use the following procedure in the elevated PowerShell session you used to provision the Surface app.
|
||||
5. In the elevated PowerShell session, copy and paste the following command:
|
||||
```
|
||||
Add-AppxProvisionedPackage –Online –SkipLicense –PackagePath <DownloadPath>\Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe.Appx
|
||||
```
|
||||
6. In the elevated PowerShell session, copy and paste the following command:
|
||||
```
|
||||
Add-AppxProvisionedPackage –Online –SkipLicense –PackagePath <DownloadPath>\Microsoft.NET.Native.Runtime.1.1_1.1.23406.0_x64__8wekyb3d8bbwe.Appx
|
||||
```
|
||||
|
||||
##Install Surface app with MDT
|
||||
The following procedure uses MDT to automate installation of the Surface app at the time of deployment. The application is provisioned automatically by MDT during deployment and thus you can use this process with existing images. This is the recommended process to deploy the Surface app as part of a Windows deployment to Surface devices because it does not reduce the cross platform compatibility of the Windows image.
|
||||
1. Using the procedure described [earlier in this article](#how-to-download-surface-app-from-a-windows-store-for-business-account), download the Surface app AppxBundle and license file.
|
||||
2. Using the New Application Wizard in the MDT Deployment Workbench, import the downloaded files as a new **Application with source files**.
|
||||
3. On the **Command Details** page of the New Application Wizard, specify the default **Working Directory** and for the **Command** specify the file name of the AppxBundle, as follows:
|
||||
|
||||
* Command:
|
||||
```
|
||||
Microsoft.SurfaceHub_10.0.342.0_neutral_~_8wekyb3d8bbwe.AppxBundle
|
||||
```
|
||||
* Working Directory: %DEPLOYROOT%\Applications\SurfaceApp
|
||||
|
||||
For the Surface app to function on the target computer, it will also require the frameworks described earlier in this article. Use the following procedure to import the frameworks required for the Surface app into MDT and to configure them as dependencies.
|
||||
1. Using the procedure described earlier in this article, download the framework files. Store each framework in a separate folder.
|
||||
2. Using the New Application Wizard in the MDT Deployment Workbench, import the downloaded files as a new **Application with source files**.
|
||||
3. On the **Command Details** page, type the file name of each application you downloaded in the **Command** field and the default Working Directory.
|
||||
|
||||
To configure the frameworks as dependencies of the Surface app, use this process:
|
||||
1. Open the properties of the Surface app in the MDT Deployment Workbench.
|
||||
2. Click the **Dependencies** tab, and then click **Add**.
|
||||
3. Select the check box for each framework using the name you provided in the New Application Wizard.
|
||||
|
||||
After import, the Surface app will be available for selection in the **Applications** step of the Windows Deployment Wizard. You can also install the application automatically by specifying the application in the deployment task sequence by following this process:
|
||||
1. Open your deployment task sequence in the MDT Deployment Workbench.
|
||||
2. Add a new **Install Application** task in the **State Restore** section of deployment.
|
||||
3. Select **Install a single application** and specify the **Surface App** as the **Application to be installed**.
|
||||
|
||||
For more information about including apps into your Windows deployments, see [Deploy Windows 10 with the Microsoft Deployment Toolkit](https://technet.microsoft.com/en-us/itpro/windows/deploy/deploy-windows-10-with-the-microsoft-deployment-toolkit).
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 106 KiB |
BIN
devices/surface/images/deploysurfapp-fig3-acknowledge.png
Normal file
BIN
devices/surface/images/deploysurfapp-fig3-acknowledge.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
BIN
devices/surface/images/deploysurfapp-fig4-downloadappxbundle.png
Normal file
BIN
devices/surface/images/deploysurfapp-fig4-downloadappxbundle.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 79 KiB |
BIN
devices/surface/images/deploysurfapp-fig5-requiredframework.png
Normal file
BIN
devices/surface/images/deploysurfapp-fig5-requiredframework.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 50 KiB |
BIN
devices/surface/images/deploysurfapp-figure1-enablingapps.png
Normal file
BIN
devices/surface/images/deploysurfapp-figure1-enablingapps.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 7.7 KiB |
@ -43,42 +43,46 @@ For more information on planning for, deploying, and managing Surface devices in
|
||||
<td><p>Walk through the process of customizing the Surface out-of-box experience for end users in your organization.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td><p>[Deploy Surface app with Windows Store for Business](deploy-surface-app-with-windows-store-for-business.md)</p></td>
|
||||
<td><p>Find out how to add and download Surface app with Windows Store for Business, as well as install Surface app with PowerShell and MDT.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td><p>[Download the latest firmware and drivers for Surface devices](deploy-the-latest-firmware-and-drivers-for-surface-devices.md)</p></td>
|
||||
<td><p>Get a list of the available downloads for Surface devices and links to download the drivers and firmware for your device.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<tr class="odd">
|
||||
<td><p>[Enable PEAP, EAP-FAST, and Cisco LEAP on Surface devices](enable-peap-eap-fast-and-cisco-leap-on-surface-devices.md)</p></td>
|
||||
<td><p>Find out how to enable support for PEAP, EAP-FAST, or Cisco LEAP protocols on your Surface device.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<tr class="even">
|
||||
<td><p>[Ethernet adapters and Surface deployment](ethernet-adapters-and-surface-device-deployment.md)</p></td>
|
||||
<td><p>Get guidance and answers to help you perform a network deployment to Surface devices.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<tr class="odd">
|
||||
<td><p>[Manage Surface Dock firmware updates](manage-surface-dock-firmware-updates.md)</p></td>
|
||||
<td><p>Read about the different methods you can use to manage the process of Surface Dock firmware updates.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<tr class="even">
|
||||
<td><p>[Manage Surface driver and firmware updates](manage-surface-pro-3-firmware-updates.md)</p></td>
|
||||
<td><p>Explore the available options to manage firmware and driver updates for Surface devices.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<tr class="odd">
|
||||
<td><p>[Manage Surface UEFI settings](manage-surface-uefi-settings.md)<p></td>
|
||||
<td><p>Use Surface UEFI settings to enable or disable devices, configure security settings, and adjust Surface device boot settings.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<tr class="even">
|
||||
<td><p>[Surface Data Eraser](microsoft-surface-data-eraser.md)</p></td>
|
||||
<td><p>Find out how the Microsoft Surface Data Eraser tool can help you securely wipe data from your Surface devices.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<tr class="odd">
|
||||
<td><p>[Surface Deployment Accelerator](microsoft-surface-deployment-accelerator.md)</p></td>
|
||||
<td><p>See how Microsoft Surface Deployment Accelerator provides a quick and simple deployment mechanism for organizations to reimage Surface devices.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<tr class="even">
|
||||
<td><p>[Surface Diagnostic Toolkit](surface-diagnostic-toolkit.md)</p></td>
|
||||
<td><p>Find out how you can use the Microsoft Surface Diagnostic Toolkit to test the hardware of your Surface device.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<tr class="odd">
|
||||
<td><p>[Surface Dock Updater](surface-dock-updater.md)</p></td>
|
||||
<td><p>Get a detailed walkthrough of Microsoft Surface Dock Updater.</p></td>
|
||||
</tr>
|
||||
|
||||
@ -25,7 +25,7 @@
|
||||
#### [Deploying the App-V 5.1 Sequencer and Client](deploying-the-app-v-51-sequencer-and-client.md)
|
||||
##### [How to Deploy the App-V Client](how-to-deploy-the-app-v-client-51gb18030.md)
|
||||
##### [About Client Configuration Settings 5.1](about-client-configuration-settings51.md)
|
||||
##### [How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46x-and-the-app-v--51-client-on-the-same-computer.md)
|
||||
##### [How to Deploy the App-V 4.6 and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--51-client-on-the-same-computer.md)
|
||||
##### [How to Install the App-V 5.1 Client for Shared Content Store Mode](how-to-install-the-app-v-51-client-for-shared-content-store-mode.md)
|
||||
##### [How to Install the Sequencer](how-to-install-the-sequencer-51beta-gb18030.md)
|
||||
##### [How to Modify App-V 5.1 Client Configuration Using the ADMX Template and Group Policy](how-to-modify-app-v-51-client-configuration-using-the-admx-template-and-group-policy.md)
|
||||
@ -81,11 +81,10 @@
|
||||
#### [Migrating to App-V 5.1 from a Previous Version](migrating-to-app-v-51-from-a-previous-version.md)
|
||||
##### [Check Registry Keys before installing App-V 5.x Server](check-reg-key-svr.md)
|
||||
##### [How to Convert a Package Created in a Previous Version of App-V 5.1](how-to-convert-a-package-created-in-a-previous-version-of-app-v51.md)
|
||||
##### [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md)
|
||||
##### [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-51-for-a-specific-user.md)
|
||||
##### [How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-all-users-on-a-specific-computer.md)
|
||||
##### [How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-a-specific-user.md)
|
||||
##### [How to Use an App-V 4.6 SP1 Application From an App-V 5.1 Application](how-to-use-an-app-v-46-sp1-application-from-an-app-v-51-application.md)
|
||||
##### [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md)
|
||||
##### [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-51-for-a-specific-user.md)
|
||||
##### [How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-package-for-all-users-on-a-specific-computer.md)
|
||||
##### [How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-package-for-a-specific-user.md)
|
||||
#### [Maintaining App-V 5.1](maintaining-app-v-51.md)
|
||||
##### [How to Move the App-V Server to Another Computer 5.1](how-to-move-the-app-v-server-to-another-computer51.md)
|
||||
#### [Administering App-V 5.1 by Using PowerShell](administering-app-v-51-by-using-powershell.md)
|
||||
@ -141,7 +140,7 @@
|
||||
#### [Deploying the App-V 5.0 Sequencer and Client](deploying-the-app-v-50-sequencer-and-client.md)
|
||||
##### [How to Deploy the App-V Client](how-to-deploy-the-app-v-client-gb18030.md)
|
||||
##### [About Client Configuration Settings](about-client-configuration-settings.md)
|
||||
##### [How to Deploy the App-V 4.6.x and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46x-and-the-app-v--50-client-on-the-same-computer.md)
|
||||
##### [How to Deploy the App-V 4.6 and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--50-client-on-the-same-computer.md)
|
||||
##### [How to Install the App-V 5.0 Client for Shared Content Store Mode](how-to-install-the-app-v-50-client-for-shared-content-store-mode.md)
|
||||
##### [How to Install the Sequencer](how-to-install-the-sequencer-beta-gb18030.md)
|
||||
##### [How to Modify App-V 5.0 Client Configuration Using the ADMX Template and Group Policy](how-to-modify-app-v-50-client-configuration-using-the-admx-template-and-group-policy.md)
|
||||
@ -196,11 +195,10 @@
|
||||
##### [How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server](how-to-configure-the-client-to-receive-package-and-connection-groups-updates-from-the-publishing-server-beta.md)
|
||||
#### [Migrating from a Previous Version](migrating-from-a-previous-version-app-v-50.md)
|
||||
##### [How to Convert a Package Created in a Previous Version of App-V](how-to-convert-a-package-created-in-a-previous-version-of-app-v.md)
|
||||
##### [How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md)
|
||||
##### [How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-50-for-a-specific-user.md)
|
||||
##### [How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 SP2 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-sp2-package-for-all-users-on-a-specific-computer.md)
|
||||
##### [How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 SP2 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-sp2-package-for-a-specific-user.md)
|
||||
##### [How to Use an App-V 4.6 SP1 Application From an App-V 5.0 Application](how-to-use-an-app-v-46-sp1-application-from-an-app-v-50-application.md)
|
||||
##### [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md)
|
||||
##### [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-50-for-a-specific-user.md)
|
||||
##### [How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-package-for-all-users-on-a-specific-computer.md)
|
||||
##### [How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-package-for-a-specific-user.md)
|
||||
#### [Maintaining App-V 5.0](maintaining-app-v-50.md)
|
||||
##### [How to Move the App-V Server to Another Computer](how-to-move-the-app-v-server-to-another-computer.md)
|
||||
#### [Administering App-V by Using PowerShell](administering-app-v-by-using-powershell.md)
|
||||
|
||||
@ -34,7 +34,7 @@ The following list displays what is new with App-V 5.0:
|
||||
|
||||
- **Connection Groups** - App-V 5.0 connection groups allow you to connect and run virtual applications interactively.
|
||||
|
||||
## <a href="" id="bkmk-diff-46-50"></a>Differences between App-4.6 and App-V 5.0
|
||||
## <a href="" id="bkmk-diff-46-50"></a>Differences between App-V 4.6 and App-V 5.0
|
||||
|
||||
|
||||
The following table displays some of the differences between App-V 4.6 and App-V 5.0:
|
||||
|
||||
@ -449,6 +449,8 @@ The App-V client supports the following versions of System Center Configuration
|
||||
|
||||
The following App-V and System Center Configuration Manager version matrix shows all officially supported combinations of App-V and Configuration Manager.
|
||||
|
||||
**Note:** Both App-V 4.5 and 4.6 have exited Mainstream support.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="12%" />
|
||||
@ -474,130 +476,6 @@ The following App-V and System Center Configuration Manager version matrix shows
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.5</p></td>
|
||||
<td align="left"><p>R2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.5 CU1</p></td>
|
||||
<td align="left"><p>R2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.5 SP1</p></td>
|
||||
<td align="left"><p>R2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.5 SP2</p></td>
|
||||
<td align="left"><p>R2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6</p></td>
|
||||
<td align="left"><p>R2, SP1</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP1</p></td>
|
||||
<td align="left"><p>R2, R3, SP2</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP2</p></td>
|
||||
<td align="left"><p>R2, R3, SP2</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>R2, R3, SP2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 5.0</p></td>
|
||||
<td align="left"><p>MSI-Wrapper-Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 5.0 SP1</p></td>
|
||||
<td align="left"><p>MSI-Wrapper Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 5.0 SP2</p></td>
|
||||
<td align="left"><p>MSI-Wrapper Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>2012 SP1 CU4</p>
|
||||
<p>App-V 5.0 HF5 or later</p></td>
|
||||
<td align="left"><p>2012 R2 CU1</p>
|
||||
<p>App-V 5.0 HF5 or later</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>With App-V 5.0 SP2 HF5 or later</p></td>
|
||||
<td align="left"><p>With App-V 5.0 SP2 HF5 or later</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 5.0 SP2 HF4</p></td>
|
||||
<td align="left"><p>MSI-Wrapper Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>2012 SP1 CU4</p>
|
||||
<p>App-V 5.0 HF5 or later</p></td>
|
||||
<td align="left"><p>2012 R2 CU1</p>
|
||||
<p>App-V 5.0 HF5 or later</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Requires HF5 or later</p></td>
|
||||
<td align="left"><p>Requires HF5 or later</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 5.0 SP3</p></td>
|
||||
<td align="left"><p>MSI-Wrapper Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
|
||||
@ -24,7 +24,7 @@ The App-V 5.0 client is the component that runs a virtualized application on a t
|
||||
|
||||
[How to Uninstall the App-V 5.0 Client](how-to-uninstall-the-app-v-50-client.md)
|
||||
|
||||
[How to Deploy the App-V 4.6.x and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46x-and-the-app-v--50-client-on-the-same-computer.md)
|
||||
[How to Deploy the App-V 4.6 and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--50-client-on-the-same-computer.md)
|
||||
|
||||
## Client Configuration Settings
|
||||
|
||||
|
||||
@ -24,7 +24,7 @@ The App-V 5.1 client is the component that runs a virtualized application on a t
|
||||
|
||||
[How to Uninstall the App-V 5.1 Client](how-to-uninstall-the-app-v-51-client.md)
|
||||
|
||||
[How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46x-and-the-app-v--51-client-on-the-same-computer.md)
|
||||
[How to Deploy the App-V 4.6 and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--51-client-on-the-same-computer.md)
|
||||
|
||||
## Client Configuration Settings
|
||||
|
||||
|
||||
@ -0,0 +1,54 @@
|
||||
---
|
||||
title: How to Deploy the App-V 4.6 and the App-V 5.0 Client on the Same Computer
|
||||
description: How to Deploy the App-V 4.6 and the App-V 5.0 Client on the Same Computer
|
||||
ms.assetid: 5b7e27e4-4360-464c-b832-f1c7939e5485
|
||||
author: jamiejdt
|
||||
---
|
||||
|
||||
# How to Deploy the App-V 4.6 and the App-V 5.0 Client on the Same Computer
|
||||
|
||||
**Note:** App-V 4.6 has exited Mainstream support. The following assumes that the App-V 4.6 SP3 client is already installed.
|
||||
|
||||
Use the following information to install the App-V 5.0 client (preferably, with the latest Service Packs and hotfixes) and the App-V 4.6 SP3 client on the same computer. For supported versions, requirements, and other planning information, see [Planning for Migrating from a Previous Version of App-V](planning-for-migrating-from-a-previous-version-of-app-v.md).
|
||||
|
||||
**To deploy the App-V 5.0 client and App-V 4.6 client on the same computer**
|
||||
|
||||
1. Install the App-V 5.0 SP3 client on the computer that is running the App-V 4.6 version of the client. For best results, we recommend that you install all available updates to the App-V 5.0 SP3 client.
|
||||
|
||||
2. Convert or re-sequence the packages gradually.
|
||||
|
||||
- To convert the packages, use the App-V 5.0 package converter and convert the required packages to the App-V 5.0 (**.appv**) file format.
|
||||
|
||||
- To re-sequence the packages, consider using the latest version of the Sequencer for best results.
|
||||
|
||||
For more information about publishing packages, see [How to Publish a Package by Using the Management Console](how-to-publish-a-package-by-using-the-management-console-50.md).
|
||||
|
||||
3. Deploy packages to the client computers.
|
||||
|
||||
4. Convert extension points, as needed. For more information, see the following resources:
|
||||
|
||||
- [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md)
|
||||
|
||||
- [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-50-for-a-specific-user.md)
|
||||
|
||||
- [How to Convert a Package Created in a Previous Version of App-V](how-to-convert-a-package-created-in-a-previous-version-of-app-v.md)
|
||||
|
||||
5. Test that your App-V 5.0 packages are successful, and then remove the 4.6 packages. To check the user state of your client computers, we recommend that you use [User Experience Virtualization](http://technet.microsoft.com/library/dn458947.aspx) or another user environment management tool.
|
||||
|
||||
**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issu**e? Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Planning for Migrating from a Previous Version of App-V](planning-for-migrating-from-a-previous-version-of-app-v.md)
|
||||
|
||||
[Deploying the App-V 5.0 Sequencer and Client](deploying-the-app-v-50-sequencer-and-client.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,29 +1,27 @@
|
||||
---
|
||||
title: How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer
|
||||
description: How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer
|
||||
author: jamiejdt
|
||||
title: How to Deploy the App-V 4.6 and the App-V 5.1 Client on the Same Computer
|
||||
description: How to Deploy the App-V 4.6 and the App-V 5.1 Client on the Same Computer
|
||||
ms.assetid: 498d50c7-f13d-4fbb-8ea1-b959ade26fdf
|
||||
author: jamiejdt
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Deploy the App-V 4.6 and the App-V 5.1 Client on the Same Computer
|
||||
|
||||
# How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer
|
||||
|
||||
**Note:** App-V 4.6 has exited Mainstream support.
|
||||
|
||||
Use the following information to install the Microsoft Application Virtualization (App-V) 5.1 client (preferably, with the latest Service Packs and hotfixes) and the App-V 4.6 SP2 client or the App-V 4.6 S3 client on the same computer. For supported versions, requirements, and other planning information, see [Planning for Migrating from a Previous Version of App-V](planning-for-migrating-from-a-previous-version-of-app-v51.md).
|
||||
|
||||
**To deploy the App-V 5.1 client and App-V 4.6.x client on the same computer**
|
||||
**To deploy the App-V 5.1 client and App-V 4.6 client on the same computer**
|
||||
|
||||
1. Install one of the following versions of the App-V client on the computer that is running App-V 4.6.
|
||||
|
||||
- [Microsoft Application Virtualization 4.6 Service Pack 2](http://go.microsoft.com/fwlink/?LinkId=262687)
|
||||
1. Install the following version of the App-V client on the computer that is running App-V 4.6.
|
||||
|
||||
- [Microsoft Application Virtualization 4.6 Service Pack 3](http://www.microsoft.com/download/details.aspx?id=41187)
|
||||
|
||||
2. Install the App-V 5.1 client on the computer that is running the App-V 4.6 SP2 or 4.6 SP3 version of the client. For best results, we recommend that you install all available updates to the App-V 5.1 client.
|
||||
2. Install the App-V 5.1 client on the computer that is running the App-V 4.6 SP3 version of the client. For best results, we recommend that you install all available updates to the App-V 5.1 client.
|
||||
|
||||
3. Convert or re-sequence the packages gradually.
|
||||
|
||||
@ -37,9 +35,9 @@ Use the following information to install the Microsoft Application Virtualizatio
|
||||
|
||||
5. Convert extension points, as needed. For more information, see the following resources:
|
||||
|
||||
- [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md)
|
||||
- [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md)
|
||||
|
||||
- [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-51-for-a-specific-user.md)
|
||||
- [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-51-for-a-specific-user.md)
|
||||
|
||||
- [How to Convert a Package Created in a Previous Version of App-V](how-to-convert-a-package-created-in-a-previous-version-of-app-v51.md)
|
||||
|
||||
@ -1,64 +0,0 @@
|
||||
---
|
||||
title: How to Deploy the App-V 4.6.x and the App-V 5.0 Client on the Same Computer
|
||||
description: How to Deploy the App-V 4.6.x and the App-V 5.0 Client on the Same Computer
|
||||
author: jamiejdt
|
||||
ms.assetid: 5b7e27e4-4360-464c-b832-f1c7939e5485
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Deploy the App-V 4.6.x and the App-V 5.0 Client on the Same Computer
|
||||
|
||||
|
||||
Use the following information to install the App-V 5.0 client (preferably, with the latest Service Packs and hotfixes) and the App-V 4.6 SP2 client or the App-V 4.6 S3 client on the same computer. For supported versions, requirements, and other planning information, see [Planning for Migrating from a Previous Version of App-V](planning-for-migrating-from-a-previous-version-of-app-v.md).
|
||||
|
||||
**To deploy the App-V 5.0 client and App-V 4.6.x client on the same computer**
|
||||
|
||||
1. Install one of the following versions of the App-V client on the computer that is running App-V 4.6.
|
||||
|
||||
- [Microsoft Application Virtualization 4.6 Service Pack 2](http://go.microsoft.com/fwlink/?LinkId=262687)
|
||||
|
||||
- [Microsoft Application Virtualization 4.6 Service Pack 3](http://www.microsoft.com/download/details.aspx?id=41187)
|
||||
|
||||
2. Install the App-V 5.0 client on the computer that is running the App-V 4.6 SP2 or 4.6 SP3 version of the client. For best results, we recommend that you install all available updates to the App-V 5.0 client.
|
||||
|
||||
3. Convert or re-sequence the packages gradually.
|
||||
|
||||
- To convert the packages, use the App-V 5.0 package converter and convert the required packages to the App-V 5.0 (**.appv**) file format.
|
||||
|
||||
- To re-sequence the packages, consider using the latest version of the Sequencer for best results.
|
||||
|
||||
For more information about publishing packages, see [How to Publish a Package by Using the Management Console](how-to-publish-a-package-by-using-the-management-console-50.md).
|
||||
|
||||
4. Deploy packages to the client computers.
|
||||
|
||||
5. Convert extension points, as needed. For more information, see the following resources:
|
||||
|
||||
- [How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md)
|
||||
|
||||
- [How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-50-for-a-specific-user.md)
|
||||
|
||||
- [How to Convert a Package Created in a Previous Version of App-V](how-to-convert-a-package-created-in-a-previous-version-of-app-v.md)
|
||||
|
||||
6. Test that your App-V 5.0 packages are successful, and then remove the 4.6 packages. To check the user state of your client computers, we recommend that you use [User Experience Virtualization](http://technet.microsoft.com/library/dn458947.aspx) or another user environment management tool.
|
||||
|
||||
**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issu**e? Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Planning for Migrating from a Previous Version of App-V](planning-for-migrating-from-a-previous-version-of-app-v.md)
|
||||
|
||||
[Deploying the App-V 5.0 Sequencer and Client](deploying-the-app-v-50-sequencer-and-client.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,26 +1,26 @@
|
||||
---
|
||||
title: How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer
|
||||
description: How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer
|
||||
author: jamiejdt
|
||||
title: How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer
|
||||
description: How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer
|
||||
ms.assetid: 3ae9996f-71d9-4ca1-9aab-25b599158e55
|
||||
author: jamiejdt
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer
|
||||
|
||||
# How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer
|
||||
**Note:** App-V 4.6 has exited Mainstream support.
|
||||
|
||||
|
||||
Use the following procedure to migrate extension points from an App-V 4.6 SP2 package to a App-V 5.0 package using the deployment configuration file.
|
||||
Use the following procedure to migrate extension points from an App-V 4.6 package to a App-V 5.0 package using the deployment configuration file.
|
||||
|
||||
**Note**
|
||||
The following procedure does not require an App-V 5.0 management server.
|
||||
|
||||
|
||||
|
||||
**To migrate extension points from a package from an App-V 4.6 SP2 package to a converted App-V 5.0 package using the deployment configuration file**
|
||||
**To migrate extension points from a package from an App-V 4.6 package to a converted App-V 5.0 package using the deployment configuration file**
|
||||
|
||||
1. Locate the directory that contains the deployment configuration file for the package you want to migrate. To set the policy, make the following update to the **userConfiguration** section:
|
||||
|
||||
@ -52,14 +52,14 @@ The following procedure does not require an App-V 5.0 management server.
|
||||
|
||||
PS>**Publish-AppVClientPackage $pkg**
|
||||
|
||||
3. To test the migration, open the virtual application using asscoaited FTAs or shortcuts. The application opens with App-V 5.0. Both, the App-V 4.6 SP2 package and the converted App-V 5.0 package are published to the user, but the FTAs and shortcuts for the applications have been assumed by the App-V 5.0 package.
|
||||
3. To test the migration, open the virtual application using asscoaited FTAs or shortcuts. The application opens with App-V 5.0. Both, the App-V 4.6 package and the converted App-V 5.0 package are published to the user, but the FTAs and shortcuts for the applications have been assumed by the App-V 5.0 package.
|
||||
|
||||
**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issu**e? Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 SP2 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-sp2-package-for-all-users-on-a-specific-computer.md)
|
||||
[How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-package-for-all-users-on-a-specific-computer.md)
|
||||
|
||||
[Operations for App-V 5.0](operations-for-app-v-50.md)
|
||||
|
||||
@ -60,7 +60,7 @@ The following procedure does not require an App-V 5.1 management server.
|
||||
## Related topics
|
||||
|
||||
|
||||
[How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-all-users-on-a-specific-computer.md)
|
||||
[How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-package-for-all-users-on-a-specific-computer.md)
|
||||
|
||||
[Operations for App-V 5.1](operations-for-app-v-51.md)
|
||||
|
||||
@ -1,17 +1,17 @@
|
||||
---
|
||||
title: How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.0 for a Specific User
|
||||
description: How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.0 for a Specific User
|
||||
author: jamiejdt
|
||||
title: How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User
|
||||
description: How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User
|
||||
ms.assetid: dad25992-3c75-4b7d-b4c6-c2edf43baaea
|
||||
author: jamiejdt
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User
|
||||
|
||||
# How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.0 for a Specific User
|
||||
|
||||
*Note:** App-V 4.6 has exited Mainstream support.
|
||||
|
||||
Use the following procedure to migrate packages created with App-V using the user configuration file.
|
||||
|
||||
@ -51,7 +51,7 @@ This procedure assumes that you are running the latest version of App-V 4.6.
|
||||
|
||||
[Operations for App-V 5.1](operations-for-app-v-51.md)
|
||||
|
||||
[How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-a-specific-user.md)
|
||||
[How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-package-for-a-specific-user.md)
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,7 @@
|
||||
---
|
||||
title: How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 SP2 Package for a Specific User
|
||||
description: How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 SP2 Package for a Specific User
|
||||
title: How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 Package for a Specific User
|
||||
description: How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 Package for a Specific User
|
||||
ms.assetid: f1d2ab1f-0831-4976-b49f-169511d3382a
|
||||
author: jamiejdt
|
||||
ms.assetid: f1d2ab1f-0831-4976-b49f-169511d3382a
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -9,15 +10,15 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 Package for a Specific User
|
||||
|
||||
# How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 SP2 Package for a Specific User
|
||||
|
||||
*Note:** App-V 4.6 has exited Mainstream support.
|
||||
|
||||
Use the following procedure to revert an App-V 5.0 package to the App-V file format using the user configuration file.
|
||||
|
||||
**To revert a package**
|
||||
|
||||
1. Ensure that App-V 4.6 SP2 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.0 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-50-for-a-specific-user.md).
|
||||
1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.0 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-50-for-a-specific-user.md).
|
||||
|
||||
In the **userConfiguration** section of the deployment configuration file for the converted package, to set the policy, make the following update to the **userConfiguration** section: **ManagingAuthority TakeoverExtensionPointsFrom46="false" PackageName=<Package ID>**
|
||||
|
||||
@ -25,7 +26,7 @@ Use the following procedure to revert an App-V 5.0 package to the App-V file for
|
||||
|
||||
PS>**Publish-AppVClientPackage $pkg –DynamicUserConfigurationPath** <path to user configuration file>
|
||||
|
||||
3. Perform a publishing refresh, or wait for the next scheduled publishing refresh for the App-V 4.6 SP2. Open the application using FTAs or shortcuts. The Application should now open using App-V 4.6 SP2.
|
||||
3. Perform a publishing refresh, or wait for the next scheduled publishing refresh for the App-V 4.6. Open the application using FTAs or shortcuts. The Application should now open using App-V 4.6 SP2.
|
||||
|
||||
**Note**
|
||||
If you do not need the App-V 5.0 package anymore, you can unpublish the App-V 5.0 package and the extension points will automatically revert to App-V 4.6.
|
||||
@ -1,23 +1,23 @@
|
||||
---
|
||||
title: How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 SP2 Package For All Users on a Specific Computer
|
||||
description: How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 SP2 Package For All Users on a Specific Computer
|
||||
author: jamiejdt
|
||||
title: How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 Package For All Users on a Specific Computer
|
||||
description: How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 Package For All Users on a Specific Computer
|
||||
ms.assetid: 2a43ca1b-6847-4dd1-ade2-336ac4ac6af0
|
||||
author: jamiejdt
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 Package For All Users on a Specific Computer
|
||||
|
||||
# How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 SP2 Package For All Users on a Specific Computer
|
||||
*Note:** App-V 4.6 has exited Mainstream support. The following assumes that the App-V 4.6 SP3 client is already installed.
|
||||
|
||||
|
||||
Use the following procedure to revert extension points from an App-V 5.0 package to the App-V 4.6 SP2 file format using the deployment configuration file.
|
||||
Use the following procedure to revert extension points from an App-V 5.0 package to the App-V 4.6 file format using the deployment configuration file.
|
||||
|
||||
**To revert a package**
|
||||
|
||||
1. Ensure that App-V 4.6 SP2 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.0 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md).
|
||||
1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.0 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md).
|
||||
|
||||
In the **userConfiguration** section of the deployment configuration file for the converted package, to set the policy, make the following update to the **userConfiguration** section: **ManagingAuthority TakeoverExtensionPointsFrom46="false" PackageName=<Package ID>**
|
||||
|
||||
@ -29,7 +29,7 @@ Use the following procedure to revert extension points from an App-V 5.0 package
|
||||
|
||||
3. Perform a publishing refresh, or wait for the next scheduled publishing refresh for the App-V 4.6 SP2 package.
|
||||
|
||||
Open the application using FTAs or shortcuts. The Application should now open using App-V 4.6 SP2.
|
||||
Open the application using FTAs or shortcuts. The Application should now open using App-V 4.6.
|
||||
|
||||
**Note**
|
||||
If you do not need the App-V 5.0 package anymore, you can unpublish the App-V 5.0 package and the extension points will automatically revert to App-V 4.6.
|
||||
@ -17,7 +17,7 @@ Use the following procedure to revert an App-V 5.1 package to the App-V file for
|
||||
|
||||
**To revert a package**
|
||||
|
||||
1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.1 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-51-for-a-specific-user.md).
|
||||
1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.1 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-51-for-a-specific-user.md).
|
||||
|
||||
In the **userConfiguration** section of the deployment configuration file for the converted package, to set the policy, make the following update to the **userConfiguration** section: **ManagingAuthority TakeoverExtensionPointsFrom46="false" PackageName=<Package ID>**
|
||||
|
||||
@ -17,7 +17,7 @@ Use the following procedure to revert extension points from an App-V 5.1 package
|
||||
|
||||
**To revert a package**
|
||||
|
||||
1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.1 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md).
|
||||
1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.1 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md).
|
||||
|
||||
In the **userConfiguration** section of the deployment configuration file for the converted package, to set the policy, make the following update to the **userConfiguration** section: **ManagingAuthority TakeoverExtensionPointsFrom46="false" PackageName=<Package ID>**
|
||||
|
||||
@ -1,6 +1,7 @@
|
||||
---
|
||||
title: How to Use an App-V 4.6 SP1 Application From an App-V 5.0 Application
|
||||
description: How to Use an App-V 4.6 SP1 Application From an App-V 5.0 Application
|
||||
title: How to Use an App-V 4.6 Application From an App-V 5.0 Application
|
||||
description: How to Use an App-V 4.6 Application From an App-V 5.0 Application
|
||||
ms.assetid: 4e78cb32-9c8b-478e-ae8b-c474a7e42487
|
||||
author: jamiejdt
|
||||
ms.assetid: 4e78cb32-9c8b-478e-ae8b-c474a7e42487
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -9,21 +10,21 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Use an App-V 4.6 Application From an App-V 5.0 Application
|
||||
|
||||
# How to Use an App-V 4.6 SP1 Application From an App-V 5.0 Application
|
||||
*Note:** App-V 4.6 has exited Mainstream support. The following applies to an App-V 4.6 SP3 package.
|
||||
|
||||
|
||||
Use the following procedure to run an App-V 4.6 SP2 application with App-V 5.0 applications on a standalone client.
|
||||
Use the following procedure to run an App-V 4.6 application with App-V 5.0 applications on a standalone client.
|
||||
|
||||
**To run applications on a standalone client**
|
||||
|
||||
1. Select two applications in your environment that can be opened from one another. For example, Microsoft Outlook and Adobe Acrobat Reader. You can access an email attachment created using Adobe Acrobat.
|
||||
|
||||
2. Convert the packages, or create a new package for either of the applications using the App-V 5.0 format. For more information about converting packages see, [How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md) or [How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-50-for-a-specific-user.md).
|
||||
2. Convert the packages, or create a new package for either of the applications using the App-V 5.0 format. For more information about converting packages see, [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md) or [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-50-for-a-specific-user.md).
|
||||
|
||||
3. Add and provision the package using the App-V 5.0 management console. For more information adding and provisioning packages see, [How to Add or Upgrade Packages by Using the Management Console](how-to-add-or-upgrade-packages-by-using-the-management-console-beta-gb18030.md) and [How to Configure Access to Packages by Using the Management Console](how-to-configure-access-to-packages-by-using-the-management-console-50.md).
|
||||
|
||||
4. The converted application now runs using App-V 5.0 and you can open one application from the other. For example, if you converted a Microsoft Office package to an App-V 5.0 package and Adobe Acrobat is still running as an App-V 4.6 SP2 package, you can open an Adobe Acrobat Reader attachment using Microsoft Outlook.
|
||||
4. The converted application now runs using App-V 5.0 and you can open one application from the other. For example, if you converted a Microsoft Office package to an App-V 5.0 package and Adobe Acrobat is still running as an App-V 4.6 package, you can open an Adobe Acrobat Reader attachment using Microsoft Outlook.
|
||||
|
||||
**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issu**e? Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
|
||||
|
||||
@ -12,6 +12,7 @@ ms.prod: w10
|
||||
|
||||
# How to Use an App-V 4.6 Application From an App-V 5.1 Application
|
||||
|
||||
*Note:** App-V 4.6 has exited Mainstream support. The following applies to an App-V 4.6 SP3 package.
|
||||
|
||||
Use the following procedure to run an App-V 4.6 application with App-V 5.1 applications on a standalone client.
|
||||
|
||||
@ -22,7 +23,7 @@ This procedure assumes that you are running the latest version of App-V 4.6.
|
||||
|
||||
1. Select two applications in your environment that can be opened from one another. For example, Microsoft Outlook and Adobe Acrobat Reader. You can access an email attachment created using Adobe Acrobat.
|
||||
|
||||
2. Convert the packages, or create a new package for either of the applications using the App-V 5.1 format. For more information about converting packages see, [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md) or [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-51-for-a-specific-user.md).
|
||||
2. Convert the packages, or create a new package for either of the applications using the App-V 5.1 format. For more information about converting packages see, [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md) or [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-51-for-a-specific-user.md).
|
||||
|
||||
3. Add and provision the package using the App-V 5.1 management console. For more information adding and provisioning packages see, [How to Add or Upgrade Packages by Using the Management Console](how-to-add-or-upgrade-packages-by-using-the-management-console-51-gb18030.md) and [How to Configure Access to Packages by Using the Management Console](how-to-configure-access-to-packages-by-using-the-management-console-51.md).
|
||||
|
||||
|
||||
@ -18,7 +18,7 @@ With App-V 5.0 you can migrate your existing App-V 4.6 infrastructure to the mor
|
||||
Consider the following sections when you plan your migration strategy:
|
||||
|
||||
**Note**
|
||||
For more information about the differences between App-V 4.6 and App-V 5.0, see the **Differences between App-4.6 and App-V 5.0 section** of [About App-V 5.0](about-app-v-50.md).
|
||||
For more information about the differences between App-V 4.6 and App-V 5.0, see the **Differences between App-V 4.6 and App-V 5.0 section** of [About App-V 5.0](about-app-v-50.md).
|
||||
|
||||
|
||||
|
||||
@ -105,7 +105,7 @@ The following table displays the recommended method for upgrading clients.
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Install the App-V 5.0 client with co-existence enabled.</p></td>
|
||||
<td align="left"><p>[How to Deploy the App-V 4.6.x and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46x-and-the-app-v--50-client-on-the-same-computer.md).</p></td>
|
||||
<td align="left"><p>[How to Deploy the App-V 4.6 and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--50-client-on-the-same-computer.md).</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Sequence and roll out App-V 5.0 packages. As needed, unpublish App-V 4.6 packages.</p></td>
|
||||
@ -117,7 +117,7 @@ The following table displays the recommended method for upgrading clients.
|
||||
|
||||
|
||||
**Important**
|
||||
You must be running App-V 4.6 SP2 to use coexistence mode. Additionally, when you sequence a package, you must configure the Managing Authority setting, which is in the **User Configuration** is located in the **User Configuration** section.
|
||||
You must be running App-V 4.6 SP3 to use coexistence mode. Additionally, when you sequence a package, you must configure the Managing Authority setting, which is in the **User Configuration** is located in the **User Configuration** section.
|
||||
|
||||
|
||||
|
||||
@ -139,7 +139,7 @@ There is no direct method to upgrade to a full App-V 5.0 infrastructure. Use the
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Upgrade your environment to App-V 4.6 SP2.</p></td>
|
||||
<td align="left"><p>Upgrade your environment to App-V 4.6 SP3.</p></td>
|
||||
<td align="left"><p>[Application Virtualization Deployment and Upgrade Considerations](../appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy.md).</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -164,15 +164,14 @@ There is no direct method to upgrade to a full App-V 5.0 infrastructure. Use the
|
||||
|
||||
You can also perform additional migration tasks such as reconfiguring end points as well as opening a package created using a prior version on a computer running the App-V 5.0 client. The following links provide more information about performing these tasks.
|
||||
|
||||
[How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md)
|
||||
[How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md)
|
||||
|
||||
[How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-50-for-a-specific-user.md)
|
||||
[How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-50-for-a-specific-user.md)
|
||||
|
||||
[How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 SP2 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-sp2-package-for-all-users-on-a-specific-computer.md)
|
||||
[How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-package-for-all-users-on-a-specific-computer.md)
|
||||
|
||||
[How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 SP2 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-sp2-package-for-a-specific-user.md)
|
||||
[How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-package-for-a-specific-user.md)
|
||||
|
||||
[How to Use an App-V 4.6 SP1 Application From an App-V 5.0 Application](how-to-use-an-app-v-46-sp1-application-from-an-app-v-50-application.md)
|
||||
|
||||
## Got a suggestion for App-V?
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@ However, you cannot migrate directly from App-V 4.x to App-V 5.1, you must migra
|
||||
**Note**
|
||||
App-V 5.1 packages are exactly the same as App-V 5.0 packages. 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 5.1 packages.
|
||||
|
||||
For more information about the differences between App-V 4.6 and App-V 5.1, see the **Differences between App-4.6 and App-V 5.0 section** of [About App-V 5.0](about-app-v-50.md).
|
||||
For more information about the differences between App-V 4.6 and App-V 5.1, see the **Differences between App-V 4.6 and App-V 5.0 section** of [About App-V 5.0](about-app-v-50.md).
|
||||
|
||||
|
||||
|
||||
@ -241,7 +241,7 @@ The following table displays the recommended method for upgrading clients.
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Install the App-V 5.1 client with co-existence enabled.</p></td>
|
||||
<td align="left"><p>[How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46x-and-the-app-v--51-client-on-the-same-computer.md).</p></td>
|
||||
<td align="left"><p>[How to Deploy the App-V 4.6 and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--51-client-on-the-same-computer.md).</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Sequence and roll out App-V 5.1 packages. As needed, unpublish App-V 4.6 packages.</p></td>
|
||||
@ -300,15 +300,14 @@ There is no direct method to upgrade to a full App-V 5.1 infrastructure. Use the
|
||||
|
||||
You can also perform additional migration tasks such as reconfiguring end points as well as opening a package created using a prior version on a computer running the App-V 5.1 client. The following links provide more information about performing these tasks.
|
||||
|
||||
[How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md)
|
||||
[How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md)
|
||||
|
||||
[How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-51-for-a-specific-user.md)
|
||||
[How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-51-for-a-specific-user.md)
|
||||
|
||||
[How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-all-users-on-a-specific-computer.md)
|
||||
[How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-package-for-all-users-on-a-specific-computer.md)
|
||||
|
||||
[How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-a-specific-user.md)
|
||||
[How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-package-for-a-specific-user.md)
|
||||
|
||||
[How to Use an App-V 4.6 Application From an App-V 5.1 Application](how-to-use-an-app-v-46-sp1-application-from-an-app-v-51-application.md)
|
||||
|
||||
## Got a suggestion for App-V?
|
||||
|
||||
|
||||
@ -20,22 +20,23 @@ Use the following information to plan how to migrate to App-V 5.0 from previous
|
||||
|
||||
Before you start any upgrades, review the following requirements:
|
||||
|
||||
- If you are upgrading from a version earlier than 4.6 SP2, upgrade to version 4.6 SP2 or version 4.6 SP3 first before upgrading to App-V 5.0 or later. In this scenario, upgrade the App-V clients first, and then upgrade the server components.
|
||||
- If you are upgrading from a version earlier than App-V 4.6 SP2, upgrade to version App-V 4.6 SP3 first before upgrading to App-V 5.0 or later. In this scenario, upgrade the App-V clients first, and then upgrade the server components.
|
||||
**Note:** App-V 4.6 has exited Mainstream support.
|
||||
|
||||
- App-V 5.0 supports only packages that are created using App-V 5.0, or packages that have been converted to the App-V 5.0 (**.appv**) format.
|
||||
|
||||
- App-V 5.0 SP3 only: If you are upgrading the App-V Server from App-V 5.0 SP1, see [About App-V 5.0 SP3](about-app-v-50-sp3.md#bkmk-migrate-to-50sp3) for instructions.
|
||||
|
||||
## Running the App-V 5.0 client concurrently with App-V 4.6 SP2 or later
|
||||
## Running the App-V 5.0 client concurrently with App-V 4.6
|
||||
|
||||
|
||||
You can run the App-V 5.0 client concurrently on the same computer with the App-V 4.6 SP2 client or App-V 4.6 SP3 client.
|
||||
You can run the App-V 5.0 client concurrently on the same computer with the App-V 4.6 SP3 client.
|
||||
|
||||
When you run coexisting App-V clients, you can:
|
||||
|
||||
- Convert an App-V 4.6 SP2 or 4.6 SP3 package to the App-V 5.0 format and publish both packages, when you have both clients running.
|
||||
- Convert an App-V 4.6 SP3 package to the App-V 5.0 format and publish both packages, when you have both clients running.
|
||||
|
||||
- Define the migration policy for the converted package, which allows the converted App-V 5.0 package to assume the file type associations and shortcuts from the App-V 4.6 SP2 package.
|
||||
- Define the migration policy for the converted package, which allows the converted App-V 5.0 package to assume the file type associations and shortcuts from the App-V 4.6 package.
|
||||
|
||||
### Supported coexistence scenarios
|
||||
|
||||
@ -48,20 +49,12 @@ The following table shows the supported App-V coexistence scenarios. We recommen
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">App-V 4.6.x client type</th>
|
||||
<th align="left">App-V 4.6 client type</th>
|
||||
<th align="left">App-V 5.0 client type</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP2</p></td>
|
||||
<td align="left"><p>App-V 5.0</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP2 RDS</p></td>
|
||||
<td align="left"><p>App-V 5.0 RDS</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>App-V 5.0</p></td>
|
||||
</tr>
|
||||
@ -78,37 +71,33 @@ The following table shows the supported App-V coexistence scenarios. We recommen
|
||||
|
||||
To run coexisting clients, you must:
|
||||
|
||||
- Install the App-V 4.6 SP2 or App-V 4.6 SP3 client before you install the App-V 5.0 client.
|
||||
- Install the App-V 4.6 client before you install the App-V 5.0 client.
|
||||
|
||||
- Enable the **Enable Migration Mode** Group Policy setting, which is in the **App-V** > **Client Coexistence** node. To get the deploy the .admx template, see [How to Download and Deploy MDOP Group Policy (.admx) Templates](http://technet.microsoft.com/library/dn659707.aspx).
|
||||
|
||||
### Client downloads and documentation
|
||||
|
||||
The following table provides links to the App-V 4.6.x client downloads and to the TechNet documentation about the releases. The downloads include the App-V “regular” and RDS clients. The TechNet documentation about the App-V client applies to both clients, unless stated otherwise.
|
||||
The following table provides link to the TechNet documentation about the releases. The TechNet documentation about the App-V client applies to both clients, unless stated otherwise.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">App-V version</th>
|
||||
<th align="left">Link to download the client</th>
|
||||
<th align="left">Link to TechNet documentation</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP2</p></td>
|
||||
<td align="left"><p>[Microsoft Application Virtualization 4.6 Service Pack 2](http://www.microsoft.com/download/details.aspx?id=35513)</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 4.6 SP2](http://technet.microsoft.com/library/jj680847.aspx)</p></td>
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 4.6 SP3](http://technet.microsoft.com/library/dn511019.aspx)</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>[Microsoft Application Virtualization 4.6 Service Pack 3](http://www.microsoft.com/download/details.aspx?id=41187)</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 4.6 SP3](http://technet.microsoft.com/library/dn511019.aspx)</p></td>
|
||||
<td align="left"><p>App-V 5.0 SP3</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 5.0 SP3](about-app-v-50-sp3.md)</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -117,14 +106,14 @@ The following table provides links to the App-V 4.6.x client downloads and to th
|
||||
|
||||
For more information about how to configure App-V 5.0 client coexistence, see:
|
||||
|
||||
- [How to Deploy the App-V 4.6.x and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46x-and-the-app-v--50-client-on-the-same-computer.md)
|
||||
- [How to Deploy the App-V 4.6 and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--50-client-on-the-same-computer.md)
|
||||
|
||||
- [App-V 5.0 Coexistence and Migration](http://technet.microsoft.com/windows/jj835811.aspx)
|
||||
|
||||
## <a href="" id="converting--previous-version--packages-using-the-package-converter-"></a>Converting “previous-version” packages using the package converter
|
||||
|
||||
|
||||
Before migrating a package, created using App- 4.6 SP2 or earlier, to App-V 5.0, review the following requirements:
|
||||
Before migrating a package, created using App-V 4.6 SP3 or earlier, to App-V 5.0, review the following requirements:
|
||||
|
||||
- You must convert the package to the **.appv** file format.
|
||||
|
||||
|
||||
@ -20,22 +20,23 @@ Use the following information to plan how to migrate to Microsoft Application Vi
|
||||
|
||||
Before you start any upgrades, review the following requirements:
|
||||
|
||||
- If you are upgrading from a version earlier than 4.6 SP2, upgrade to version 4.6 SP2 or version 4.6 SP3 first before upgrading to App-V 5.1 or later. In this scenario, upgrade the App-V clients first, and then upgrade the server components.
|
||||
- If you are upgrading from a version earlier than App-V 4.6 SP2, upgrade to version App-V 4.6 SP3 first before upgrading to App-V 5.1 or later. In this scenario, upgrade the App-V clients first, and then upgrade the server components.
|
||||
**Note:** App-V 4.6 has exited Mainstream support.
|
||||
|
||||
- App-V 5.1 supports only packages that are created using App-V 5.0 or App-V 5.1, or packages that have been converted to the **.appv** format.
|
||||
|
||||
- If you are upgrading the App-V Server from App-V 5.0 SP1, see [About App-V 5.1](about-app-v-51.md#bkmk-migrate-to-51) for instructions.
|
||||
|
||||
## Running the App-V 5.1 client concurrently with App-V 4.6 SP2 or later
|
||||
## Running the App-V 5.1 client concurrently with App-V 4.6
|
||||
|
||||
|
||||
You can run the App-V 5.1 client concurrently on the same computer with the App-V 4.6 SP2 client or App-V 4.6 SP3 client.
|
||||
You can run the App-V 5.1 client concurrently on the same computer with the App-V 4.6 SP3 client.
|
||||
|
||||
When you run coexisting App-V clients, you can:
|
||||
|
||||
- Convert an App-V 4.6 SP2 or 4.6 SP3 package to the App-V 5.1 format and publish both packages, when you have both clients running.
|
||||
- Convert an App-V 4.6 SP3 package to the App-V 5.1 format and publish both packages, when you have both clients running.
|
||||
|
||||
- Define the migration policy for the converted package, which allows the converted App-V 5.1 package to assume the file type associations and shortcuts from the App-V 4.6 SP2 package.
|
||||
- Define the migration policy for the converted package, which allows the converted App-V 5.1 package to assume the file type associations and shortcuts from the App-V 4.6 package.
|
||||
|
||||
### Supported coexistence scenarios
|
||||
|
||||
@ -48,20 +49,12 @@ The following table shows the supported App-V coexistence scenarios. We recommen
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">App-V 4.6.x client type</th>
|
||||
<th align="left">App-V 4.6 client type</th>
|
||||
<th align="left">App-V 5.1 client type</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP2</p></td>
|
||||
<td align="left"><p>App-V 5.1</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP2 RDS</p></td>
|
||||
<td align="left"><p>App-V 5.1 RDS</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>App-V 5.1</p></td>
|
||||
</tr>
|
||||
@ -78,42 +71,38 @@ The following table shows the supported App-V coexistence scenarios. We recommen
|
||||
|
||||
To run coexisting clients, you must:
|
||||
|
||||
- Install the App-V 4.6 SP2 or App-V 4.6 SP3 client before you install the App-V 5.1 client.
|
||||
- Install the App-V 4.6 client before you install the App-V 5.1 client.
|
||||
|
||||
- Enable the **Enable Migration Mode** Group Policy setting, which is in the **App-V** > **Client Coexistence** node. To deploy the .admx template, see [How to Download and Deploy MDOP Group Policy (.admx) Templates](http://technet.microsoft.com/library/dn659707.aspx).
|
||||
|
||||
**Note**
|
||||
App-V 5.1 packages can run side by side with App-V 4.X packages if you have coexisting installations of App-V 5.1 and 4.X. However, App-V 5.1 packages cannot interact with App-V 4.X packages in the same virtual environment.
|
||||
App-V 5.1 packages can run side by side with App-V 4.6 packages if you have coexisting installations of App-V 5.1 and 4.6. However, App-V 5.1 packages cannot interact with App-V 4.6 packages in the same virtual environment.
|
||||
|
||||
|
||||
|
||||
### Client downloads and documentation
|
||||
|
||||
The following table provides links to the App-V 4.6.x client downloads and to the TechNet documentation about the releases. The downloads include the App-V “regular” and RDS clients. The TechNet documentation about the App-V client applies to both clients, unless stated otherwise.
|
||||
The following table provides links to the App-V 4.6 client downloads and to the TechNet documentation about the releases. The downloads include the App-V “regular” and RDS clients. The TechNet documentation about the App-V client applies to both clients, unless stated otherwise.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">App-V version</th>
|
||||
<th align="left">Link to download the client</th>
|
||||
<th align="left">Link to TechNet documentation</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP2</p></td>
|
||||
<td align="left"><p>[Microsoft Application Virtualization 4.6 Service Pack 2](http://www.microsoft.com/download/details.aspx?id=35513)</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 4.6 SP2](http://technet.microsoft.com/library/jj680847.aspx)</p></td>
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 4.6 SP3](http://technet.microsoft.com/library/dn511019.aspx)</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>[Microsoft Application Virtualization 4.6 Service Pack 3](http://www.microsoft.com/download/details.aspx?id=41187)</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 4.6 SP3](http://technet.microsoft.com/library/dn511019.aspx)</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 5.1](about-app-v-51.md)</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -122,7 +111,7 @@ The following table provides links to the App-V 4.6.x client downloads and to th
|
||||
|
||||
For more information about how to configure App-V 5.1 client coexistence, see:
|
||||
|
||||
- [How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46x-and-the-app-v--51-client-on-the-same-computer.md)
|
||||
- [How to Deploy the App-V 4.6 and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--51-client-on-the-same-computer.md)
|
||||
|
||||
- [App-V 5.0 Coexistence and Migration](http://technet.microsoft.com/windows/jj835811.aspx)
|
||||
|
||||
|
||||
@ -66,7 +66,7 @@ App-V 5.0 dynamic configuration files customize a package for a specific user. Y
|
||||
|
||||
When a dynamic user configuration file is used, none of the App-V 5.0 information for the extension in the manifest file is used. This means that the dynamic user configuration file must include everything for the extension that is specific to App-V 5.0 in the manifest file, as well as the changes that you want to make, such as, deletions and updates. For more information about how to create a custom configuration file, see [How to Create a Custom Configuration File by Using the App-V 5.0 Management Console](how-to-create-a-custom-configuration-file-by-using-the-app-v-50-management-console.md).
|
||||
|
||||
[How to Deploy the App-V 4.6.x and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46x-and-the-app-v--50-client-on-the-same-computer.md)
|
||||
[How to Deploy the App-V 4.6 and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--50-client-on-the-same-computer.md)
|
||||
|
||||
## <a href="" id="bkmk-plan-for-scs"></a>Planning for the App-V 5.0 Shared Content Store (SCS)
|
||||
|
||||
|
||||
@ -92,7 +92,7 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
|
||||
[How to Deploy the App-V Client](how-to-deploy-the-app-v-client-51gb18030.md)
|
||||
|
||||
[How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46x-and-the-app-v--51-client-on-the-same-computer.md)
|
||||
[How to Deploy the App-V 4.6 and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--51-client-on-the-same-computer.md)
|
||||
|
||||
[How to Install the App-V 5.1 Client for Shared Content Store Mode](how-to-install-the-app-v-51-client-for-shared-content-store-mode.md)
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user