diff --git a/windows/manage/TOC.md b/windows/manage/TOC.md index a9d6fefe63..b439a02e08 100644 --- a/windows/manage/TOC.md +++ b/windows/manage/TOC.md @@ -58,10 +58,9 @@ ##### [Planning to Use Folder Redirection with App-V](appv-planning-folder-redirection-with-appv.md) #### [App-V Planning Checklist](appv-planning-checklist.md) ### [Deploying App-V](appv-deploying-appv.md) -#### [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md) +#### [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md) ##### [About Client Configuration Settings](appv-client-configuration-settings.md) ##### [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md) -##### [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md) ##### [How to Install the Sequencer](appv-install-the-sequencer.md) ##### [How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md) #### [Deploying the App-V Server](appv-deploying-the-appv-server.md) diff --git a/windows/manage/appv-application-publishing-and-client-interaction.md b/windows/manage/appv-application-publishing-and-client-interaction.md index d9e5931749..fdec3fdd21 100644 --- a/windows/manage/appv-application-publishing-and-client-interaction.md +++ b/windows/manage/appv-application-publishing-and-client-interaction.md @@ -1059,7 +1059,7 @@ For situations where there is more than one application that could register the The AppPath extension point supports calling App-V applications directly from the operating system. This is typically accomplished from the Run or Start Screen, depending on the operating system, which enables administrators to provide access to App-V applications from operating system commands or scripts without calling the specific path to the executable. It therefore avoids modifying the system path environment variable on all systems, as it is accomplished during publishing. -The AppPath extension point is configured either in the manifest or in the dynamic configuration files and is stored in the registry on the local machine during publishing for the user. For additional information on AppPath review: [App Paths ? A Virtual Application Extension in App-V 5.0](https://blogs.technet.microsoft.com/virtualworld/2012/12/12/app-paths-a-virtual-application-extension-in-app-v-5-0/). +The AppPath extension point is configured either in the manifest or in the dynamic configuration files and is stored in the registry on the local machine during publishing for the user. For additional information on AppPath review: [App Paths - A Virtual Application Extension in App-V 5.0](https://blogs.technet.microsoft.com/virtualworld/2012/12/12/app-paths-a-virtual-application-extension-in-app-v-5-0/). ### Virtual application diff --git a/windows/manage/appv-capacity-planning.md b/windows/manage/appv-capacity-planning.md index 32072d9331..0c1453422f 100644 --- a/windows/manage/appv-capacity-planning.md +++ b/windows/manage/appv-capacity-planning.md @@ -47,18 +47,10 @@ Before you design the App-V infrastructure, determine the project’s scope. The -  - ## Determine Which App-V Infrastructure is Required - ->**Important**   -Both of the following models require the App-V client to be installed on the computer where you plan to run virtual applications. - You can also manage your App-V environment using an Electronic Software Distribution (ESD) solution such as Microsoft Systems Center Configuration Manager. For more information see [How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md). -  - - **Standalone Model** - The standalone model allows virtual applications to be Windows Installer-enabled for distribution without streaming. App-V in Standalone Mode consists of the sequencer and the client; no additional components are required. Applications are prepared for virtualization using a process called sequencing. For more information see, [Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md). The stand-alone model is recommended for the following scenarios: - With disconnected remote users who cannot connect to the App-V infrastructure. diff --git a/windows/manage/appv-client-configuration-settings.md b/windows/manage/appv-client-configuration-settings.md index 93b6745d4e..6dfed6b51b 100644 --- a/windows/manage/appv-client-configuration-settings.md +++ b/windows/manage/appv-client-configuration-settings.md @@ -108,6 +108,6 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros ## Related topics -[Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md) +[Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md) [How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md) diff --git a/windows/manage/appv-deploy-the-appv-server.md b/windows/manage/appv-deploy-the-appv-server.md index c85f273c6c..16d49c34e8 100644 --- a/windows/manage/appv-deploy-the-appv-server.md +++ b/windows/manage/appv-deploy-the-appv-server.md @@ -8,7 +8,7 @@ ms.sitesec: library ms.prod: w10 --- -# How to Deploy the App-V Server (new installataion) +# How to Deploy the App-V Server (new installation) >**Important**
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. diff --git a/windows/manage/appv-deploying-appv.md b/windows/manage/appv-deploying-appv.md index 14a78375a1..85384b2568 100644 --- a/windows/manage/appv-deploying-appv.md +++ b/windows/manage/appv-deploying-appv.md @@ -15,7 +15,7 @@ App-V supports a number of different deployment options. Review this topic for i ## App-V Deployment Information -- [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md) +- [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md) This section describes how to install the App-V sequencer, which is used to virtualize applications, and how to enable the App-V client, which runs on target computers to facilitate virtualized packages. diff --git a/windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md b/windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md index 87112ed665..fe452de031 100644 --- a/windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md +++ b/windows/manage/appv-deploying-microsoft-office-2010-wth-appv.md @@ -72,9 +72,9 @@ Sequencing Office 2010 is one of the main methods for creating an Office 2010 pa Office 2010 App-V packages can be created through package accelerators. Microsoft has provided package accelerators for creating Office 2010 on Windows 10, Windows 8 and Windows 7. To create Office 2010 packages on App-V using Package accelerators, refer to the following pages to access the appropriate package accelerator: -- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 8](http://go.microsoft.com/fwlink/p/?LinkId=330677) +- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 8](https://gallery.technet.microsoft.com/App-V-50-Package-a29410db) -- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 7](http://go.microsoft.com/fwlink/p/?LinkId=330678) +- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 7](https://gallery.technet.microsoft.com/App-V-50-Package-e7ef536b) For detailed instructions on how to create virtual application packages using App-V package accelerators, see [How to Create a Virtual Application Package Using an App-V Package Accelerator](appv-create-a-virtual-application-package-package-accelerator.md). diff --git a/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md b/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md index 1664333c9f..f441e4af00 100644 --- a/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md +++ b/windows/manage/appv-deploying-microsoft-office-2013-with-appv.md @@ -133,7 +133,7 @@ The following table describes the recommended methods for excluding specific Off

