mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 06:17:22 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into vs-8493251
This commit is contained in:
commit
8b12de5af6
@ -62,7 +62,6 @@
|
||||
##### [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 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)
|
||||
##### [How to Deploy the App-V Server](appv-deploy-the-appv-server.md)
|
||||
##### [How to Deploy the App-V Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Accessibility for App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Microsoft is committed to making its products and services easier for everyone to use. This section provides information about features and services that make this product and its corresponding documentation more accessible for people with disabilities.
|
||||
|
||||
|
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# How to access the client management console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the App-V client management console to manage packages on the computer running the App-V client.
|
||||
|
||||
> [!NOTE]
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Add or Remove an Administrator by Using the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedures to add or remove an administrator on the Microsoft Application Virtualization (App-V) server.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Add or Upgrade Packages by Using the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can the following procedure to add or upgrade a package to the App-V Management Console. To upgrade a package that already exists in the Management Console, use the following steps and import the upgraded package using the same package **Name**.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Administering App-V by Using PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Microsoft Application Virtualization (App-V) provides Windows PowerShell cmdlets, which can help administrators perform various App-V tasks. The following sections provide more information about using PowerShell with App-V.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Administering App-V Virtual Applications by Using the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the Microsoft Application Virtualization (App-V) management server to manage packages, connection groups, and package access in your environment. The server publishes application icons, shortcuts, and file type associations to authorized computers that run the App-V client. One or more management servers typically share a common data store for configuration and package information.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Allow Only Administrators to Enable Connection Groups
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can configure the App-V client so that only administrators (not end users) can enable or disable connection groups. In earlier versions of App-V, you could not prevent end users from performing these tasks.
|
||||
|
||||
@ -36,7 +37,7 @@ Use one of the following methods to allow only administrators to enable or disab
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Group Policy setting</p></td>
|
||||
<td align="left"><p>Enable the “Require publish as administrator” Group Policy setting, which is located in the following Group Policy Object node:</p>
|
||||
<p><strong>Computer Configuration > Policies > Administrative Templates > System > App-V > Publishing</strong></p></td>
|
||||
<p><strong>Computer Configuration > Administrative Templates > System > App-V > Publishing</strong></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>PowerShell cmdlet</p></td>
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Application Publishing and Client Interaction
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
This article provides technical information about common App-V client operations and their integration with the local operating system.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Apply the Deployment Configuration File by Using PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
The dynamic deployment configuration file is applied when a package is added or set to a computer running the App-V client before the package has been published. The file configures the default settings for package for all users on the computer running the App-V client. This section describes the steps used to use a deployment configuration file. The procedure is based on the following example and assumes the following package and configuration files exist on a computer:
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Apply the User Configuration File by Using PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
The dynamic user configuration file is applied when a package is published to a specific user and determines how the package will run.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# App-V Capacity Planning
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
The following recommendations can be used as a baseline to help determine capacity planning information that is appropriate to your organization’s App-V infrastructure.
|
||||
|
||||
|
@ -10,9 +10,11 @@ ms.prod: w10
|
||||
|
||||
# About Client Configuration Settings
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
The Microsoft Application Virtualization (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. This topic lists the App-V Client configuration settings and explains their uses. You can use PowerShell to modify the client configuration settings. For more information about using PowerShell and App-V see [Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md).
|
||||
|
||||
|
||||
You can use Group Policy to configure App-V client settings by using the Group Policy Management Console under **Computer Configuration** > **Administrative Templates** > **System** > **App-V**.
|
||||
|
||||
## App-V Client Configuration Settings: Windows PowerShell
|
||||
|
||||
@ -110,4 +112,3 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
|
||||
[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)
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Configure Access to Packages by Using the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Before you deploy an App-V virtualized package, you must configure the Active Directory Domain Services (AD DS) security groups that will be allowed to access and run the applications. The security groups may contain computers or users. Entitling a package to a computer group publishes the package globally to all computers in the group.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Make a Connection Group Ignore the Package Version
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Microsoft Application Virtualization (App-V) lets you configure a connection group to use any version of a package, which simplifies package upgrades and reduces the number of connection groups you need to create.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Deploying packages and connection groups using the App-V publishing server is helpful because it offers single-point management and high scalability.
|
||||
|
||||
|
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# How to Connect to the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to connect to the App-V Management Console.
|
||||
|
||||
**To connect to the App-V Management Console**
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# About the Connection Group File
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
**In this topic:**
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# About the Connection Group Virtual Environment
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
**In this topic:**
|
||||
|
||||
|
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# How to Convert a Package Created in a Previous Version of App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can use the package converter utility to upgrade virtual application packages that have been created with previous versions of App-V.
|
||||
|
||||
> [!NOTE]
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Create a Connection Group with User-Published and Globally Published Packages
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can create user-entitled connection groups that contain both user-published and globally published packages, using either of the following methods:
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Create a Connection Group
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use these steps to create a connection group by using the App-V Management Console. To use PowerShell to create connection groups, see [How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md).
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Create a Custom Configuration File by Using the App-V Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can use a dynamic configuration to customize an App-V package for a specific user. However, you must first create the dynamic user configuration (.xml) file or the dynamic deployment configuration file before you can use the files. Creation of the file is an advanced manual operation. For general information about dynamic user configuration files, see, [About App-V Dynamic Configuration](appv-dynamic-configuration.md).
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Create a Package Accelerator by Using PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
App-V package accelerators automatically sequence large, complex applications. Additionally, when you apply an App-V package accelerator, you are not always required to manually install an application to create the virtualized package.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Create a Package Accelerator
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
App-V package accelerators automatically generate new virtual application packages.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Create a Virtual Application Package Using an App-V Package Accelerator
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
**Important**
|
||||
The App-V Sequencer does not grant any license rights to the software application that you use to create the Package Accelerator. You must abide by all end user license terms for the application that you use. It is your responsibility to make sure that the software application’s license terms allow you to create a Package Accelerator with the App-V Sequencer.
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Create and Use a Project Template
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can use an App-V project template to save commonly applied settings associated with an existing virtual application package. These settings can then be applied when you create new virtual application packages in your environment. Using a project template can streamline the process of creating virtual application packages.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Creating and Managing App-V Virtualized Applications
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
After you have properly deployed the Microsoft Application Virtualization (App-V) sequencer, you can use it to monitor and record the installation and setup process for an application to be run as a virtualized application.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Customize Virtual Applications Extensions for a Specific AD Group by Using the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to customize the virtual application extensions for an Active Directory (AD) group.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Delete a Connection Group
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to delete an existing App-V connection group.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Delete a Package in the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to delete an App-V package.
|
||||
|
||||
|
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# How to Deploy the App-V Databases by Using SQL Scripts
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
Use the following instructions to use SQL scripts, rather than the Windows Installer, to:
|
||||
|
||||
- Install the App-V databases
|
||||
|
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# How to deploy App-V packages using electronic software distribution
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can use an electronic software distribution (ESD) system to deploy App-V virtual applications to App-V clients.
|
||||
|
||||
For component requirements and options for using an ESD to deploy App-V packages, see [Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md).
|
||||
|
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# How to Deploy the App-V Server Using a Script
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
In order to complete the **appv\_server\_setup.exe** Server setup successfully using the command line, you must specify and combine multiple parameters.
|
||||
|
||||
**To Install the App-V server using a script**
|
||||
|
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# How to Deploy the App-V Server (new installation)
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
>**Important**<br>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.
|
||||
|
||||
**Before you start:**
|
||||
|
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# Deploying App-V for Windows 10
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
App-V supports a number of different deployment options. Review this topic for information about the tasks that you must complete at different stages in your deployment.
|
||||
|
||||
## App-V Deployment Information
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Deploying Microsoft Office 2010 by Using App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can create Office 2010 packages for Microsoft Application Virtualization (App-V) using one of the following methods:
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Deploying Microsoft Office 2013 by Using App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the information in this article to use Microsoft Application Virtualization (App-V), or later versions, to deliver Microsoft Office 2013 as a virtualized application to computers in your organization. For information about using App-V to deliver Office 2010, see [Deploying Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md). To successfully deploy Office 2013 with App-V, you need to be familiar with Office 2013 and App-V.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Deploying App-V Packages by Using Electronic Software Distribution (ESD)
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can deploy App-V packages using an Electronic Software Distribution (ESD) solution. For information about planning to deploy App-V packages with an ESD, see [Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md).
|
||||
|
||||
|
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# Deploying the App-V Sequencer and Configuring the Client
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
The App-V Sequencer and client enable administrators to virtualize and run virtualized applications.
|
||||
|
||||
## Enable the client
|
||||
@ -24,23 +26,19 @@ 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)
|
||||
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. For more information, see [About Client Configuration Settings](appv-client-configuration-settings.md).
|
||||
|
||||
## Configure the client by using the ADMX template and Group Policy
|
||||
|
||||
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.
|
||||
To manage the ADMX template, 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**
|
||||
|
||||
2. Save the **.adml** file to the following directory: **Windows \\ PolicyDefinitions \\ <Language Directory>**
|
||||
|
||||
After you have completed the preceding steps, you can manage the App-V client configuration settings with the **Group Policy Management** console.
|
||||
|
||||
[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)
|
||||
After you have completed the preceding steps, you can use Group Policy to configure the client settings by using the Group Policy Management Console under **Computer Configuration** > **Administrative Templates** > **System** > **App-V**.
|
||||
|
||||
## Understanding Shared Content Store mode for App-V clients
|
||||
|
||||
|
@ -10,7 +10,7 @@ ms.prod: w10
|
||||
|
||||
# Deploying the App-V server
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
>**Note** If you plan to use the App-V server components in your deployment, note that they reference App-V 5.x. This is because the App-V server components have not changed in App-V for Windows 10.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# App-V Deployment Checklist
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
This checklist can be used to help you during an App-V deployment.
|
||||
|
||||
|
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# About App-V Dynamic Configuration
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can use the dynamic configuration to customize an App-V package for a user. Use the following information to create or edit an existing dynamic configuration file.
|
||||
|
||||
When you edit the dynamic configuration file it customizes how an App-V package will run for a user or group. This helps to provide a more convenient method for package customization by removing the need to re-sequence packages using the desired settings, and provides a way to keep package content and custom settings independent.
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Enable Only Administrators to Publish Packages by Using an ESD
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Starting in App-V 5.0 SP3, you can configure the App-V client so that only administrators (not end users) can publish or unpublish packages. In earlier versions of App-V, you could not prevent end users from performing these tasks.
|
||||
|
||||
@ -18,7 +19,7 @@ Starting in App-V 5.0 SP3, you can configure the App-V client so that only admin
|
||||
|
||||
1. Navigate to the following Group Policy Object node:
|
||||
|
||||
**Computer Configuration > Policies > Administrative Templates > System > App-V > Publishing**.
|
||||
**Computer Configuration > Administrative Templates > System > App-V > Publishing**.
|
||||
|
||||
2. Enable the **Require publish as administrator** Group Policy setting.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Enable Reporting on the App-V Client by Using PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to configure the App-V for reporting.
|
||||
|
||||
|
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# Enable the App-V in-box client
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
The App-V client is the component that runs virtualized applications on user devices. The client enables users to interact with icons and file names to start virtualized applications. The client can also get virtual application content from the management server.
|
||||
|
||||
With Windows 10, version 1607, the App-V client is installed automatically. You need to enable the client to allow user devices to access and run virtual applications. You can enable the client with the Group Policy editor or with Windows PowerShell.
|
||||
|
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# Evaluating App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Before you deploy App-V into a production environment, you should evaluate it in a lab environment. You can use the information in this topic to set up App-V in a lab environment for evaluation purposes only.
|
||||
|
||||
## Configure lab computers for App-V Evaluation
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Application Virtualization (App-V) for Windows 10 overview
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
The topics in this section provide information and step-by-step procedures to help you administer App-V and its components. This information will be valuable for system administrators who manage large installations with many servers and clients and for support personnel who interact directly with the computers or the end users.
|
||||
|
||||
|
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# Getting Started with App-V for Windows 10
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Microsoft Application Virtualization (App-V) for Windows 10 enables organizations to deliver Win32 applications to users as virtual applications. Virtual applications are installed on centrally managed servers and delivered to users as a service – in real time and on as as-needed basis. Users launch virtual applications from familiar access points and interact with them as if they were installed locally.
|
||||
|
||||
With the release of Windows 10, version 1607, App-V is included with the [Windows 10 for Enterprise edition](https://www.microsoft.com/en-us/WindowsForBusiness/windows-for-enterprise). If you are new to Windows 10 and App-V, you’ll need to download, activate, and install server- and client-side components to start delivering virtual applications to users. For information about what you need to know before getting started with App-V, see the [Application Virtualization (App-V) overview](appv-for-windows.md).
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# High Level Architecture for App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following information to help you simplify you Microsoft Application Virtualization (App-V) deployment.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
Use the following PowerShell procedure to convert any number of Active Directory Domain Services (AD DS) user or machine accounts into formatted Security Identifiers (SIDs) both in the standard format and in the hexadecimal format used by Microsoft SQL Server when running SQL scripts.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
Use the following procedure to install the database server and management server on different computers. The computer you plan to install the database server on must be running a supported version of Microsoft SQL or the installation will fail.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to install the Management Server on a Standalone Computer and Connect it to the Database
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
Use the following procedure to install the management server on a standalone computer and connect it to the database.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Install the Publishing Server on a Remote Computer
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
Use the following procedure to install the publishing server on a separate computer. Before you perform the following procedure, ensure the database and management server are available.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to install the Reporting Server on a Standalone Computer and Connect it to the Database
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
Use the following procedure to install the reporting server on a standalone computer and connect it to the database.
|
||||
|
||||
|
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# Install the App-V Sequencer
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the App-V Sequencer to convert Win32 applications into virtual packages for deployment to user devices. Those devices must be running the App-V client to allow users to interact with virtual applications.
|
||||
|
||||
The App-V Sequencer is included in the Windows 10 Assessment and Deployment Kit (Windows ADK).
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Load the PowerShell Cmdlets and Get Cmdlet Help
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
What this topic covers:
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Maintaining App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
After you have deployed App-V for Windows 10, you can use the following information to maintain the App-V infrastructure.
|
||||
|
||||
|
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
|
||||
The following sections explain how to perform various management tasks on a stand-alone client computer by using PowerShell:
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
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.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Managing Connection Groups
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Connection groups enable the applications within a package to interact with each other in the virtual environment, while remaining isolated from the rest of the system. By using connection groups, administrators can manage packages independently and can avoid having to add the same application multiple times to a client computer.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Modify an Existing Virtual Application Package
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
This topic explains how to:
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Modify Client Configuration by Using PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to configure the App-V client configuration.
|
||||
|
||||
|
@ -1,23 +1,4 @@
|
||||
---
|
||||
title: How to Modify App-V Client Configuration Using the ADMX Template and Group Policy (Windows 10)
|
||||
description: How to Modify App-V Client Configuration Using the ADMX Template and Group Policy
|
||||
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 Modify App-V client configuration using the ADMX template and Group Policy
|
||||
|
||||
You can use Group Policy to configure App-V client settings by using the Group Policy Management Console under **Computer Configuration** > **Policies** > **Administrative Templates** > **System** > **App-V**.
|
||||
|
||||
## 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 App-V](appv-deploying-appv.md)
|
||||
|
||||
- [About Client Configuration Settings](appv-client-configuration-settings.md)
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to move the App-V server to another computer
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
Use the following information to create a new management server console in your environment.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Operations for App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
This section of the Microsoft Application Virtualization (App-V) Administrator’s Guide includes information about the various types of App-V administration and operating tasks that are typically performed by an administrator. This section also includes step-by-step procedures to help you successfully perform those tasks.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Performance Guidance for Application Virtualization
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Learn how to configure App-V for optimal performance, optimize virtual app packages, and provide a better user experience with RDS and VDI.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# App-V Planning Checklist
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
This checklist can be used to help you plan for preparing your organization for an App-V deployment.
|
||||
|
||||
|
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# Planning to Use Folder Redirection with App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Microsoft Application Virtualization (App-V) supports the use of folder redirection, a feature that enables users and administrators to redirect the path of a folder to a new location.
|
||||
|
||||
This topic contains the following sections:
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Planning for the App-V Server Deployment
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
The Microsoft Application Virtualization (App-V) server infrastructure consists of a set of specialized features that can be installed on one or more server computers, based on the requirements of the enterprise.
|
||||
|
||||
|
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# Planning for App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use this information to plan how to deploy App-V so that it does not disrupt your users or the network.
|
||||
|
||||
## Planning information
|
||||
|
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# Planning for High Availability with App-V Server
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Microsoft Application Virtualization (App-V) system configurations can take advantage of options that maintain a high level of available service.
|
||||
|
||||
Use the information in the following sections to help you understand the options to deploy App-V in a highly available configuration.
|
||||
|
@ -10,6 +10,7 @@ ms.prod: w10
|
||||
|
||||
# Planning for the App-V Sequencer and Client Deployment
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Before you can use App-V, you must install the App-V Sequencer, enable the App-V client, and optionally the App-V shared content store. The following sections address planning for these installations.
|
||||
|
||||
|
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# Planning for Using App-V with Office
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following information to plan how to deploy Office by using Microsoft Application Virtualization (App-V). This article includes:
|
||||
|
||||
- [App-V support for Language Packs](#bkmk-lang-pack)
|
||||
|
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# Planning to Deploy App-V with an electronic software distribution system
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
If you are using an electronic software distribution system to deploy App-V packages, review the following planning considerations. For information about using System Center Configuration Manager to deploy App-V, see [Introduction to Application Management in Configuration Manager](https://technet.microsoft.com/en-us/library/gg682125.aspx#BKMK_Appv).
|
||||
|
||||
Review the following component and architecture requirements options that apply when you use an ESD to deploy App-V packages:
|
||||
|
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# Preparing Your Environment for App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
There are a number of different deployment configurations and prerequisites that you must consider before you create your deployment plan for Microsoft Application Virtualization (App-V). This section includes information that can help you gather the information that you must have to formulate a deployment plan that best meets your business requirements.
|
||||
|
||||
## App-V prerequisites
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Publish a Connection Group
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
After you create a connection group, you must publish it to computers that run the App-V client.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Publish a Package by Using the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to publish an App-V package. Once you publish a package, computers that are running the App-V client can access and run the applications in that package.
|
||||
|
||||
@ -31,7 +32,7 @@ The ability to enable only administrators to publish or unpublish packages (desc
|
||||
|
||||
1. Navigate to the following Group Policy Object node:
|
||||
|
||||
**Computer Configuration > Policies > Administrative Templates > System > App-V > Publishing**.
|
||||
**Computer Configuration > Administrative Templates > System > App-V > Publishing**.
|
||||
|
||||
2. Enable the **Require publish as administrator** Group Policy setting.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Register and Unregister a Publishing Server by Using the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can register and unregister publishing servers that will synchronize with the App-V management server. You can also see the last attempt that the publishing server made to synchronize the information with the management server.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# About App-V Reporting
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Application Virtualization (App-V) includes a built-in reporting feature that helps you collect information about computers running the App-V client as well as information about virtual application package usage. You can use this information to generate reports from a centralized database.
|
||||
|
||||
@ -134,9 +135,7 @@ To use App-V reporting you must enable and configure the App-V client. To config
|
||||
The following examples show how Windows PowerShell parameters can configure the reporting features of the App-V client.
|
||||
|
||||
**Note**
|
||||
The following configuration task can also be configured using Group Policy settings in the App-V ADMX template. The App-V settings are under **Computer Configuration > Administrative Templates > System > App-V**. For more information about using the ADMX template, see [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).
|
||||
|
||||
|
||||
The following configuration task can also be configured using Group Policy settings in the App-V ADMX template. The App-V settings are under **Computer Configuration > Administrative Templates > System > App-V**.
|
||||
|
||||
**To enable reporting and to initiate data collection on the computer running the App-V client**:
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can run a locally installed application in a virtual environment, alongside applications that have been virtualized by using Microsoft Application Virtualization (App-V). You might want to do this if you:
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# App-V Security Considerations
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
This topic contains a brief overview of the accounts and groups, log files, and other security-related considerations for Microsoft Application Virtualization (App-V).
|
||||
|
||||
|
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# How to Sequence a New Application with App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
In Windows 10, version 1607, the App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
**To review or do before you start sequencing**
|
||||
|
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# How to Sequence a Package by using Windows PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to create a new App-V package using Windows PowerShell.
|
||||
|
||||
> [!NOTE]
|
||||
|
@ -11,7 +11,7 @@ ms.prod: w10
|
||||
|
||||
# App-V Supported Configurations
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
Applies to: Windows 10, version 1607; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; and Windows Server 2008 R2
|
||||
|
||||
This topic specifies the requirements to install and run App-V in your Windows 10 environment.
|
||||
|
||||
@ -35,7 +35,7 @@ The App-V server does not support the following scenarios:
|
||||
|
||||
### Management server operating system requirements
|
||||
|
||||
The App-V Management server can be installed on a server that runs Windows Server 2008 R2 with SP1 or a later.
|
||||
The App-V Management server can be installed on a server that runs Windows Server 2008 R2 with SP1 or later.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Deployment of the Management server role to a computer with Remote Desktop Services enabled is not supported.
|
||||
@ -90,7 +90,7 @@ The following table lists the SQL Server versions that are supported for the App
|
||||
|
||||
### Publishing server operating system requirements
|
||||
|
||||
The App-V Publishing server can be installed on a server that runs Windows Server 2008 R2 with SP1 or a later.
|
||||
The App-V Publishing server can be installed on a server that runs Windows Server 2008 R2 with SP1 or later.
|
||||
|
||||
|
||||
### Publishing server hardware requirements
|
||||
@ -105,7 +105,7 @@ App-V adds no additional requirements beyond those of Windows Server.
|
||||
|
||||
### Reporting server operating system requirements
|
||||
|
||||
The App-V Reporting server can be installed on a server that runs Windows Server 2008 R2 with SP1 or a later.
|
||||
The App-V Reporting server can be installed on a server that runs Windows Server 2008 R2 with SP1 or later.
|
||||
|
||||
### Reporting server hardware requirements
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Technical Reference for App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
This section provides reference information related to managing App-V.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to transfer the access and default package configurations to another version of a package by using the management console.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Troubleshooting App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Troubleshooting content is not included in the Administrator’s Guide for this product. Instead, you can find troubleshooting information for this product on the [TechNet Wiki](http://go.microsoft.com/fwlink/p/?LinkId=224905).
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Using the App-V Client Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
This topic provides information about how you can configure and manage the Microsoft Application Virtualization (App-V) client.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to view and configure default package extensions.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Viewing App-V Server Publishing Metadata
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
Use this procedure to view publishing metadata, which can help you resolve publishing-related issues. You must be using the App-V Management server to use this procedure.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Accessibility for UE-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Microsoft is committed to making its products and services easier for everyone to use. This section provides information about features and services that make this product and its corresponding documentation more accessible for people with disabilities.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Administering UE-V with Windows PowerShell and WMI
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
User Experience Virtualization (UE-V) provides Windows PowerShell cmdlets to help administrators perform various UE-V tasks. The following sections provide more information about using Windows PowerShell in UE-V.
|
||||
|
||||
|
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# Administering UE-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
After you finish deploying User Experience Virtualization (UE-V), you'll perform ongoing administrative tasks, such as managing the configuration of the UE-V service and recovering lost settings. These tasks are explained in the following sections.
|
||||
|
||||
## Managing UE-V configurations
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Application Template Schema Reference for UE-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
User Experience Virtualization (UE-V) uses XML settings location templates to define the desktop application settings and Windows settings that are captured and applied by UE-V. UE-V includes a set of default settings location templates. You can also create custom settings location templates with the UE-V template generator.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Changing the Frequency of UE-V Scheduled Tasks
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
When the User Experience Virtualization (UE-V) service is enabled, it creates the following scheduled tasks:
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Configuring UE-V with Group Policy Objects
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Some User Experience Virtualization (UE-V) Group Policy settings can be defined for computers, and other Group Policy settings can be defined for users. The Group Policy administrative templates for these settings are included in Windows 10, version 1607.
|
||||
|
||||
|
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Configuring UE-V with System Center Configuration Manager
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
After you deploy User Experience Virtualization (UE-V) and its required features, you can start to configure it to meet your organization's need. The UE-V Configuration Pack provides a way for administrators to use the Compliance Settings feature of System Center Configuration Manager (2012 SP1 or later) to apply consistent configurations across sites where UE-V and Configuration Manager are installed.
|
||||
|
||||
|
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# Deploy required UE-V features
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
To get up and running with User Experience Virtualization (UE-V), install and configure the following features.
|
||||
|
||||
- [Deploy a settings storage location](#deploy-a-ue-v-settings-storage-location) that is accessible to end users.
|
||||
|
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# Use UE-V with custom applications
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
User Experience Virtualization (UE-V) uses XML files called ***settings location templates*** to monitor and synchronize application settings and Windows settings between user devices. By default, some settings location templates are included in UE-V. However, if you want to synchronize settings for desktop applications other than those included in the default templates, you can create your own custom settings location templates with the UE-V template generator.
|
||||
|
||||
After you’ve reviewed [Prepare a UE-V Deployment](uev-prepare-for-deployment.md) and decided that you want to synchronize settings for custom applications (third-party, line-of-business, e.g.), you’ll need to deploy the features of UE-V described in this topic.
|
||||
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user