mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
app-v round 2
This commit is contained in:
MandiOhlinger
parent
98c3af8c5a
commit
0323970096
@ -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.
|
||||
|
||||
|
||||
@ -14,10 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)
|
||||
|
||||
**Applies to**:
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
[!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.
|
||||
|
||||
|
||||
@ -14,10 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)
|
||||
|
||||
**Applies to**:
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
[!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.
|
||||
|
||||
|
||||
@ -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
|
||||
|
||||
|
||||
@ -14,10 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)
|
||||
|
||||
**Applies to**:
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
[!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. 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.
|
||||
|
||||
|
||||
@ -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
|
||||
|
||||
@ -14,10 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# About Client Configuration Settings
|
||||
|
||||
**Applies to**:
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
[!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).
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
@ -14,10 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to create a package accelerator
|
||||
|
||||
**Applies to**:
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
|
||||
|
||||
App-V Package Accelerators automatically generate new virtual application packages.
|
||||
|
||||
|
||||
@ -14,10 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# How to create a virtual application package using an App-V Package Accelerator
|
||||
|
||||
**Applies to**:
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
[!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.
|
||||
|
||||
|
||||
@ -14,10 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Create and apply an App-V project template to a sequenced App-V package
|
||||
|
||||
**Applies to**:
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
[!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).
|
||||
|
||||
|
||||
@ -14,10 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Creating and managing App-V virtualized applications
|
||||
|
||||
**Applies to**:
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
[!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.
|
||||
|
||||
|
||||
@ -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 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: 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
|
||||
|
||||
|
||||
@ -14,10 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Application Virtualization (App-V) for Windows client overview
|
||||
|
||||
**Applies to**:
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
[!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: 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,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: 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.
|
||||
|
||||
|
||||
@ -0,0 +1,15 @@
|
||||
---
|
||||
author: MandiOhlinger
|
||||
ms.author: mandia
|
||||
ms.date: 09/28/2021
|
||||
ms.reviewer:
|
||||
audience: itpro
|
||||
manager: dansimp
|
||||
ms.prod: w10
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
**Applies to**:
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
Loading…
x
Reference in New Issue
Block a user