mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
Merge branch 'master' into nimishasatapathy-5400951-part6
This commit is contained in:
commit
73380bfe99
@ -18956,10 +18956,10 @@
|
||||
"redirect_document_id": false
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/data-processor-service-for-windows-enterprise-public-preview-terms.md",
|
||||
"redirect_url": "/windows/privacy/windows-10-and-privacy-compliance",
|
||||
"source_path": "windows/security/identity-protection/change-history-for-access-protection.md",
|
||||
"redirect_url": "/windows/security/",
|
||||
"redirect_document_id": false
|
||||
},
|
||||
}
|
||||
|
||||
|
||||
]
|
||||
|
5
.vscode/settings.json
vendored
5
.vscode/settings.json
vendored
@ -1,5 +0,0 @@
|
||||
{
|
||||
"cSpell.words": [
|
||||
"emie"
|
||||
]
|
||||
}
|
@ -16,9 +16,10 @@ ms.topic: article
|
||||
|
||||
# Add or hide features on the Windows client OS
|
||||
|
||||
> Applies to:
|
||||
>
|
||||
> - Windows 10
|
||||
**Applies to**:
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
The Windows client operating systems include more features that you and your users can install. These features are called [Features on Demand](/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities) (opens another Microsoft web site), and can be installed at any time. On your organization-owned devices, you may want to control access to these other features.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Add or Remove an Administrator by Using the Management Console (Windows 10)
|
||||
title: How to Add or Remove an Administrator by Using the Management Console (Windows 10/11)
|
||||
description: Add or remove an administrator on the Microsoft Application Virtualization (App-V) server by using the Management Console.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to add or remove an administrator by using the Management Console
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following procedures to add or remove an administrator on the Microsoft Application Virtualization (App-V) server.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Add or Upgrade Packages by Using the Management Console (Windows 10)
|
||||
title: How to Add or Upgrade Packages by Using the Management Console (Windows 10/11)
|
||||
description: Add or remove an administrator on the Microsoft Application Virtualization (App-V) server by using the Management Console.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to add or upgrade packages by using the Management Console
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
You can use 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**.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Administering App-V by using Windows PowerShell (Windows 10)
|
||||
title: Administering App-V by using Windows PowerShell (Windows 10/11)
|
||||
description: Administer App-V by using Windows PowerShell and learn where to find more information about PowerShell for App-V.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Administering App-V by using Windows PowerShell
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Microsoft Application Virtualization (App-V) supports Windows PowerShell cmdlets that give administrators a quick and easy way to manage App-V. The following sections will tell you more about how to use Windows PowerShell with App-V.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Administering App-V Virtual Applications by using the Management Console (Windows 10)
|
||||
title: Administering App-V Virtual Applications by using the Management Console (Windows 10/11)
|
||||
description: Administering App-V Virtual Applications by using the Management Console
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Administering App-V Virtual Applications by using the Management Console
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
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 running the App-V client. One or more management servers typically share a common data store for configuration and package information.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Only Allow Admins to Enable Connection Groups (Windows 10)
|
||||
title: Only Allow Admins to Enable Connection Groups (Windows 10/11)
|
||||
description: Configure the App-V client so that only administrators, not users, can enable or disable connection groups.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to allow only administrators to enable connection groups
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
You can configure the App-V client so that only administrators, not users, can enable or disable connection groups. In earlier versions of App-V, there was no way to restrict access to disabling connection groups to users.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Application Publishing and Client Interaction (Windows 10)
|
||||
title: Application Publishing and Client Interaction (Windows 10/11)
|
||||
description: Learn technical information about common App-V Client operations and their integration with the local operating system.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Application publishing and client interaction
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
This article provides technical information about common App-V Client operations and their integration with the local operating system.
|
||||
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Apply deployment config file via Windows PowerShell (Windows 10)
|
||||
description: How to apply the deployment configuration file by using Windows PowerShell for Windows 10.
|
||||
title: Apply deployment config file via Windows PowerShell (Windows 10/11)
|
||||
description: How to apply the deployment configuration file by using Windows PowerShell for Windows 10/11.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to apply the deployment configuration file by using Windows PowerShell
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
When you add or set a package to a computer running the App-V client before it's been published, a dynamic deployment configuration file is applied to it. The dynamic deployment configuration file configures the default settings for the package that all users share on the computer running the App-V client. This section will tell you how to use a deployment configuration file.
|
||||
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How to apply the user configuration file by using Windows PowerShell (Windows 10)
|
||||
description: How to apply the user configuration file by using Windows PowerShell (Windows 10).
|
||||
title: How to apply the user configuration file by using Windows PowerShell (Windows 10/11)
|
||||
description: How to apply the user configuration file by using Windows PowerShell (Windows 10/11).
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to apply the user configuration file by using Windows PowerShell
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
When you publish a package to a specific user, you'll also need to specify a dynamic user configuration file to tell that package how to run.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10)
|
||||
title: Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10/11)
|
||||
description: How to automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer).
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,11 +14,11 @@ ms.topic: article
|
||||
---
|
||||
# Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)
|
||||
|
||||
>Applies to: Windows 10, version 1703
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Sequencing multiple apps at the same time requires you to install and start Microsoft Application Virtualization Sequencer (App-V Sequencer), and to install the necessary apps to collect any changes made to the operating system during the installation and building of the App-V package.
|
||||
|
||||
In Windows 10, version 1703, running the App-V Sequencer automatically captures and stores your customizations as an App-V project template (.appvt) file. If you want to make changes to this package later, your customizations will be automatically loaded from this template file. This is applicable to all of the sequencing scenarios:
|
||||
Starting with Windows 10 version 1703, running the App-V Sequencer automatically captures and stores your customizations as an App-V project template (.appvt) file. If you want to make changes to this package later, your customizations will be automatically loaded from this template file. This is applicable to all of the sequencing scenarios:
|
||||
|
||||
- Using the **New-BatchAppVSequencerPackages** cmdlet
|
||||
- Using the App-V Sequencer interface
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10)
|
||||
title: Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10/11)
|
||||
description: How to automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer).
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,11 +14,11 @@ ms.topic: article
|
||||
---
|
||||
# Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)
|
||||
|
||||
>Applies to: Windows 10, version 1703
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Updating multiple apps at the same time follows a similar process to the one used for [automatically sequencing multiple apps at the same time](appv-auto-batch-sequencing.md). However, when updating, you'll also have to pass your previously created app package files to the App-V Sequencer cmdlet.
|
||||
|
||||
Starting with Windows 10, version 1703, running the New-BatchAppVSequencerPackages cmdlet or the App-V Sequencer interface captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file.
|
||||
Starting with Windows 10 version 1703, running the New-BatchAppVSequencerPackages cmdlet or the App-V Sequencer interface captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file.
|
||||
|
||||
>[!NOTE]
|
||||
>If you're trying to sequence multiple apps at the same time, see [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md).
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Auto-remove unpublished packages on App-V client (Windows 10)
|
||||
title: Auto-remove unpublished packages on App-V client (Windows 10/11)
|
||||
description: How to automatically clean up any unpublished packages on your App-V client devices.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,9 +14,9 @@ ms.topic: article
|
||||
---
|
||||
# Automatically clean up unpublished packages on the App-V client
|
||||
|
||||
>Applies to: Windows 10, version 1703
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
If you wanted to free up additional storage space in previous versions of App-V, you would have had to manually remove your unpublished packages from your client devices. Windows 10, version 1703 introduces the ability to use PowerShell or Group Policy settings to automatically clean up your unpublished packages after restarting your device.
|
||||
If you wanted to free up additional storage space in previous versions of App-V, you would have had to manually remove your unpublished packages from your client devices. Starting with Windows 10 version 1703, use PowerShell or Group Policy settings to automatically clean up your unpublished packages after restarting your device.
|
||||
|
||||
## Clean up with PowerShell cmdlets
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10)
|
||||
title: Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10/11)
|
||||
description: How to automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer) PowerShell cmdlet or the user interface.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,9 +14,9 @@ ms.topic: article
|
||||
---
|
||||
# Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)
|
||||
|
||||
>Applies to: Windows 10, version 1703
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Previous versions of the App-V Sequencer have required you to manually create your sequencing environment. Windows 10, version 1703 introduces two new PowerShell cmdlets, New-AppVSequencerVM and Connect-AppvSequencerVM, which automatically create your sequencing environment for you, including provisioning your virtual machine.
|
||||
Previous versions of the App-V Sequencer have required you to manually create your sequencing environment. Starting with Windows 10 version 1703, the `New-AppVSequencerVM` and `Connect-AppvSequencerVM` Windows PowerShell cmdlets are available, which automatically create your sequencing environment for you, including provisioning your virtual machine.
|
||||
|
||||
## Automatic VM provisioning of the sequencing environment
|
||||
|
||||
@ -54,7 +54,7 @@ For this process to work, you must have a base operating system available as a V
|
||||
|
||||
After you have a VHD file, you must provision your VM for auto-sequencing.
|
||||
|
||||
1. On the Host device, install Windows 10, version 1703 and the **Microsoft Application Virtualization (App-V) Auto Sequencer** component from the matching version of the Windows Assessment and Deployment Kit (ADK). For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
|
||||
1. On the Host device, install the Windows client and the **Microsoft Application Virtualization (App-V) Auto Sequencer** component from the matching version of the Windows Assessment and Deployment Kit (ADK). For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
|
||||
2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see [Hyper-V on Windows Server 2016](/windows-server/virtualization/hyper-v/Hyper-V-on-Windows-Server).
|
||||
3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters:
|
||||
|
||||
@ -93,7 +93,7 @@ If your apps require custom prerequisites, such as Microsoft SQL Server, we reco
|
||||
|
||||
#### Provision an existing VM
|
||||
|
||||
1. On the Host device, install Windows 10, version 1703 and the **Microsoft Application Virtualization (App-V) Auto Sequencer** component from the matching version of the Windows Assessment and Deployment Kit (ADK). For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
|
||||
1. On the Host device, install the Windows client and the **Microsoft Application Virtualization (App-V) Auto Sequencer** component from the matching version of the Windows Assessment and Deployment Kit (ADK). For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
2. Open PowerShell as an admin and run the **Connect-AppvSequencerVM** cmdlet, using the following parameters:
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Available Mobile Device Management (MDM) settings for App-V (Windows 10)
|
||||
title: Available Mobile Device Management (MDM) settings for App-V (Windows 10/11)
|
||||
description: Learn the available Mobile Device Management (MDM) settings you can use to configure App-V on Windows 10.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,22 +14,22 @@ ms.topic: article
|
||||
---
|
||||
# Available Mobile Device Management (MDM) settings for App-V
|
||||
|
||||
With Windows 10, version 1703, you can configure, deploy, and manage your App-V apps with the following Mobile Device Management (MDM) settings. For the full list of available settings, see the [EnterpriseAppVManagement CSP](/windows/client-management/mdm/enterpriseappvmanagement-csp) page.
|
||||
Starting with Windows 10 version 1703, you can configure, deploy, and manage your App-V apps with the following Mobile Device Management (MDM) settings. For the full list of available settings, see the [EnterpriseAppVManagement CSP](/windows/client-management/mdm/enterpriseappvmanagement-csp) page.
|
||||
|
||||
|Policy name|Supported versions|URI full path|Data type|Values|
|
||||
|---|---|---|---|---|
|
||||
|Name|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/Name|String|Read-only data, provided by your App-V packages.|
|
||||
|Version|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/Version|String|Read-only data, provided by your App-V packages.|
|
||||
|Publisher|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/Publisher|String|Read-only data, provided by your App-V packages.|
|
||||
|InstallLocation|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/InstallLocation|String|Read-only data, provided by your App-V packages.|
|
||||
|InstallDate|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/InstallDate|String|Read-only data, provided by your App-V packages.|
|
||||
|Users|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/Users|String|Read-only data, provided by your App-V packages.|
|
||||
|AppVPackageID|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/AppVPackageID|String|Read-only data, provided by your App-V packages.|
|
||||
|AppVVersionID|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/AppVVersionID|String|Read-only data, provided by your App-V packages.|
|
||||
|AppVPackageUri|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/AppVPackageUri|String|Read-only data, provided by your App-V packages.|
|
||||
|LastError|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/<br>AppVPublishing/LastSync/LastError|String|Read-only data, provided by your App-V packages.|
|
||||
|LastErrorDescription|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPublishing/LastSync/LastErrorDescription|String|- **0**: No errors returned during publish.<br>- **1**: Unpublish groups failed during publish.<br>- **2**: Publish no-group packages failed during publish.<br>- **3**: Publish group packages failed during publish.<br>- **4**: Unpublish packages failed during publish.<br>- **5**: New policy write failed during publish.<br>- **6**: Multiple non-fatal errors occurred during publish.|
|
||||
|SyncStatusDescription|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPublishing/LastSync/SyncStatusDescription|String|- **0**: App-V publishing is idle.<br>- **1**: App-V connection groups publish in progress.<br>- **2**: App-V packages (non-connection group) publish in progress.<br>- **3**: App-V packages (connection group) publish in progress.<br>- **4**: App-V packages unpublish in progress.|
|
||||
|SyncProgress|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPublishing/LastSync/SyncProgress|String|- **0**: App-V Sync is idle.<br>- **1**: App-V Sync is initializing.<br>- **2**: App-V Sync is in progress.<br>- **3**: App-V Sync is complete.<br>- **4**: App-V Sync requires device reboot.|
|
||||
|PublishXML|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/<br>AppVPublishing/Sync/PublishXML|String|Custom value, entered by admin.|
|
||||
|Policy|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/<br>AppVDynamicPolicy/configurationid/Policy|String|Custom value, entered by admin.|
|
||||
|Name|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/Name|String|Read-only data, provided by your App-V packages.|
|
||||
|Version|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/Version|String|Read-only data, provided by your App-V packages.|
|
||||
|Publisher|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/Publisher|String|Read-only data, provided by your App-V packages.|
|
||||
|InstallLocation|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/InstallLocation|String|Read-only data, provided by your App-V packages.|
|
||||
|InstallDate|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/InstallDate|String|Read-only data, provided by your App-V packages.|
|
||||
|Users|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/Users|String|Read-only data, provided by your App-V packages.|
|
||||
|AppVPackageID|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/AppVPackageID|String|Read-only data, provided by your App-V packages.|
|
||||
|AppVVersionID|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/AppVVersionID|String|Read-only data, provided by your App-V packages.|
|
||||
|AppVPackageUri|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement/<enterprise_id>/ <package_family_name>/<package_full_name>/AppVPackageUri|String|Read-only data, provided by your App-V packages.|
|
||||
|LastError|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/<br>AppVPublishing/LastSync/LastError|String|Read-only data, provided by your App-V packages.|
|
||||
|LastErrorDescription|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPublishing/LastSync/LastErrorDescription|String|- **0**: No errors returned during publish.<br>- **1**: Unpublish groups failed during publish.<br>- **2**: Publish no-group packages failed during publish.<br>- **3**: Publish group packages failed during publish.<br>- **4**: Unpublish packages failed during publish.<br>- **5**: New policy write failed during publish.<br>- **6**: Multiple non-fatal errors occurred during publish.|
|
||||
|SyncStatusDescription|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPublishing/LastSync/SyncStatusDescription|String|- **0**: App-V publishing is idle.<br>- **1**: App-V connection groups publish in progress.<br>- **2**: App-V packages (non-connection group) publish in progress.<br>- **3**: App-V packages (connection group) publish in progress.<br>- **4**: App-V packages unpublish in progress.|
|
||||
|SyncProgress|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPublishing/LastSync/SyncProgress|String|- **0**: App-V Sync is idle.<br>- **1**: App-V Sync is initializing.<br>- **2**: App-V Sync is in progress.<br>- **3**: App-V Sync is complete.<br>- **4**: App-V Sync requires device reboot.|
|
||||
|PublishXML|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/<br>AppVPublishing/Sync/PublishXML|String|Custom value, entered by admin.|
|
||||
|Policy|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/<br>AppVDynamicPolicy/configurationid/Policy|String|Custom value, entered by admin.|
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: App-V Capacity Planning (Windows 10)
|
||||
title: App-V Capacity Planning (Windows 10/11)
|
||||
description: Use these recommendations as a baseline to help determine capacity planning information that is appropriate to your organization’s App-V infrastructure.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: About Client Configuration Settings (Windows 10)
|
||||
title: About Client Configuration Settings (Windows 10/11)
|
||||
description: Learn about the App-V client configuration settings and how to use Windows PowerShell to modify the client configuration settings.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# About Client Configuration Settings
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
The Microsoft Application Virtualization (App-V) client stores its configuration in the registry. Understanding how the register's format for data works can help you better understand the client, as you can configure many client actions by changing registry entries. This topic lists the App-V client configuration settings and explains their uses. You can use Windows PowerShell to modify the client configuration settings. For more information about using Windows PowerShell and App-V see [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md).
|
||||
|
||||
@ -29,7 +29,7 @@ The following table provides information about App-V client configuration settin
|
||||
|------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-PackageInstallationRoot**<br>String | Specifies directory where all new applications and updates will be installed. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-PackageSourceRoot**<br>String | Overrides source location for downloading package content. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-AllowHighCostLaunch**<br>True (enabled); False (Disabled state) | This setting controls whether virtualized applications are launched on Windows 10 machines connected by a metered network connection (for example, 4G). | 0 |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-AllowHighCostLaunch**<br>True (enabled); False (Disabled state) | This setting controls whether virtualized applications are launched on Windows client machines connected by a metered network connection (for example, 4G). | 0 |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReestablishmentRetries**<br>Integer (0–99) | Specifies the number of times to retry a dropped session. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReestablishmentInterval**<br>Integer (0–3600) | Specifies the number of seconds between attempts to reestablish a dropped session. | Policy value not written (same as Not Configured) |
|
||||
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-LocationProvider**<br>String | Specifies the CLSID for a compatible implementation of the IAppvPackageLocationProvider interface. | Policy value not written (same as Not Configured) |
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to configure access to packages by using the Management Console (Windows 10)
|
||||
title: How to configure access to packages by using the Management Console (Windows 10/11)
|
||||
description: How to configure access to packages by using the App-V Management Console.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to configure access to packages by using the Management Console
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
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.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to make a connection group ignore the package version (Windows 10)
|
||||
title: How to make a connection group ignore the package version (Windows 10/11)
|
||||
description: Learn how to make a connection group ignore the package version with the App-V Server Management Console.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to make a connection group ignore the package version
|
||||
|
||||
> Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
You can use Application Virtualization (App-V) to configure a connection group to use any version of a package, simplifying package upgrades and reducing the number of connection groups you need to create.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to configure the client to receive package and connection groups updates from the publishing server (Windows 10)
|
||||
title: How to configure the client to receive package and connection groups updates from the publishing server (Windows 10/11)
|
||||
description: How to configure the client to receive package and connection groups updates from the publishing server.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to configure the client to receive package and connection groups updates from the publishing server
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
The App-V publishing server's single-point management and high scalability lets you deploy packages and connection groups and keep them up to date.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to connect to the Management Console (Windows 10)
|
||||
title: How to connect to the Management Console (Windows 10/11)
|
||||
description: In this article, learn the procedure for connecting to the App-V Management Console through your web browser.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to connect to the Management Console
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following procedure to connect to the App-V Management Console.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: About the connection group file (Windows 10)
|
||||
title: About the connection group file (Windows 10/11)
|
||||
description: A summary of what the connection group file is and how to configure it.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# About the connection group file
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
## Connection group file overview
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: About the connection group virtual environment (Windows 10)
|
||||
title: About the connection group virtual environment (Windows 10/11)
|
||||
description: Learn how the connection group virtual environment works and how package priority is determined.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# About the connection group virtual environment
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
## How package priority is determined
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to convert a package created in a previous version of App-V (Windows 10)
|
||||
title: How to convert a package created in a previous version of App-V (Windows 10/11)
|
||||
description: Use the package converter utility to convert a virtual application package created in a previous version of App-V.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to convert a package created in a previous version of App-V
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
You can use the package converter utility to upgrade virtual application packages created by previous versions of App-V. This section will tell you how to convert existing virtual application packages for upgrade.
|
||||
|
||||
@ -28,9 +28,9 @@ The package converter can only directly convert packages created by an App-V seq
|
||||
|
||||
## App-V 4.6 installation folder is redirected to virtual file system root
|
||||
|
||||
When you convert packages from App-V 4.6 to App-V for Windows 10, the App-V for Windows 10 package can access the hardcoded drive that you were required to use when you created 4.6 packages. The drive letter will be the drive you selected as the installation drive on the 4.6 sequencing machine. (The default drive is drive Q.)
|
||||
When you convert packages from App-V 4.6 to App-V for Windows 10/11, the App-V for Windows client package can access the hardcoded drive that you were required to use when you created 4.6 packages. The drive letter will be the drive you selected as the installation drive on the 4.6 sequencing machine. (The default drive is drive Q.)
|
||||
|
||||
The App-V package converter will save the App-V 4.6 installation root folder and short folder names in the FilesystemMetadata.xml file in the **Filesystem** element. When the App-V for Windows 10 client creates the virtual process, it will map requests from the App-V 4.6 installation root to the virtual file system root.
|
||||
The App-V package converter will save the App-V 4.6 installation root folder and short folder names in the FilesystemMetadata.xml file in the **Filesystem** element. When the App-V for Windows client creates the virtual process, it will map requests from the App-V 4.6 installation root to the virtual file system root.
|
||||
|
||||
## Getting started
|
||||
|
||||
@ -50,9 +50,9 @@ The App-V package converter will save the App-V 4.6 installation root folder and
|
||||
ConvertFrom-AppvLegacyPackage C:\contentStore C:\convertedPackages
|
||||
```
|
||||
|
||||
In this cmdlet, `C:\contentStore` represents the location of the existing package and `C:\convertedPackages` is the output directory to which the resulting App-V for Windows 10 virtual application package file will be saved. By default, if you do not specify a new name, the old package name will be used.
|
||||
In this cmdlet, `C:\contentStore` represents the location of the existing package and `C:\convertedPackages` is the output directory to which the resulting App-V for Windows client virtual application package file will be saved. By default, if you do not specify a new name, the old package name will be used.
|
||||
|
||||
Additionally, the package converter optimizes performance of packages in App-V for Windows 10 by setting the package to stream fault the App-V package. This is more performant than the primary feature block and fully downloading the package. The flag **DownloadFullPackageOnFirstLaunch** allows you to convert the package and set the package to be fully downloaded by default.
|
||||
Additionally, the package converter optimizes performance of packages in App-V for Windows client by setting the package to stream fault the App-V package. This is more performant than the primary feature block and fully downloading the package. The flag **DownloadFullPackageOnFirstLaunch** allows you to convert the package and set the package to be fully downloaded by default.
|
||||
|
||||
> [!NOTE]
|
||||
> Before you specify the output directory, you must create the output directory.
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to create a connection croup with user-published and globally published packages (Windows 10)
|
||||
title: How to create a connection croup with user-published and globally published packages (Windows 10/11)
|
||||
description: How to create a connection croup with user-published and globally published packages.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to create a connection croup with user-published and globally published packages
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
You can create user-entitled connection groups that contain both user-published and globally published packages, using either of the following methods:
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to create a connection group (Windows 10)
|
||||
title: How to create a connection group (Windows 10/11)
|
||||
description: Learn how to create a connection group with the App-V Management Console and where to find information about managing connection groups.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to create a connection group
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use these steps to create a connection group by using the App-V Management Console. To use Windows PowerShell to create connection groups, see [How to manage connection groups on a stand-alone computer by using Windows PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md).
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to create a custom configuration file by using the App-V Management Console (Windows 10)
|
||||
title: How to create a custom configuration file by using the App-V Management Console (Windows 10/11)
|
||||
description: How to create a custom configuration file by using the App-V Management Console.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to create a custom configuration file by using the App-V Management Console
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
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).
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to create a package accelerator by using Windows PowerShell (Windows 10)
|
||||
title: How to create a package accelerator by using Windows PowerShell (Windows 10/11)
|
||||
description: Learn how to create an App-v Package Accelerator by using Windows PowerShell. App-V Package Accelerators automatically sequence large, complex applications.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to create a package accelerator by using Windows PowerShell
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
App-V Package Accelerators automatically sequence large, complex applications. Also, when you apply an App-V Package Accelerator, you don't have to manually install an application to create the virtualized package.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to create a package accelerator (Windows 10)
|
||||
title: How to create a package accelerator (Windows 10/11)
|
||||
description: Learn how to create App-V Package Accelerators to automatically generate new virtual application packages.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to create a package accelerator
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
App-V Package Accelerators automatically generate new virtual application packages.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to create a virtual application package using an App-V Package Accelerator (Windows 10)
|
||||
title: How to create a virtual application package using an App-V Package Accelerator (Windows 10/11)
|
||||
description: How to create a virtual application package using an App-V Package Accelerator.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to create a virtual application package using an App-V Package Accelerator
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following procedure to create a virtual application package with the App-V Package Accelerator.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Create and apply an App-V project template to a sequenced App-V package (Windows 10)
|
||||
title: Create and apply an App-V project template to a sequenced App-V package (Windows 10/11)
|
||||
description: Steps for how to create and apply an App-V project template (.appvt) to a sequenced App-V package.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,12 +14,12 @@ ms.topic: article
|
||||
---
|
||||
# Create and apply an App-V project template to a sequenced App-V package
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
You can use an App-V Project Template (.appvt) file to save commonly applied settings associated with an existing virtual application package. You can then apply these settings whenever you create new virtual application packages in your environment, streamlining the package creation process. App-V Project Templates differ from App-V Package Accelerators because App-V Package Accelerators are application-specific, while App-V Project Templates can be applied to multiple applications. To learn more about package accelerators, see [How to create a package accelerator](appv-create-a-package-accelerator.md).
|
||||
|
||||
>[!IMPORTANT]
|
||||
>In Windows 10, version 1703, running the **New-AppvSequencerPackage** or the **Update-AppvSequencerPackage** cmdlets will automatically capture and store your customizations as an App-V Project Template. If you want to make changes to this package later, you can automatically load your customizations from this template file. If you have an auto-saved template and you attempt to load another template through the *TemplateFilePath* parameter, the customization value from the parameter will override the auto-saved template.
|
||||
>Starting with Windows 10 version 1703, running the **New-AppvSequencerPackage** or the **Update-AppvSequencerPackage** cmdlets will automatically capture and store your customizations as an App-V Project Template. If you want to make changes to this package later, you can automatically load your customizations from this template file. If you have an auto-saved template and you attempt to load another template through the *TemplateFilePath* parameter, the customization value from the parameter will override the auto-saved template.
|
||||
|
||||
## Create a project template
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Creating and managing App-V virtualized applications (Windows 10)
|
||||
title: Creating and managing App-V virtualized applications (Windows 10/11)
|
||||
description: Create and manage App-V virtualized applications to monitor and record the installation process for an application to be run as a virtualized application.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Creating and managing App-V virtualized applications
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
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.
|
||||
|
||||
@ -119,7 +119,7 @@ A template can specify and store multiple settings as follows:
|
||||
- **General Options**. Enables the use of **Windows Installer**, **Append Package Version to Filename**.
|
||||
- **Exclusion Items.** Contains the Exclusion pattern list.
|
||||
|
||||
In Windows 10, version 1703, running the **new-appvsequencerpackage** or **update-appvsequencepackage** cmdlets automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file.
|
||||
Starting with Windows 10 version 1703, running the **new-appvsequencerpackage** or **update-appvsequencepackage** cmdlets automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>If you attempt to load another template through the *_TemplateFilePath_* parameter while already having an auto-saved template, the customization value from the parameter will override the auto-saved template.
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to customize virtual application extensions for a specific AD group by using the Management Console (Windows 10)
|
||||
title: How to customize virtual application extensions for a specific AD group by using the Management Console (Windows 10/11)
|
||||
description: How to customize virtual application extensions for a specific AD group by using the Management Console.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to customize virtual applications extensions for a specific AD group by using the Management Console
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following procedure to customize the virtual application extensions for an Active Directory (AD) group.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to delete a connection group (Windows 10)
|
||||
title: How to delete a connection group (Windows 10/11)
|
||||
description: Learn how to delete an existing App-V connection group in the App-V Management Console and where to find information about managing connection groups.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to delete a connection group
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following procedure to delete an existing App-V connection group.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to delete a package in the Management Console (Windows 10)
|
||||
title: How to delete a package in the Management Console (Windows 10/11)
|
||||
description: Learn how to delete a package in the App-V Management Console and where to find information about operations for App-V.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to delete a package in the Management Console
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following procedure to delete an App-V package.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Deploy the App-V Databases by Using SQL Scripts (Windows 10)
|
||||
title: How to Deploy the App-V Databases by Using SQL Scripts (Windows 10/11)
|
||||
description: Learn how to use SQL scripts to install the App-V databases and upgrade the App-V databases to a later version.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to deploy App-V packages using electronic software distribution (Windows 10)
|
||||
title: How to deploy App-V packages using electronic software distribution (Windows 10/11)
|
||||
description: Learn how use an electronic software distribution (ESD) system to deploy App-V virtual applications to App-V clients.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to deploy App-V packages using electronic software distribution
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
You can use an electronic software distribution (ESD) system to deploy App-V virtual applications to App-V clients.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Deploy the App-V Server Using a Script (Windows 10)
|
||||
title: How to Deploy the App-V Server Using a Script (Windows 10/11)
|
||||
description: 'Learn how to deploy the App-V server by using a script (appv_server_setup.exe) from the command line.'
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How to Deploy the App-V Server (Windows 10)
|
||||
description: Use these instructions to deploy the Application Virtualization (App-V) Server in App-V for Windows 10.
|
||||
title: How to Deploy the App-V Server (Windows 10/11)
|
||||
description: Use these instructions to deploy the Application Virtualization (App-V) Server in App-V for Windows 10/11.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -32,7 +32,7 @@ ms.topic: article
|
||||
1. Download the App-V server components. All five App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from either of the following locations:
|
||||
|
||||
* The [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/subscriptions/downloads/default.aspx#FileId=65215). You must have a MSDN subscription to download the MDOP ISO package from this site.
|
||||
* The [Volume Licensing Service Center](https://www.microsoft.com/licensing/default.aspx) if you're using [Windows 10 for Enterprise or Education](https://www.microsoft.com/WindowsForBusiness/windows-product-home).
|
||||
* The [Volume Licensing Service Center](https://www.microsoft.com/licensing/default.aspx) if you're using [Windows client for Enterprise or Education](https://www.microsoft.com/WindowsForBusiness/windows-product-home).
|
||||
|
||||
2. Copy the App-V server installation files to the computer on which you want to install it.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Deploying App-V (Windows 10)
|
||||
title: Deploying App-V (Windows 10/11)
|
||||
description: App-V supports several different deployment options. Learn how to complete App-V deployment at different stages in your App-V deployment.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -12,9 +12,9 @@ manager: dansimp
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
---
|
||||
# Deploying App-V for Windows 10
|
||||
# Deploying App-V for Windows client
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
App-V supports several different deployment options. Review this topic for information about the tasks that you must complete at different stages in your deployment.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Deploying Microsoft Office 2010 by Using App-V (Windows 10)
|
||||
title: Deploying Microsoft Office 2010 by Using App-V (Windows 10/11)
|
||||
description: Create Office 2010 packages for Microsoft Application Virtualization (App-V) using the App-V Sequencer or the App-V Package Accelerator.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Deploying Microsoft Office 2010 by Using App-V
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
You can create Office 2010 packages for Microsoft Application Virtualization (App-V) using one of the following methods:
|
||||
|
||||
@ -37,7 +37,7 @@ Sequencing Office 2010 is one of the main methods for creating an Office 2010 pa
|
||||
|
||||
## Creating Office 2010 App-V packages using package accelerators
|
||||
|
||||
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. The following pages will show you which package accelerator is best for creating Office 2010 App-V packages on your version of Windows:
|
||||
Office 2010 App-V packages can be created through package accelerators. Microsoft has provided package accelerators for creating Office 2010 on Windows 10/11, Windows 8, and Windows 7. The following pages will show you which package accelerator is best for creating Office 2010 App-V packages on your version of Windows:
|
||||
|
||||
* [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](https://gallery.technet.microsoft.com/App-V-50-Package-e7ef536b)
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Deploying Microsoft Office 2013 by Using App-V (Windows 10)
|
||||
title: Deploying Microsoft Office 2013 by Using App-V (Windows 10/11)
|
||||
description: Use Application Virtualization (App-V) to deliver Microsoft Office 2013 as a virtualized application to computers in your organization.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Deploying Microsoft Office 2013 by Using App-V
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the information in this article to use Application Virtualization (App-V) 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.
|
||||
|
||||
@ -73,7 +73,7 @@ Before you start, make sure that the computer on which you are installing the Of
|
||||
|
||||
You create Office 2013 App-V packages with the Office Deployment Tool. The following instructions explain how to create an Office 2013 App-V package with Volume Licensing or Subscription Licensing.
|
||||
|
||||
Create Office 2013 App-V packages on 64-bit Windows computers. Once created, the Office 2013 App-V package will run on 32-bit and 64-bit Windows 7, Windows 8.1, and Windows 10 computers.
|
||||
Create Office 2013 App-V packages on 64-bit Windows computers. Once created, the Office 2013 App-V package will run on 32-bit and 64-bit Windows 7, Windows 8.1, and Windows 10/11 computers.
|
||||
|
||||
### Download the Office Deployment Tool
|
||||
|
||||
@ -148,7 +148,7 @@ After you download the Office 2013 applications through the Office Deployment To
|
||||
|
||||
#### What you'll need to do
|
||||
|
||||
* Create the Office 2013 App-V packages on 64-bit Windows computers. However, the package will run on 32-bit and 64-bit Windows 7, Windows 8, and Windows 10 computers.
|
||||
* Create the Office 2013 App-V packages on 64-bit Windows computers. However, the package will run on 32-bit and 64-bit Windows 7, Windows 8, and Windows 10/11 computers.
|
||||
* Create an Office App-V package for either the Subscription Licensing package or Volume Licensing by using the Office Deployment Tool, then modify the **Customconfig.xml** configuration file.
|
||||
|
||||
The following table summarizes the values you need to enter in the **Customconfig.xml** file for the licensing model you’re using. The steps in the sections that follow the table will specify the exact entries you need to make.
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Deploying Microsoft Office 2016 by using App-V (Windows 10)
|
||||
title: Deploying Microsoft Office 2016 by using App-V (Windows 10/11)
|
||||
description: Use Application Virtualization (App-V) to deliver Microsoft Office 2016 as a virtualized application to computers in your organization.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Deploying Microsoft Office 2016 by using App-V
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the information in this article to use Application Virtualization (App-V) to deliver Microsoft Office 2016 as a virtualized application to computers in your organization. For information about using App-V to deliver Office 2013, see [Deploying Microsoft Office 2013 by using App-V](appv-deploying-microsoft-office-2013-with-appv.md). 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).
|
||||
|
||||
@ -64,7 +64,7 @@ The computer on which you are installing the Office Deployment Tool must have th
|
||||
| Prerequisite | Description |
|
||||
|----------------------|--------------------|
|
||||
| Prerequisite software | .Net Framework 4 |
|
||||
| Supported operating systems | 64-bit version of Windows 10<br>64-bit version of Windows 8 or 8.1<br>64-bit version of Windows 7 |
|
||||
| Supported operating systems | 64-bit version of Windows 10/11<br>64-bit version of Windows 8 or 8.1<br>64-bit version of Windows 7 |
|
||||
|
||||
>[!NOTE]
|
||||
>In this topic, the term “Office 2016 App-V package” refers to subscription licensing.
|
||||
@ -73,7 +73,7 @@ The computer on which you are installing the Office Deployment Tool must have th
|
||||
|
||||
You create Office 2016 App-V packages by using the Office Deployment Tool. The following instructions explain how to create an Office 2016 App-V package with subscription licensing.
|
||||
|
||||
Create Office 2016 App-V packages on 64-bit Windows computers. Once created, the Office 2016 App-V package will run on 32-bit and 64-bit Windows 7, Windows 8.1, and Windows 10 computers.
|
||||
Create Office 2016 App-V packages on 64-bit Windows computers. Once created, the Office 2016 App-V package will run on 32-bit and 64-bit Windows 7, Windows 8.1, and Windows 10/11 computers.
|
||||
|
||||
### Download the Office Deployment Tool
|
||||
|
||||
@ -146,7 +146,7 @@ After you download the Office 2016 applications through the Office Deployment To
|
||||
|
||||
#### What you’ll need to do
|
||||
|
||||
* Create the Office 2016 App-V packages on 64-bit Windows computers. However, the package will run on 32-bit and 64-bit Windows 7, Windows 8 or 8.1, and Windows 10 computers.
|
||||
* Create the Office 2016 App-V packages on 64-bit Windows computers. However, the package will run on 32-bit and 64-bit Windows 7, Windows 8 or 8.1, and Windows 10/11 computers.
|
||||
* Create an Office App-V package for either Subscription Licensing package by using the Office Deployment Tool, and then modify the **Customconfig.xml** configuration file.
|
||||
|
||||
The following table summarizes the values you need to enter in the **Customconfig.xml** file. The steps in the sections that follow the table will specify the exact entries you need to make.
|
||||
@ -377,7 +377,7 @@ The following table describes the requirements and options for deploying Visio 2
|
||||
|
||||
## Related topics
|
||||
|
||||
* [Deploying App-V for Windows 10](appv-deploying-appv.md)
|
||||
* [Deploying App-V for Windows client](appv-deploying-appv.md)
|
||||
* [Deploying Microsoft Office 2013 by using App-V](appv-deploying-microsoft-office-2013-with-appv.md)
|
||||
* [Deploying Microsoft Office 2010 by using App-V](appv-deploying-microsoft-office-2010-wth-appv.md)
|
||||
* [Office 2016 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117)
|
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Deploying App-V packages by using electronic software distribution (ESD)
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
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).
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Deploying the App-V Sequencer and configuring the client (Windows 10)
|
||||
title: Deploying the App-V Sequencer and configuring the client (Windows 10/11)
|
||||
description: Learn how to deploy the App-V Sequencer and configure the client by using the ADMX template and Group Policy.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Deploying the App-V Sequencer and configuring the client
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
The App-V Sequencer and client let administrators to virtualize and run virtual applications.
|
||||
|
||||
@ -23,7 +23,7 @@ The App-V Sequencer and client let administrators to virtualize and run virtual
|
||||
The App-V client is the component that runs a virtualized application on a target computer. The client lets users interact with icons and file types, starting virtualized applications. The client can also get the virtual application content from the management server.
|
||||
|
||||
>[!NOTE]
|
||||
>In Windows 10, version 1607, App-V is included with the operating system. You only need to enable it.
|
||||
>Starting with Windows 10 version 1607, App-V is included with the operating system. You only need to enable it.
|
||||
|
||||
[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)
|
||||
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Deploying the App-V Server (Windows 10)
|
||||
description: Learn how to deploy the Application Virtualization (App-V) Server in App-V for Windows 10 by using different deployment configurations described in this article.
|
||||
title: Deploying the App-V Server (Windows 10/11)
|
||||
description: Learn how to deploy the Application Virtualization (App-V) Server in App-V for Windows 10/11 by using different deployment configurations described in this article.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -19,9 +19,9 @@ ms.topic: article
|
||||
You can install the Application Virtualization (App-V) server components using different deployment configurations, which are described in this topic. Before you install the server features, review the server section of [App-V security considerations](appv-security-considerations.md).
|
||||
|
||||
>[!NOTE]
|
||||
>If you plan to use the App-V server components in your deployment, note that the version number is still listed as App-V 5.x, as the App-V server components have not changed in App-V for Windows 10.
|
||||
>If you plan to use the App-V server components in your deployment, note that the version number is still listed as App-V 5.x, as the App-V server components have not changed in App-V for Windows client.
|
||||
|
||||
To learn more about deploying App-V for Windows 10, read [What's new in App-V](appv-about-appv.md).
|
||||
To learn more about deploying App-V for Windows client, read [What's new in App-V](appv-about-appv.md).
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Before installing and configuring the App-V servers, you must specify the port or ports where each component will be hosted. You must also add the associated firewall rules to allow incoming requests to access the specified ports, as the installer does not modify firewall settings.
|
||||
@ -49,7 +49,7 @@ App-V offers the following five server components, each of which serves a specif
|
||||
All five App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from either of the following locations:
|
||||
|
||||
* The [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/subscriptions/downloads/default.aspx#FileId=65215). You must have a MSDN subscription to download the MDOP ISO package from this site.
|
||||
* The [Volume Licensing Service Center](https://www.microsoft.com/licensing/default.aspx) if you're using [Windows 10 for Enterprise or Education](https://www.microsoft.com/WindowsForBusiness/windows-product-home).
|
||||
* The [Volume Licensing Service Center](https://www.microsoft.com/licensing/default.aspx) if you're using [Windows client for Enterprise or Education](https://www.microsoft.com/WindowsForBusiness/windows-product-home).
|
||||
|
||||
In large organizations, you might want to install more than one instance of the server components to get the following benefits.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: App-V Deployment Checklist (Windows 10)
|
||||
title: App-V Deployment Checklist (Windows 10/11)
|
||||
description: Use the App-V deployment checklist to understand the recommended steps and items to consider when deploying App-V features.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# App-V Deployment Checklist
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
This checklist outlines the recommended steps and items to consider when deploying App-V features. Use it to organize your priorities while you deploy App-V. You can copy this checklist into a spreadsheet program and customize it for your use.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: About App-V Dynamic Configuration (Windows 10)
|
||||
title: About App-V Dynamic Configuration (Windows 10/11)
|
||||
description: Learn how to create or edit an existing Application Virtualization (App-V) dynamic configuration file.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# About App-V dynamic configuration
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
You can use dynamic configuration to customize an App-V package for a user. This article will tell you how to create or edit an existing dynamic configuration file.
|
||||
|
||||
@ -562,7 +562,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 included in the App-V client.
|
||||
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 client. 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
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Enable Only Administrators to Publish Packages by Using an ESD (Windows 10)
|
||||
title: How to Enable Only Administrators to Publish Packages by Using an ESD (Windows 10/11)
|
||||
description: Learn how to enable only administrators to publish packages by bsing an electronic software delivery (ESD).
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to enable only administrators to publish packages by using an ESD
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
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.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Enable Reporting on the App-V Client by Using Windows PowerShell (Windows 10)
|
||||
title: How to Enable Reporting on the App-V Client by Using Windows PowerShell (Windows 10/11)
|
||||
description: How to Enable Reporting on the App-V Client by Using Windows PowerShell
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,8 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to Enable Reporting on the App-V Client by Using Windows PowerShell
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following procedure to configure the App-V for reporting.
|
||||
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Enable the App-V in-box client (Windows 10)
|
||||
description: Learn how to enable the Microsoft Application Virtualization (App-V) in-box client installed with Windows 10.
|
||||
title: Enable the App-V in-box client (Windows 10/11)
|
||||
description: Learn how to enable the Microsoft Application Virtualization (App-V) in-box client installed with Windows 10/11.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -14,11 +14,11 @@ ms.topic: article
|
||||
---
|
||||
# Enable the App-V in-box client
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
The App-V client is the component that runs virtualized applications on user devices. Once you enable the client, users can 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. However, you'll still need to enable the client yourself to allow user devices to access and run virtual applications. You can set up the client with the Group Policy editor or with Windows PowerShell.
|
||||
Starting with Windows 10 version 1607, the App-V client is installed automatically. However, you'll still need to enable the client yourself to allow user devices to access and run virtual applications. You can set up the client with the Group Policy editor or with Windows PowerShell.
|
||||
|
||||
Here's how to enable the App-V client with Group Policy:
|
||||
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Evaluating App-V (Windows 10)
|
||||
description: Learn how to evaluate App-V for Windows 10 in a lab environment before deploying into a production environment.
|
||||
title: Evaluating App-V (Windows 10/11)
|
||||
description: Learn how to evaluate App-V for Windows 10/11 in a lab environment before deploying into a production environment.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -15,8 +15,7 @@ ms.author: greglin
|
||||
|
||||
# Evaluating App-V
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
> [!NOTE]
|
||||
> [!INCLUDE [Application Virtualization will be end of life in April 2026](../includes/app-v-end-life-statement.md)]
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Application Virtualization (App-V) (Windows 10)
|
||||
title: Application Virtualization (App-V) (Windows 10/11)
|
||||
description: See various topics that can help you administer Application Virtualization (App-V) and its components.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -12,9 +12,9 @@ manager: dansimp
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
---
|
||||
# Application Virtualization (App-V) for Windows 10 overview
|
||||
# Application Virtualization (App-V) for Windows client overview
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
> [!NOTE]
|
||||
> [!INCLUDE [Application Virtualization will be end of life in April 2026](../includes/app-v-end-life-statement.md)]
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Getting Started with App-V (Windows 10)
|
||||
description: Get started with Microsoft Application Virtualization (App-V) for Windows 10. App-V for Windows 10 delivers Win32 applications to users as virtual applications.
|
||||
title: Getting Started with App-V (Windows 10/11)
|
||||
description: Get started with Microsoft Application Virtualization (App-V) for Windows 10/11. App-V for Windows client devices delivers Win32 applications to users as virtual applications.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -12,35 +12,35 @@ manager: dansimp
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
---
|
||||
# Getting started with App-V for Windows 10
|
||||
# Getting started with App-V for Windows client
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
> [!NOTE]
|
||||
> [!INCLUDE [Application Virtualization will be end of life in April 2026](../includes/app-v-end-life-statement.md)]
|
||||
|
||||
Microsoft Application Virtualization (App-V) for Windows 10 delivers 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 an as-needed basis. Users launch virtual applications from familiar access points and interact with them as if they were installed locally.
|
||||
Microsoft Application Virtualization (App-V) for Windows delivers 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 an 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/WindowsForBusiness/windows-for-enterprise). If you're 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. To learn what you need to know before getting started with App-V, see the [Application Virtualization (App-V) overview](appv-for-windows.md).
|
||||
Starting with Windows 10 version 1607, App-V is included with the [Windows 10 for Enterprise edition](https://www.microsoft.com/WindowsForBusiness/windows-for-enterprise). If you're new to Windows client and App-V, you’ll need to download, activate, and install server- and client-side components to start delivering virtual applications to users. To learn what you need to know before getting started with App-V, see the [Application Virtualization (App-V) overview](appv-for-windows.md).
|
||||
|
||||
If you’re already using App-V, performing an in-place upgrade to Windows 10 on user devices automatically installs the App-V client and migrates users’ App-V applications and settings. For more information about how to configure an existing App-V installation after upgrading user devices to Windows 10, see [Upgrading to App-V for Windows 10 from an existing installation](appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md).
|
||||
If you’re already using App-V, performing an in-place upgrade to Windows 10/11 on user devices automatically installs the App-V client and migrates users’ App-V applications and settings. For more information about how to configure an existing App-V installation after upgrading user devices to Windows 10/11, see [Upgrading to App-V for Windows from an existing installation](appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md).
|
||||
|
||||
>[!IMPORTANT]
|
||||
>You can upgrade your existing App-V installation to App-V for Windows from App-V versions 5.0 SP2 and higher only. If you are using an earlier version of App-V, you’ll need to upgrade your existing App-V installation to App-V 5.0 SP2 before upgrading to App-V for Windows.
|
||||
|
||||
To learn more about previous versions of App-V, see [MDOP information experience](/microsoft-desktop-optimization-pack/index).
|
||||
|
||||
## Getting started with App-V for Windows 10 (new installations)
|
||||
## Getting started with App-V for Windows (new installations)
|
||||
|
||||
To start using App-V to deliver virtual applications to users, you’ll need to download, enable, and install server- and client-side components. The following table describes the App-V for Windows 10 components, what they do, and where to find them.
|
||||
To start using App-V to deliver virtual applications to users, you’ll need to download, enable, and install server- and client-side components. The following table describes the App-V for Windows client components, what they do, and where to find them.
|
||||
|
||||
<!--App-V Remote Desktop Services (RDS) client once had its own row in the table below, and could have its own row again. As of 7/29/2016, it's in the same row as App-V client -->
|
||||
|
||||
| Component | What it does | Where to find it |
|
||||
|------------|--|------|
|
||||
| App-V server components | App-V offers five server components that work together to allow you to host and publish virtual applications, generate usage reports, and manage your App-V environment. For more details, see [Deploying the App-V Server](appv-deploying-the-appv-server.md).<br><br>If you're already using App-V 5.x, you don't need to redeploy the App-V server components, as they haven't changed since App-V 5.0's release. | The App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package that can be downloaded from the following locations:<br><br> If you have a Microsoft Developer Network (MSDN) subscription, use the [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/subscriptions/downloads/default.aspx#FileId=65215) to download the MDOP ISO package.<br><br> If you're using [Windows 10 for Enterprise or Education](https://www.microsoft.com/WindowsForBusiness/windows-product-home), download it from the [Volume Licensing Service Center](https://www.microsoft.com/licensing/default.aspx).<br><br>See [Deploying the App-V Server](appv-deploying-the-appv-server.md) for more information about installing and using the server components.|
|
||||
| App-V client and App-V Remote Desktop Services (RDS) client | The App-V client is the component that runs virtualized applications on user devices, allowing users to interact with icons and file names to start virtualized applications. | The App-V client is automatically installed with Windows 10, version 1607. <br><br>To learn how to enable the client, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md). |
|
||||
| App-V sequencer | Use the App-V sequencer to convert Win32 applications into virtual packages for deployment to user devices. Devices must run the App-V client to allow users to interact with virtual applications. | Installed with the [Windows Assessment and Deployment kit (ADK) for Windows 10, version 1607](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit). |
|
||||
| App-V server components | App-V offers five server components that work together to allow you to host and publish virtual applications, generate usage reports, and manage your App-V environment. For more details, see [Deploying the App-V Server](appv-deploying-the-appv-server.md).<br><br>If you're already using App-V 5.x, you don't need to redeploy the App-V server components, as they haven't changed since App-V 5.0's release. | The App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package that can be downloaded from the following locations:<br><br> If you have a Microsoft Developer Network (MSDN) subscription, use the [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/subscriptions/downloads/default.aspx#FileId=65215) to download the MDOP ISO package.<br><br> If you're using [Windows client for Enterprise or Education](https://www.microsoft.com/WindowsForBusiness/windows-product-home), download it from the [Volume Licensing Service Center](https://www.microsoft.com/licensing/default.aspx).<br><br>See [Deploying the App-V Server](appv-deploying-the-appv-server.md) for more information about installing and using the server components.|
|
||||
| App-V client and App-V Remote Desktop Services (RDS) client | The App-V client is the component that runs virtualized applications on user devices, allowing users to interact with icons and file names to start virtualized applications. | Starting with Windows 10 version 1607, the App-V client is automatically installed. <br><br>To learn how to enable the client, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md). |
|
||||
| App-V sequencer | Use the App-V sequencer to convert Win32 applications into virtual packages for deployment to user devices. Devices must run the App-V client to allow users to interact with virtual applications. | Installed with the [Windows Assessment and Deployment kit (ADK) for Windows client](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit). |
|
||||
|
||||
For more information about these components, see [High Level Architecture for App-V](appv-high-level-architecture.md).
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: High-level architecture for App-V (Windows 10)
|
||||
title: High-level architecture for App-V (Windows 10/11)
|
||||
description: Use the information in this article to simplify your Microsoft Application Virtualization (App-V) deployment.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# High-level architecture for App-V
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following information to simplify your Microsoft Application Virtualization (App-V) deployment.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell (Windows 10)
|
||||
title: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell (Windows 10/11)
|
||||
description: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Install the Management and Reporting Databases on separate computers from the Management and Reporting Services (Windows 10)
|
||||
title: How to Install the Management and Reporting Databases on separate computers from the Management and Reporting Services (Windows 10/11)
|
||||
description: How to install the Management and Reporting Databases on separate computers from the Management and Reporting Services.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to install the Management Server on a Standalone Computer and Connect it to the Database (Windows 10)
|
||||
title: How to install the Management Server on a Standalone Computer and Connect it to the Database (Windows 10/11)
|
||||
description: How to install the Management Server on a Standalone Computer and Connect it to the Database
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Install the Publishing Server on a Remote Computer (Windows 10)
|
||||
title: Install the Publishing Server on a Remote Computer (Windows 10/11)
|
||||
description: Use the procedures in this article to install the Microsoft Application Virtualization (App-V) publishing server on a separate computer.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to install the Reporting Server on a standalone computer and connect it to the database (Windows 10)
|
||||
title: How to install the Reporting Server on a standalone computer and connect it to the database (Windows 10/11)
|
||||
description: How to install the App-V Reporting Server on a Standalone Computer and Connect it to the Database
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Install the App-V Sequencer (Windows 10)
|
||||
title: Install the App-V Sequencer (Windows 10/11)
|
||||
description: Learn how to install the App-V Sequencer to convert Win32 applications into virtual packages for deployment to user devices.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,11 +14,11 @@ ms.topic: article
|
||||
---
|
||||
# Install the App-V Sequencer
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
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).
|
||||
The App-V Sequencer is included in the Windows client Assessment and Deployment Kit (Windows ADK).
|
||||
|
||||
>[!NOTE]
|
||||
>The computer that will run the sequencer must not have the App-V client enabled. As a best practice, choose a computer with the same hardware and software configurations as the computers that will run the virtual applications. The sequencing process is resource-intensive, so make sure the computer that will run the Sequencer has plenty of memory, a fast processor, and a fast hard drive.
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help (Windows 10)
|
||||
title: How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help (Windows 10/11)
|
||||
description: How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to load the Windows PowerShell cmdlets for App-V and get cmdlet help
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
## Requirements for using Windows PowerShell cmdlets
|
||||
|
||||
@ -82,7 +82,7 @@ Starting in App-V 5.0 SP3, cmdlet help is available in two formats:
|
||||
|App-V Sequencer|**Update-Help -Module AppvSequencer**|
|
||||
|App-V Client|**Update-Help -Module AppvClient**|
|
||||
|
||||
* Online in the [Microsoft Desktop Optimization Pack](/powershell/mdop/get-started?view=win-mdop2-ps).
|
||||
* Online in the [Microsoft Desktop Optimization Pack](/powershell/mdop/get-started).
|
||||
|
||||
## Displaying the help for a Windows PowerShell cmdlet
|
||||
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Maintaining App-V (Windows 10)
|
||||
description: After you have deployed App-V for Windows 10, you can use the following information to maintain the App-V infrastructure.
|
||||
title: Maintaining App-V (Windows 10/11)
|
||||
description: After you have deployed App-V for Windows 10/11, you can use the following information to maintain the App-V infrastructure.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -14,9 +14,9 @@ ms.topic: article
|
||||
---
|
||||
# Maintaining App-V
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
After you have deployed App-V for Windows 10, you can use the following information to maintain the App-V infrastructure.
|
||||
After you have deployed App-V for Windows client, you can use the following information to maintain the App-V infrastructure.
|
||||
|
||||
## Moving the App-V server
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to manage App-V packages running on a stand-alone computer by using Windows PowerShell (Windows 10)
|
||||
title: How to manage App-V packages running on a stand-alone computer by using Windows PowerShell (Windows 10/11)
|
||||
description: How to manage App-V packages running on a stand-alone computer by using Windows PowerShell.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to manage App-V packages running on a stand-alone computer by using Windows PowerShell
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
The following sections explain how to perform various management tasks on a stand-alone client computer with Windows PowerShell cmdlets.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell (Windows 10)
|
||||
title: How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell (Windows 10/11)
|
||||
description: How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -15,8 +15,7 @@ ms.author: greglin
|
||||
|
||||
# How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
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.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Managing Connection Groups (Windows 10)
|
||||
title: Managing Connection Groups (Windows 10/11)
|
||||
description: Connection groups can allow administrators to manage packages independently and avoid having to add the same application multiple times to a client computer.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -15,8 +15,7 @@ ms.author: greglin
|
||||
|
||||
# Managing Connection Groups
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
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.
|
||||
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Migrating to App-V from a Previous Version (Windows 10)
|
||||
description: Learn how to migrate to Microsoft Application Virtualization (App-V) for Windows 10 from a previous version.
|
||||
title: Migrating to App-V from a Previous Version (Windows 10/11)
|
||||
description: Learn how to migrate to Microsoft Application Virtualization (App-V) for Windows 10/11 from a previous version.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -15,10 +15,9 @@ ms.author: greglin
|
||||
|
||||
# Migrating to App-V from previous versions
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
To migrate from App-V 4.x to App-V for Windows 10, you must upgrade to App-V 5.x first.
|
||||
To migrate from App-V 4.x to App-V for Windows 10/11, you must upgrade to App-V 5.x first.
|
||||
|
||||
## <a href="" id="bkmk-pkgconvimprove"></a>Improvements to the App-V Package Converter
|
||||
|
||||
@ -34,7 +33,7 @@ You can also use the `–OSDsToIncludeInPackage` parameter with the `ConvertFrom
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">New in App-V for Windows 10</th>
|
||||
<th align="left">New in App-V for Windows client</th>
|
||||
<th align="left">Prior to App-V for Windows 10</th>
|
||||
</tr>
|
||||
</thead>
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Modify an Existing Virtual Application Package (Windows 10)
|
||||
title: How to Modify an Existing Virtual Application Package (Windows 10/11)
|
||||
description: Learn how to modify an existing virtual application package and add a new application to an existing virtual application package.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -15,8 +15,7 @@ ms.author: greglin
|
||||
|
||||
# How to Modify an Existing Virtual Application Package
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
This topic explains how to:
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Modify Client Configuration by Using Windows PowerShell (Windows 10)
|
||||
title: How to Modify Client Configuration by Using Windows PowerShell (Windows 10/11)
|
||||
description: Learn how to modify the Application Virtualization (App-V) client configuration by using Windows PowerShell.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -15,8 +15,7 @@ ms.author: greglin
|
||||
|
||||
# How to Modify Client Configuration by Using Windows PowerShell
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following procedure to configure the App-V client configuration.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Move the App-V Server to Another Computer (Windows 10)
|
||||
title: How to Move the App-V Server to Another Computer (Windows 10/11)
|
||||
description: Learn how to create a new management server console in your environment and learn how to connect it to the App-V database.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Operations for App-V (Windows 10)
|
||||
title: Operations for App-V (Windows 10/11)
|
||||
description: Learn about the various types of App-V administration and operating tasks that are typically performed by an administrator.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Operations for App-V
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
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.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Performance Guidance for Application Virtualization (Windows 10)
|
||||
title: Performance Guidance for Application Virtualization (Windows 10/11)
|
||||
description: Learn how to configure App-V for optimal performance, optimize virtual app packages, and provide a better user experience with RDS and VDI.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -15,11 +15,13 @@ ms.author: greglin
|
||||
|
||||
# Performance Guidance for Application Virtualization
|
||||
|
||||
**Applies to**
|
||||
- Windows 7 SP1
|
||||
- Windows 10
|
||||
- Server 2012 R2
|
||||
- Server 2016
|
||||
**Applies to**:
|
||||
|
||||
- Windows 7 SP1
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
- Server 2012 R2
|
||||
- Server 2016
|
||||
|
||||
Learn how to configure App-V for optimal performance, optimize virtual app packages, and provide a better user experience with RDS and VDI.
|
||||
|
||||
@ -270,11 +272,11 @@ We recommend using User Experience Virtualization (UE-V) to capture and centrali
|
||||
|
||||
For more information, see:
|
||||
|
||||
- [User Experience Virtualization (UE-V) for Windows 10 overview](/windows/configuration/ue-v/uev-for-windows)
|
||||
- [User Experience Virtualization (UE-V) for Windows client overview](/windows/configuration/ue-v/uev-for-windows)
|
||||
|
||||
- [Get Started with UE-V](/windows/configuration/ue-v/uev-getting-started)
|
||||
|
||||
In essence all that is required is to enable the UE-V service and download the following Microsoft authored App-V settings template from the [Microsoft User Experience Virtualization (UE-V) template gallery](https://gallery.technet.microsoft.com/Authored-UE-V-Settings-bb442a33). Register the template. For more information about UE-V templates, see [User Experience Virtualization (UE-V) for Windows 10 overview](/windows/configuration/ue-v/uev-for-windows).
|
||||
In essence all that is required is to enable the UE-V service and download the following Microsoft authored App-V settings template from the [Microsoft User Experience Virtualization (UE-V) template gallery](https://gallery.technet.microsoft.com/Authored-UE-V-Settings-bb442a33). Register the template. For more information about UE-V templates, see [User Experience Virtualization (UE-V) for Windows client overview](/windows/configuration/ue-v/uev-for-windows).
|
||||
|
||||
**Note**
|
||||
Without performing an additional configuration step, User Environment Virtualization (UE-V) will not be able to synchronize the Start menu shortcuts (.lnk files) on the target computer. The .lnk file type is excluded by default.
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: App-V Planning Checklist (Windows 10)
|
||||
title: App-V Planning Checklist (Windows 10/11)
|
||||
description: Learn about the recommended steps and items to consider when planning an Application Virtualization (App-V) deployment.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# App-V Planning Checklist
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
This checklist can be used to help you plan for preparing your organization for an App-V deployment.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Planning to Use Folder Redirection with App-V (Windows 10)
|
||||
title: Planning to Use Folder Redirection with App-V (Windows 10/11)
|
||||
description: Learn about folder redirection with App-V. Folder redirection enables users and administrators to redirect the path of a folder to a new location.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Planning to Use Folder Redirection with App-V
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
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.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Planning for the App-V Server Deployment (Windows 10)
|
||||
title: Planning for the App-V Server Deployment (Windows 10/11)
|
||||
description: Learn what you need to know so you can plan for the Microsoft Application Virtualization (App-V) 5.1 server deployment.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Planning for App-V (Windows 10)
|
||||
title: Planning for App-V (Windows 10/11)
|
||||
description: Use the information in this article to plan to deploy App-V without disrupting your existing network or user experience.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Planning for App-V
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
> [!NOTE]
|
||||
> [!INCLUDE [Application Virtualization will be end of life in April 2026](../includes/app-v-end-life-statement.md)]
|
||||
|
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Planning for high availability with App-V Server
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Microsoft Application Virtualization (App-V) system configurations can take advantage of options that maintain a high available service level.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Planning for the App-V Sequencer and Client Deployment (Windows 10)
|
||||
title: Planning for the App-V Sequencer and Client Deployment (Windows 10/11)
|
||||
description: Learn what you need to do to plan for the App-V Sequencer and Client deployment, and where to find additional information about the deployment process.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Planning for the App-V Sequencer and Client Deployment
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Before you can use App-V, you must install the App-V Sequencer and enable the App-V client. You can also the App-V shared content store, although it isn't required. The following sections will tell you how to set these up.
|
||||
|
||||
@ -38,7 +38,7 @@ Ideally, you should install the sequencer on a computer running as a virtual mac
|
||||
|
||||
## Planning for App-V client deployment
|
||||
|
||||
In Windows 10, version 1607, the App-V client is included with the operating system. For more information, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
|
||||
Starting with Windows 10 version 1607, the App-V client is included with the operating system. For more information, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
|
||||
|
||||
## Planning for the App-V Shared Content Store (SCS)
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Planning for Deploying App-V with Office (Windows 10)
|
||||
title: Planning for Deploying App-V with Office (Windows 10/11)
|
||||
description: Use the information in this article to plan how to deploy Office within Microsoft Application Virtualization (App-V).
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Planning for deploying App-V with Office
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following information to plan how to deploy Office within Microsoft Application Virtualization (App-V).
|
||||
|
||||
@ -92,7 +92,7 @@ To bypass the auto-registration operation for native Word 2010, follow these ste
|
||||
|
||||
* In Windows 7k, select **Start**, type **regedit** in the Start Search box, then select the Enter key.
|
||||
|
||||
* In Windows 8.1 or Windows 10, enter **regedit**, select **Enter** on the Start page, then select the Enter key.
|
||||
* In Windows client, enter **regedit**, select **Enter** on the Start page, then select the Enter key.
|
||||
|
||||
If you're prompted for an administrator password, enter the password. If you're prompted for a confirmation, select **Continue**.
|
||||
3. Locate and then select the following registry subkey:
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Planning to Deploy App-V with an Electronic Software Distribution System (Windows 10)
|
||||
title: Planning to Deploy App-V with an Electronic Software Distribution System (Windows 10/11)
|
||||
description: Planning to Deploy App-V with an Electronic Software Distribution System
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Planning to Deploy App-V with an electronic software distribution system
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
If you are using an electronic software distribution (ESD) system to deploy App-V packages, review the following planning considerations. For information about deploying App-V with Microsoft Endpoint Configuration Manager, see [Introduction to application management in Configuration Manager](/previous-versions/system-center/system-center-2012-R2/gg682125(v=technet.10)#BKMK_Appv).
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Planning to Deploy App-V (Windows 10)
|
||||
title: Planning to Deploy App-V (Windows 10/11)
|
||||
description: Learn about the different deployment configurations and requirements to consider before you deploy App-V for Windows 10.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -12,11 +12,11 @@ manager: dansimp
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
---
|
||||
# Planning to Deploy App-V for Windows 10
|
||||
# Planning to Deploy App-V for Windows client
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
There are several different deployment configurations and requirements to consider before you deploy App-V for Windows 10. Review this topic for information about what you'll need to make a deployment plan that best meets your needs.
|
||||
There are several different deployment configurations and requirements to consider before you deploy App-V for Windows client. Review this topic for information about what you'll need to make a deployment plan that best meets your needs.
|
||||
|
||||
## App-V supported configurations
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Preparing Your Environment for App-V (Windows 10)
|
||||
title: Preparing Your Environment for App-V (Windows 10/11)
|
||||
description: Use this info to prepare for deployment configurations and prerequisites for Microsoft Application Virtualization (App-V).
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Preparing your environment for App-V
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
There are several different deployment configurations and prerequisites that you must consider before creating your deployment plan for Microsoft App-V. The following articles will help you gather the information you need to set up a deployment plan that best suits your business’ needs.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: App-V Prerequisites (Windows 10)
|
||||
title: App-V Prerequisites (Windows 10/11)
|
||||
description: Learn about the prerequisites you need before you begin installing Application Virtualization (App-V).
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -12,11 +12,12 @@ manager: dansimp
|
||||
ms.author: greglin
|
||||
ms.topic: article
|
||||
---
|
||||
# App-V for Windows 10 prerequisites
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
# App-V for Windows client prerequisites
|
||||
|
||||
Before installing App-V for Windows 10, ensure that you have installed all of the following required prerequisite software.
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Before installing App-V for Windows client, ensure that you have installed all of the following required prerequisite software.
|
||||
|
||||
For a list of supported operating systems and hardware requirements for the App-V server, sequencer, and client, see [App-V Supported Configurations](appv-supported-configurations.md).
|
||||
|
||||
@ -26,7 +27,7 @@ The following table indicates the software that is already installed for differe
|
||||
|
||||
|Operating system|Prerequisite description|
|
||||
|---|---|
|
||||
|Windows 10|All prerequisite software is already installed.|
|
||||
|Windows 10/11|All prerequisite software is already installed.|
|
||||
|Windows 8.1|All prerequisite software is already installed.<br>If you're running Windows 8, upgrade to Windows 8.1 before using App-V.|
|
||||
|Windows Server 2016|The following prerequisite software is already installed:<br>- Microsoft .NET Framework 4.5<br>- Windows PowerShell 3.0<br><br>Installing Windows PowerShell requires a restart.|
|
||||
|Windows 7|No prerequisite software is installed. You must install the software before you can install App-V.|
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Publish a Connection Group (Windows 10)
|
||||
title: How to Publish a Connection Group (Windows 10/11)
|
||||
description: Learn how to publish a connection group to computers that run the Application Virtualization (App-V) client.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to Publish a Connection Group
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
After you create a connection group, you must publish it to computers that run the App-V client.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to publish a package by using the Management console (Windows 10)
|
||||
title: How to publish a package by using the Management console (Windows 10/11)
|
||||
description: Learn how the Management console in App-V can help you enable admin controls as well as publish App-V packages.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to publish a package by using the Management console
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following procedure to publish an App-V package. Once you publish a package, computers running the App-V client can access and run the applications in that package.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Register and Unregister a Publishing Server by Using the Management Console (Windows 10)
|
||||
title: How to Register and Unregister a Publishing Server by Using the Management Console (Windows 10/11)
|
||||
description: How to Register and Unregister a Publishing Server by Using the Management Console
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -15,8 +15,7 @@ ms.author: greglin
|
||||
|
||||
# How to Register and Unregister a Publishing Server by Using the Management Console
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
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.
|
||||
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Release Notes for App-V for Windows 10, version 1703 (Windows 10)
|
||||
description: A list of known issues and workarounds for App-V running on Windows 10, version 1703.
|
||||
title: Release Notes for App-V for Windows 10 version 1703 (Windows 10/11)
|
||||
description: A list of known issues and workarounds for App-V running on Windows 10 version 1703 and Windows 11.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -13,12 +13,11 @@ ms.author: greglin
|
||||
---
|
||||
|
||||
|
||||
# Release Notes for App-V for Windows 10, version 1703
|
||||
# Release Notes for App-V for Windows 10 version 1703 and later
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1703
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
The following are known issues and workarounds for Application Virtualization (App-V) running on Windows 10, version 1703.
|
||||
The following are known issues and workarounds for Application Virtualization (App-V) running on Windows 10 version 1703 and later
|
||||
|
||||
<table border="1">
|
||||
<thead>
|
||||
@ -106,7 +105,7 @@ The following are known issues and workarounds for Application Virtualization (A
|
||||
|
||||
|
||||
## Related resources list
|
||||
For information that can help with troubleshooting App-V for Windows 10, see:
|
||||
For information that can help with troubleshooting App-V for Windows client, see:
|
||||
- [Application Virtualization (App-V): List of Microsoft Support Knowledge Base Articles](https://social.technet.microsoft.com/wiki/contents/articles/14272.app-v-v5-x-list-of-microsoft-support-knowledge-base-articles.aspx)
|
||||
|
||||
- [The Official Microsoft App-V Team Blog](/archive/blogs/appv/)
|
||||
@ -119,6 +118,6 @@ For information that can help with troubleshooting App-V for Windows 10, see:
|
||||
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
- [What's new in App-V for Windows 10](appv-about-appv.md)
|
||||
- [What's new in App-V for Windows client](appv-about-appv.md)
|
||||
|
||||
- [Release Notes for App-V for Windows 10, version 1607](appv-release-notes-for-appv-for-windows-1703.md)
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: About App-V Reporting (Windows 10)
|
||||
title: About App-V Reporting (Windows 10/11)
|
||||
description: Learn how the App-V reporting feature collects information about computers running the App-V client and virtual application package usage.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# About App-V reporting
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Application Virtualization (App-V) includes a built-in reporting feature that collects information about computers running the App-V client and virtual application package usage. You can generate reports from a centralized database with this information.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications (Windows 10)
|
||||
title: Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications (Windows 10/11)
|
||||
description: Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -18,6 +18,7 @@ ms.author: greglin
|
||||
**Applies to**
|
||||
- Windows 7 SP1
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2016
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: App-V Security Considerations (Windows 10)
|
||||
title: App-V Security Considerations (Windows 10/11)
|
||||
description: Learn about accounts and groups, log files, and other security-related considerations for Microsoft Application Virtualization (App-V).
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# App-V security considerations
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
This topic contains a brief overview of the accounts and groups, log files, and other security-related considerations for Microsoft Application Virtualization (App-V).
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10)
|
||||
title: Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10/11)
|
||||
description: Learn how to manually sequence a new app by using the App-V Sequencer that's included with the Windows ADK.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -14,9 +14,9 @@ ms.topic: article
|
||||
---
|
||||
# Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)
|
||||
|
||||
>Applies to: Windows 10, version 1607 and later
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
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).
|
||||
Starting with 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).
|
||||
|
||||
## Before you start sequencing
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to sequence a package by using Windows PowerShell (Windows 10)
|
||||
title: How to sequence a package by using Windows PowerShell (Windows 10/11)
|
||||
description: Learn how to sequence a new Microsoft Application Virtualization (App-V) package by using Windows PowerShell.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -15,8 +15,7 @@ ms.author: greglin
|
||||
|
||||
# How to Sequence a Package by using Windows PowerShell
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following procedure to create a new App-V package using Windows PowerShell.
|
||||
|
||||
@ -63,7 +62,7 @@ The following list displays additional optional parameters that can be used with
|
||||
|
||||
- FullLoad - specifies that the package must be fully downloaded to the computer running the App-V before it can be opened.
|
||||
|
||||
In Windows 10, version 1703, running the new-appvsequencerpackage or the update-appvsequencepackage cmdlets automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file.
|
||||
Starting with Windows 10 version 1703, the `new-appvsequencerpackage` or the `update-appvsequencepackage` cmdlets automatically capture and store all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template.
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: App-V Supported Configurations (Windows 10)
|
||||
description: Learn the requirements to install and run App-V supported configurations in your Windows 10 environment.
|
||||
title: App-V Supported Configurations (Windows 10/11)
|
||||
description: Learn the requirements to install and run App-V supported configurations in your Windows 10/11 environment.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -14,9 +14,17 @@ ms.topic: article
|
||||
---
|
||||
# App-V Supported Configurations
|
||||
|
||||
>Applies to: Windows 10, version 1607; Window Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 (Extended Security Update)
|
||||
**Applies to**:
|
||||
|
||||
This topic specifies the requirements to install and run App-V in your Windows 10 environment. For information about prerequisite software such as the .NET Framework, see [App-V prerequisites](appv-prerequisites.md).
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
- Window Server 2019
|
||||
- Windows Server 2016
|
||||
- Windows Server 2012 R2
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2 (Extended Security Update)
|
||||
|
||||
This topic specifies the requirements to install and run App-V in your Windows client environment. For information about prerequisite software such as the .NET Framework, see [App-V prerequisites](appv-prerequisites.md).
|
||||
|
||||
## App-V Server system requirements
|
||||
|
||||
@ -98,7 +106,7 @@ The following table lists the SQL Server versions that are supported for the App
|
||||
|
||||
## App-V client and Remote Desktop Services client requirements
|
||||
|
||||
With Windows 10, version 1607 and later releases, the App-V client is included with Windows 10 Enterprise and Windows 10 Education. The App-V client is no longer part of the Microsoft Desktop Optimization Pack. Before you can use the App-V client, it must be enabled, as described in [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
|
||||
Starting with Windows 10 version 1607, the App-V client is included with Windows Enterprise and Windows Education. The App-V client is no longer part of the Microsoft Desktop Optimization Pack. Before you can use the App-V client, it must be enabled, as described in [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
|
||||
|
||||
Similarly, the App-V Remote Desktop Services (RDS) client is included with Windows Server 2016 Standard and Windows Server 2016 Datacenter.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Technical Reference for App-V (Windows 10)
|
||||
title: Technical Reference for App-V (Windows 10/11)
|
||||
description: Learn strategy and context for many performance optimization practices in this technical reference for Application Virtualization (App-V).
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -15,8 +15,7 @@ ms.author: greglin
|
||||
|
||||
# Technical Reference for App-V
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
This section provides reference information related to managing App-V.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console (Windows 10)
|
||||
title: How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console (Windows 10/11)
|
||||
description: How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -15,8 +15,7 @@ ms.author: greglin
|
||||
|
||||
# How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following procedure to transfer the access and default package configurations to another version of a package by using the management console.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Troubleshooting App-V (Windows 10)
|
||||
title: Troubleshooting App-V (Windows 10/11)
|
||||
description: Learn how to find information about troubleshooting Application Virtualization (App-V) and information about other App-V topics.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -15,10 +15,9 @@ ms.author: greglin
|
||||
|
||||
# Troubleshooting App-V
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
For information that can help with troubleshooting App-V for Windows 10, see:
|
||||
For information that can help with troubleshooting App-V for Windows client, see:
|
||||
|
||||
- [Application Virtualization (App-V): List of Microsoft Support Knowledge Base Articles](https://social.technet.microsoft.com/wiki/contents/articles/14272.app-v-v5-x-list-of-microsoft-support-knowledge-base-articles.aspx)
|
||||
|
||||
@ -33,9 +32,9 @@ For information that can help with troubleshooting App-V for Windows 10, see:
|
||||
|
||||
## Other resources
|
||||
|
||||
- [Application Virtualization (App-V) for Windows 10 overview](appv-for-windows.md)
|
||||
- [Application Virtualization (App-V) for Windows client overview](appv-for-windows.md)
|
||||
|
||||
- [Getting Started with App-V for Windows 10](appv-getting-started.md)
|
||||
- [Getting Started with App-V for Windows client](appv-getting-started.md)
|
||||
|
||||
- [Planning for App-V](appv-planning-for-appv.md)
|
||||
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Upgrading to App-V for Windows 10 from an existing installation (Windows 10)
|
||||
description: Learn about upgrading to Application Virtualization (App-V) for Windows 10 from an existing installation.
|
||||
title: Upgrading to App-V for Windows 10/11 from an existing installation (Windows 10/11)
|
||||
description: Learn about upgrading to Application Virtualization (App-V) for Windows 10/11 from an existing installation.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -12,14 +12,13 @@ manager: dansimp
|
||||
ms.author: greglin
|
||||
---
|
||||
|
||||
# Upgrading to App-V for Windows 10 from an existing installation
|
||||
# Upgrading to App-V for Windows client from an existing installation
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
If you’re already using App-V and you’re planning to upgrade user devices to Windows 10, you need to make only the following few adjustments to your existing environment to start using App-V for Windows 10.
|
||||
If you’re already using App-V and you’re planning to upgrade user devices to Windows 10/11, you need to make only the following few adjustments to your existing environment to start using App-V for Windows client.
|
||||
|
||||
1. [Upgrade user devices to Windows 10](#upgrade-user-devices-to-windows-10). Performing an in-place upgrade automatically installs the App-V client and migrates users’ App-V applications and settings.
|
||||
1. [Upgrade user devices to Windows 10/11](#upgrade-user-devices-to-windows-1011). Performing an in-place upgrade automatically installs the App-V client and migrates users’ App-V applications and settings.
|
||||
|
||||
2. [Verify that App-V applications and settings were migrated correctly](#verify-that-app-v-applications-and-settings-were-migrated-correctly).
|
||||
|
||||
@ -31,13 +30,13 @@ If you’re already using App-V and you’re planning to upgrade user devices to
|
||||
|
||||
These steps are explained in more detail below.
|
||||
|
||||
## Upgrade user devices to Windows 10
|
||||
## Upgrade user devices to Windows 10/11
|
||||
|
||||
Performing an in-place upgrade automatically installs the App-V client and migrates users’ App-V applications and settings. See the [Windows 10 and Windows 10 Mobile document set](/windows/windows-10/) for information about upgrading user devices to Windows 10.
|
||||
Performing an in-place upgrade automatically installs the App-V client and migrates users’ App-V applications and settings. See the [Windows document set](/windows/windows-10/) for information about upgrading user devices.
|
||||
|
||||
## Verify that App-V applications and settings were migrated correctly
|
||||
|
||||
After upgrading a user device to Windows 10, it’s important to verify that App-V applications and settings were migrated correctly during the upgrade.
|
||||
After upgrading a user device, it’s important to verify that App-V applications and settings were migrated correctly during the upgrade.
|
||||
|
||||
To verify that the user’s App-V application packages were migrated correctly, type `Get-AppvClientPackage` in Windows PowerShell.
|
||||
|
||||
@ -45,7 +44,7 @@ To verify that the user’s App-V settings were migrated correctly, type `Get-Ap
|
||||
|
||||
## Enable the in-box App-V client
|
||||
|
||||
With Windows 10, 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.
|
||||
With Windows 10/11, 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.
|
||||
|
||||
**To enable the App-V client with Group Policy**
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Using the App-V Client Management Console (Windows 10)
|
||||
title: Using the App-V Client Management Console (Windows 10/11)
|
||||
description: Learn how to use the Application Virtualization (App-V) client management console to manage packages on the computer running the App-V client.
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -15,8 +15,7 @@ ms.author: greglin
|
||||
|
||||
# Using the App-V Client Management Console
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
This topic provides information about using the Application Virtualization (App-V) client management console to manage packages on the computer running the App-V client.
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console (Windows 10)
|
||||
title: How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console (Windows 10/11)
|
||||
description: How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console
|
||||
author: greg-lindsay
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -15,8 +15,7 @@ ms.author: greglin
|
||||
|
||||
# How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
Use the following procedure to view and configure default package extensions.
|
||||
|
||||
|
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