Use the ExcludeApp setting when you create the package by using the Office Deployment Tool.

@@ -205,7 +205,7 @@ Create Office 2013 App-V packages on 64-bit Windows computers. Once created, the Office 2013 App-V Packages are created using the Office Deployment Tool, which generates an Office 2013 App-V Package. The package cannot be created or modified through the App-V sequencer. To begin package creation: -1. Download the [Office Deployment Tool for Click-to-Run](http://www.microsoft.com/download/details.aspx?id=36778). +1. Download the [Office 2013 Deployment Tool for Click-to-Run](http://www.microsoft.com/download/details.aspx?id=36778). 2. Run the .exe file and extract its features into the desired location. To make this process easier, you can create a shared network folder where the features will be saved. @@ -810,7 +810,7 @@ The following table describes the requirements and options for deploying Visio 2

How do I package and publish Visio 2013 and Project 2013 with Office?

You must include Visio 2013 and Project 2013 in the same package with Office.

-

If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow the [Virtualizing Microsoft Office 2013 for Application Virtualization (App-V) 5.0](https://technet.microsoft.com/en-us/itpro/mdop/solutions/virtualizing-microsoft-office-2013-for-application-virtualization--app-v--50-solutions#bkmk-pkg-pub-reqs).

+

If you aren’t deploying Office, you can create a package that contains Visio and/or Project.

How can I deploy Visio 2013 and Project 2013 to specific users?

@@ -841,7 +841,7 @@ The following table describes the requirements and options for deploying Visio 2

  1. Create a package that contains Office, Visio, and Project.

  2. Deploy the package to all users.

    3. -

  3. Use [Microsoft AppLocker](http://technet.microsoft.com/library/dd723678.aspx) to prevent specific users from using Visio and Project.

    4. +

  4. Use [AppLocker](https://technet.microsoft.com/en-us/itpro/windows/keep-secure/applocker-overview) to prevent specific users from using Visio and Project.

@@ -858,13 +858,13 @@ The following table describes the requirements and options for deploying Visio 2 **Office 2013 App-V Packages Additional Resources** -[Office Deployment Tool for Click-to-Run](http://go.microsoft.com/fwlink/p/?LinkID=330672) +[Office 2013 Deployment Tool for Click-to-Run](http://www.microsoft.com/download/details.aspx?id=36778) [Supported scenarios for deploying Microsoft Office as a sequenced App-V Package](https://support.microsoft.com/en-us/kb/2772509) **Office 2010 App-V Packages** -[Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0](https://www.microsoft.com/en-us/download/details.aspx?id=38399) +[Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0](https://www.microsoft.com/download/details.aspx?id=38399) [Known issues when you create or use an App-V 5.0 Office 2010 package](https://support.microsoft.com/en-us/kb/2828619) @@ -882,14 +882,4 @@ The following table describes the requirements and options for deploying Visio 2 ## Have a suggestion for App-V? - Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). - -  - -  - - - - - diff --git a/windows/manage/appv-deploying-packages-with-electronic-software-distribution-solutions.md b/windows/manage/appv-deploying-packages-with-electronic-software-distribution-solutions.md index 67811c04b2..ca135a0bea 100644 --- a/windows/manage/appv-deploying-packages-with-electronic-software-distribution-solutions.md +++ b/windows/manage/appv-deploying-packages-with-electronic-software-distribution-solutions.md @@ -19,7 +19,7 @@ To deploy App-V packages with Microsoft System Center 2012 Configuration Manage ## How to deploy virtualized packages using an ESD -Describes the methods you can use to deploy App-V packages by using an ESD +Describes the methods you can use to deploy App-V packages by using an ESD. [How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md) diff --git a/windows/manage/appv-deploying-the-appv-sequencer-and-client.md b/windows/manage/appv-deploying-the-appv-sequencer-and-client.md index 809872cdec..f4c7790c8f 100644 --- a/windows/manage/appv-deploying-the-appv-sequencer-and-client.md +++ b/windows/manage/appv-deploying-the-appv-sequencer-and-client.md @@ -1,6 +1,6 @@ --- -title: Deploy the App-V Sequencer and Client (Windows 10) -description: Deploying the App-V Sequencer and Client +title: Deploying the App-V Sequencer and Configuring the Client (Windows 10) +description: Deploying the App-V Sequencer and Configuring the Client author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -9,13 +9,12 @@ ms.prod: w10 --- -# Deploying the App-V Sequencer and Client +# Deploying the App-V Sequencer and Configuring the Client The App-V Sequencer and client enable administrators to virtualize and run virtualized applications. ## Enable the client - The App-V client is the component that runs a virtualized application on a target computer. The client enables users to interact with icons and to double-click file types, so that they can start a virtualized application. The client can also obtain the virtual application content from the management server. > [!NOTE] @@ -25,7 +24,6 @@ The App-V client is the component that runs a virtualized application on a targe ## Client Configuration Settings - The App-V client stores its configuration in the registry. You can gather some useful information about the client if you understand the format of data in the registry. You can also configure many client actions by changing registry entries. [About Client Configuration Settings](appv-client-configuration-settings.md) @@ -34,7 +32,6 @@ The App-V client stores its configuration in the registry. You can gather some u You can use Group Policy to configure the client settings for the App-V client and the Remote Desktop Services client. - Perform the following steps on the computer that you will use to manage Group Policy. This is typically the Domain Controller. 1. Save the **.admx** file to the following directory: **Windows \\ PolicyDefinitions** @@ -43,11 +40,9 @@ Perform the following steps on the computer that you will use to manage Group Po After you have completed the preceding steps, you can manage the App-V client configuration settings with the **Group Policy Management** console. -The App-V client also stores its configuration in the registry. You can gather some useful information about the client if you understand the format of the data in the registry. You can also configure many client actions by changing registry entries. - [How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md) -## Deploy the client by using the Shared Content Store mode +## Understanding Shared Content Store mode for App-V clients The App-V Shared Content Store (SCS) mode enables the SCS App-V clients to run virtualized applications without saving any of the associated package data locally. All required virtualized package data is transmitted across the network; therefore, you should only use the SCS mode in environments with a fast connection. Both the Remote Desktop Services (RDS) and the standard version of the App-V client are supported with SCS mode. @@ -62,15 +57,25 @@ The SCS mode is helpful in the following scenarios: - Remote Desktop Services deployments -To use SCS in your environment, you must enable the App-V client to run in SCS mode. This setting should be specified during installation. By default, the client is not configured to use SCS mode. You should install the client by using the suggested procedure if you plan to use SCS. However, you can configure an existing App-V client to run in SCS mode by entering the following Windows PowerShell command on the computer that runs the App-V client: - -``` -set-AppvClientConfiguration -SharedContentStoreMode 1 -``` +To use SCS in your environment, you must configure the App-V client to run in SCS mode (it will not use SCS mode by default). There might be cases when the administrator pre-loads some virtual applications on the computer that runs the App-V client in SCS mode. This can be accomplished with Windows PowerShell commands to add, publish, and mount the package. For example, if a package is pre-loaded on all computers, the administrator could add, publish, and mount the package by using Windows PowerShell commands. The package would not stream across the network because it would be locally stored. -[How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md) +### Configure the Group Policy setting for the SCS Mode for App-V clients + +Use the following steps to locate and configure the Group Policy setting for the SCS Mode for App-V clients. + +1. In the Group Policy Management Console, navigate to **Computer Configuration** > **Administrative Templates** > **System** > **App-V** > **Streaming**. + +2. Enable the **Set the Shared Content Mode (SCS) mode** setting. + +### Configure an individual client to use the SCS mode + +To configure the App-V client to run in SCS mode, on the client, enter the following Windows PowerShell command: + +``` +Set-AppvClientConfiguration -SharedContentStoreMode 1 +``` ## Deploy the Sequencer @@ -87,11 +92,6 @@ You can use the App-V Sequencer log information to help troubleshoot the Sequenc **Event Viewer \\ Applications and Services Logs \\ Microsoft \\ App V**. Sequencer-related events are prepended with **AppV\_Sequencer**. Client-related events are prepended with **AppV\_Client**. -## Other resources for deploying the Sequencer and client - -- [Deploying App-V](appv-deploying-appv.md) -- [Planning for App-V](appv-planning-for-appv.md) - ## Have a suggestion for App-V? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). diff --git a/windows/manage/appv-deploying-the-appv-server.md b/windows/manage/appv-deploying-the-appv-server.md index c690b835bd..b1b97bc1be 100644 --- a/windows/manage/appv-deploying-the-appv-server.md +++ b/windows/manage/appv-deploying-the-appv-server.md @@ -74,7 +74,7 @@ The distributed deployment topology can support a large App-V client base and it - [How to install the Management Server on a Standalone Computer and Connect it to the Database](appv-install-the-management-server-on-a-standalone-computer.md) ## Using an Enterprise Software Distribution (ESD) solution and App-V -You can also deploy the App-V clients and packages by using an ESD without having to deploy App-V. The full capabilities for integration will vary depending on the ESD that you use. +You can also deploy packages by using an ESD. The full capabilities for integration will vary depending on the ESD that you use. >**Note**
The App-V reporting server and reporting database can still be deployed alongside the ESD to collect the reporting data from the App-V clients. However, the other three server components should not be deployed, because they will conflict with the ESD functionality. diff --git a/windows/manage/appv-deployment-checklist.md b/windows/manage/appv-deployment-checklist.md index 2da5471851..b972beff77 100644 --- a/windows/manage/appv-deployment-checklist.md +++ b/windows/manage/appv-deployment-checklist.md @@ -41,7 +41,7 @@ This checklist outlines the recommended steps and items to consider when deployi Checklist box -

Review the App-V supported configurations information to make sure selected client and server computers are supported for App-V feature installation.

+

Review the App-V supported configurations information.

[App-V Supported Configurations](appv-supported-configurations.md)

diff --git a/windows/manage/appv-dynamic-configuration.md b/windows/manage/appv-dynamic-configuration.md index 9f39eb5a86..29d3819f7a 100644 --- a/windows/manage/appv-dynamic-configuration.md +++ b/windows/manage/appv-dynamic-configuration.md @@ -636,7 +636,7 @@ The following table describes the various script events and the context under wh ### Using multiple scripts on a single event trigger -App-V supports the use of multiple scripts on a single event trigger for App-V packages, including packages that you convert from App-V 4.6 to App-V for Windows 10. To enable the use of multiple scripts, App-V uses a script launcher application, named ScriptRunner.exe, which is installed as part of the App-V client installation. +App-V supports the use of multiple scripts on a single event trigger for App-V packages, including packages that you convert from App-V 4.6 to App-V for Windows 10. To enable the use of multiple scripts, App-V uses a script launcher application, named ScriptRunner.exe, which is included in the App-V client. **How to use multiple scripts on a single event trigger:** @@ -683,10 +683,10 @@ Using the following example file and table, modify the deployment or user config

ScriptRunner.exe

-

The script launcher application that is installed as part of the App-V client installation.

+

The script launcher application that is included in the App-V client.

Note   -

Although ScriptRunner.exe is installed as part of the App-V client, the location of the App-V client must be in %path% or ScriptRunner will not run. ScriptRunner.exe is typically located in the C:\Program Files\Microsoft Application Virtualization\Client folder.

+

Although ScriptRunner.exe is included in the App-V client, the location of the App-V client must be in %path% or ScriptRunner will not run. ScriptRunner.exe is typically located in the C:\Program Files\Microsoft Application Virtualization\Client folder.

  diff --git a/windows/manage/appv-for-windows.md b/windows/manage/appv-for-windows.md index 17e12bb59e..b714e9c734 100644 --- a/windows/manage/appv-for-windows.md +++ b/windows/manage/appv-for-windows.md @@ -31,7 +31,7 @@ The topics in this section provide information and step-by-step procedures to he [Deploying App-V](appv-deploying-appv.md) -- [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md) +- [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md) - [Deploying the App-V Server](appv-deploying-the-appv-server.md) - [App-V Deployment Checklist](appv-deployment-checklist.md) - [Deploying Microsoft Office 2013 by Using App-V](appv-deploying-microsoft-office-2013-with-appv.md) diff --git a/windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.md b/windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.md index f02ef3fd54..77ee61220b 100644 --- a/windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.md +++ b/windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.md @@ -1,29 +1,4 @@ --- title: How to Install the App-V Client for Shared Content Store Mode (Windows 10) -description: How to Install the App-V Client for Shared Content Store Mode -author: MaggiePucciEvans -ms.pagetype: mdop, appcompat, virtualization -ms.mktglfcycl: deploy -ms.sitesec: library -ms.prod: w10 +redirect_url: https://technet.microsoft.com/itpro/windows/manage/appv-deploying-the-appv-sequencer-and-client --- - - -# How to Install the App-V Client for Shared Content Store Mode - - -Use the following procedure to install the Microsoft Application Virtualization (App-V) client so that it uses the App-V Shared Content Store (SCS) mode. - -**Enable the App-V client for SCS mode** - -1. In the Group Policy Management Console, navigate to **Computer Configuration** > **Administrative Templates** > **System** > **App-V** > **Streaming**. - -2. Enable the **Set the Shared Content Mode (SCS) mode** setting. - -## Have a suggestion for App-V? - -Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). - -## Related topics - -- [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md) diff --git a/windows/manage/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md b/windows/manage/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md index b54a3e959a..461ae4e6d3 100644 --- a/windows/manage/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md +++ b/windows/manage/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md @@ -14,7 +14,7 @@ ms.prod: w10 An App-V connection group allows you to run all the virtual applications as a defined set of packages in a single virtual environment. For example, you can virtualize an application and its plug-ins by using separate packages, but run them together in a single connection group. -A connection group XML file defines the connection group that runs on the computer where you’ve installed the App-V client. For information about the connection group XML file and how to configure it, see [About the Connection Group File](appv-connection-group-file.md). +A connection group XML file defines the connection group for the App-V client. For information about the connection group XML file and how to configure it, see [About the Connection Group File](appv-connection-group-file.md). This topic explains the following procedures: diff --git a/windows/manage/appv-migrating-to-appv-from-a-previous-version.md b/windows/manage/appv-migrating-to-appv-from-a-previous-version.md index 8baa974696..0c954a7bf8 100644 --- a/windows/manage/appv-migrating-to-appv-from-a-previous-version.md +++ b/windows/manage/appv-migrating-to-appv-from-a-previous-version.md @@ -207,46 +207,9 @@ It is recommended that you use the App-V sequencer for converting critical appli If a converted package does not open after you convert it, it is also recommended that you re-sequence the application using the App-V sequencer. -  - [How to Convert a Package Created in a Previous Version of App-V](appv-convert-a-package-created-in-a-previous-version-of-appv.md) -## Migrating Clients - - -The following table displays the recommended method for upgrading clients. - - ---- - - - - - - - - - - - - - - - - -
TaskMore Information

Upgrade your environment to the latest version of App-V 4.6

[Application Virtualization Deployment and Upgrade Considerations](https://technet.microsoft.com/en-us/itpro/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy).

Sequence and roll out App-V packages. As needed, unpublish App-V 4.6 packages.

[How to Sequence a New Application with App-V](appv-sequence-a-new-application.md).

- -  - -**Important**   -You must be running the latest version of App-V 4.6 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. - -  - -## Migrating the App-V server Server Full Infrastructure +## Migrating the App-V Server Full Infrastructure There is no direct method to upgrade to a full App-V infrastructure. Use the information in the following section for information about upgrading the App-V server. @@ -264,20 +227,20 @@ There is no direct method to upgrade to a full App-V infrastructure. Use the inf -

Upgrade your environment to the latest version of App-V 4.6.

-

[Application Virtualization Deployment and Upgrade Considerations](https://technet.microsoft.com/en-us/itpro/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy).

+

Review prerequisites.

+

[App-V Server prerequisite software](appv-prerequisites.md#app-v-server-prerequisite-software).

-

Deploy App-V version of the client.

+

Enable the App-V client.

[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).

-

Install App-V server server.

-

[How to Deploy the App-V server Server](appv-deploy-the-appv-server.md).

+

Install App-V Server.

+

[How to Deploy the App-V Server](appv-deploy-the-appv-server.md).

Migrate existing packages.

-

See Converting packages created using a prior version of App-V earlier in this topic.

+

See [Converting packages created using a prior version of App-V](#converting-packages-created-using-a-prior-version-of-app-v) earlier in this topic.

diff --git a/windows/manage/appv-performance-guidance.md b/windows/manage/appv-performance-guidance.md index 0154fa543b..4091c997e0 100644 --- a/windows/manage/appv-performance-guidance.md +++ b/windows/manage/appv-performance-guidance.md @@ -171,9 +171,9 @@ The following table displays the required steps to prepare the base image and th