mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 06:17:22 +00:00
Merged PR 9016: Next round of App-V revision
Updated five articles for App-V for voice, tone, and formatting.
This commit is contained in:
Heidi Lohr
commit
aa4a64da37
@ -1,42 +1,46 @@
|
|||||||
---
|
---
|
||||||
title: How to Apply the Deployment Configuration File by Using Windows PowerShell (Windows 10)
|
title: How to apply the deployment configuration file by using Windows PowerShell (Windows 10)
|
||||||
description: How to Apply the Deployment Configuration File by Using Windows PowerShell
|
description: How to apply the deployment configuration file by using Windows PowerShell for Windows 10.
|
||||||
author: MaggiePucciEvans
|
author: MaggiePucciEvans
|
||||||
ms.pagetype: mdop, appcompat, virtualization
|
ms.pagetype: mdop, appcompat, virtualization
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.date: 04/19/2017
|
ms.date: 06/15/2018
|
||||||
---
|
---
|
||||||
|
# How to apply the deployment configuration file by using Windows PowerShell
|
||||||
|
|
||||||
|
>Applies to: Windows 10, version 1607
|
||||||
|
|
||||||
# How to Apply the Deployment Configuration File by Using Windows PowerShell
|
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.
|
||||||
|
|
||||||
**Applies to**
|
## Apply the deployment configuration file with Windows PowerShell
|
||||||
- Windows 10, version 1607
|
|
||||||
|
|
||||||
The dynamic deployment configuration file is applied when a package is added or set to a computer running the App-V client before the package has been published. The file configures the default settings for package for all users on the computer running the App-V client. This section describes the steps used to use a deployment configuration file. The procedure is based on the following example and assumes the following package and configuration files exist on a computer:
|
>[!NOTE]
|
||||||
|
>The following example cmdlet uses the following two file paths for the package and configuration files:
|
||||||
|
>
|
||||||
|
>* C:\\Packages\\Contoso\\MyApp.appv
|
||||||
|
>* C:\\Packages\\Contoso\\DynamicConfigurations\\deploymentconfig.xml
|
||||||
|
>
|
||||||
|
>If your package and configuration files use different file paths than the example, feel free to replace them as needed.
|
||||||
|
|
||||||
**c:\\Packages\\Contoso\\MyApp.appv**
|
To specify a new default set of configurations for all users who will run the package on a specific computer, in a Windows PowerShell console, enter the following cmdlet:
|
||||||
|
|
||||||
**c:\\Packages\\Contoso\\DynamicConfigurations\\deploymentconfig.xml**
|
```PowerShell
|
||||||
|
Add-AppVClientPackage -Path C:\Packages\Contoso\MyApp.appv -DynamicDeploymentConfiguration C:\Packages\Contoso\DynamicConfigurations\deploymentconfig.xml
|
||||||
|
```
|
||||||
|
|
||||||
**To Apply the Deployment Configuration File Using Windows PowerShell**
|
>[!NOTE]
|
||||||
|
>This command captures the resulting object into $pkg. If the package is already present on the computer, you can use the **Set-AppVclientPackage** cmdlet to apply the deployment configuration document:
|
||||||
|
>
|
||||||
|
> ```PowerShell
|
||||||
|
> Set-AppVClientPackage -Name Myapp -Path C:\Packages\Contoso\MyApp.appv -DynamicDeploymentConfiguration C:\Packages\Contoso\DynamicConfigurations\deploymentconfig.xml
|
||||||
|
> ```
|
||||||
|
|
||||||
- To specify a new default set of configurations for all users who will run the package on a specific computer, in a Windows PowerShell console, type the following:
|
|
||||||
|
|
||||||
`Add-AppVClientPackage -Path c:\Packages\Contoso\MyApp.appv -DynamicDeploymentConfiguration c:\Packages\Contoso\DynamicConfigurations\deploymentconfig.xml`
|
|
||||||
|
|
||||||
**Note**<br>
|
|
||||||
This command captures the resulting object into $pkg. If the package is already present on the computer, the **Set-AppVclientPackage** cmdlet can be used to apply the deployment configuration document:
|
|
||||||
|
|
||||||
`Set-AppVClientPackage -Name Myapp -Path c:\Packages\Contoso\MyApp.appv -DynamicDeploymentConfiguration c:\Packages\Contoso\DynamicConfigurations\deploymentconfig.xml`
|
|
||||||
|
|
||||||
|
|
||||||
## Have a suggestion for App-V?
|
## Have a suggestion for App-V?
|
||||||
|
|
||||||
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
[Operations for App-V](appv-operations.md)
|
* [Operations for App-V](appv-operations.md)
|
||||||
|
|||||||
@ -1,41 +1,45 @@
|
|||||||
---
|
---
|
||||||
title: 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)
|
||||||
description: How to Apply the User Configuration File by Using Windows PowerShell
|
description: How to apply the user configuration file by using Windows PowerShell (Windows 10).
|
||||||
author: MaggiePucciEvans
|
author: MaggiePucciEvans
|
||||||
ms.pagetype: mdop, appcompat, virtualization
|
ms.pagetype: mdop, appcompat, virtualization
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.date: 04/19/2017
|
ms.date: 06/15/2018
|
||||||
---
|
---
|
||||||
|
# How to apply the user configuration file by using Windows PowerShell
|
||||||
|
|
||||||
|
>Applies to: Windows 10, version 1607
|
||||||
|
|
||||||
# How to Apply the User Configuration File by Using Windows PowerShell
|
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.
|
||||||
|
|
||||||
**Applies to**
|
## Apply a user configuration file
|
||||||
- Windows 10, version 1607
|
|
||||||
|
|
||||||
The dynamic user configuration file is applied when a package is published to a specific user and determines how the package will run.
|
Here's how to specify a user-specific configuration file:
|
||||||
|
|
||||||
Use the following procedure to specify a user-specific configuration file. The following procedure is based on the example:
|
>[!NOTE]
|
||||||
|
>The following example cmdlets use this example file path for its package:
|
||||||
|
>
|
||||||
|
>* C:\\Packages\\Contoso\\MyApp.appv.
|
||||||
|
>
|
||||||
|
>If your package file uses a different file path than the example, feel free to replace it as needed.
|
||||||
|
|
||||||
**c:\\Packages\\Contoso\\MyApp.appv**
|
1. Enter the following cmdlet in Windows PowerShell to add the package to the computer:
|
||||||
|
|
||||||
**To apply a user Configuration file**
|
```PowerShell
|
||||||
|
Add-AppVClientPackage C:\Packages\Contoso\MyApp.appv
|
||||||
1. To add the package to the computer using the Windows PowerShell console, type the following command:
|
```
|
||||||
|
2. Enter the following cmdlet to publish the package to the user and specify the updated the dynamic user configuration file:
|
||||||
`Add-AppVClientPackage c:\Packages\Contoso\MyApp.appv`
|
|
||||||
|
|
||||||
2. Use the following command to publish the package to the user and specify the updated the dynamic user configuration file:
|
|
||||||
|
|
||||||
`Publish-AppVClientPackage $pkg -DynamicUserConfigurationPath c:\Packages\Contoso\config.xml`
|
|
||||||
|
|
||||||
|
```PowerShell
|
||||||
|
Publish-AppVClientPackage $pkg -DynamicUserConfigurationPath C:\Packages\Contoso\config.xml
|
||||||
|
```
|
||||||
|
|
||||||
## Have a suggestion for App-V?
|
## Have a suggestion for App-V?
|
||||||
|
|
||||||
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
[Operations for App-V](appv-operations.md)
|
* [Operations for App-V](appv-operations.md)
|
||||||
|
|||||||
@ -1,77 +1,62 @@
|
|||||||
---
|
---
|
||||||
title: Automatically clean up unpublished packages on the App-V client (Windows 10)
|
title: Automatically clean up unpublished packages on the App-V client (Windows 10)
|
||||||
description: How to automatically clean-up any unpublished packages on your App-V client devices.
|
description: How to automatically clean up any unpublished packages on your App-V client devices.
|
||||||
author: eross-msft
|
author: eross-msft
|
||||||
ms.pagetype: mdop, appcompat, virtualization
|
ms.pagetype: mdop, appcompat, virtualization
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.date: 04/19/2017
|
ms.date: 06/15/2018
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
||||||
# Automatically clean up unpublished packages on the App-V client
|
# Automatically clean up unpublished packages on the App-V client
|
||||||
|
|
||||||
**Applies to**
|
>Applies to: Windows 10, version 1703
|
||||||
- Windows 10, version 1703
|
|
||||||
|
|
||||||
Previous versions of App-V have required you to manually remove your unpublished packages from your client devices, to free up additional storage space. Windows 10, version 1703 introduces the ability to use PowerShell or Group Policy settings to automatically cleanup your unpublished packages after a device restart.
|
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.
|
||||||
|
|
||||||
## Cleanup by using PowerShell commands
|
## Clean up with PowerShell cmdlets
|
||||||
Using PowerShell, you can turn on the **AutoCleanupEnabled** setting to automatically cleanup your unpublished App-V packages from your App-V client devices.
|
|
||||||
|
|
||||||
**To turn on the AutoCleanupEnabled option**
|
You can enter PowerShell cmdlets to turn on the **AutoCleanupEnabled** setting, which will automatically clean up your unpublished App-V packages from your App-V client devices.
|
||||||
|
|
||||||
1. Open PowerShell as an admin and run the following command to turn on the automatic package cleanup functionality:
|
### Turn on the AutoCleanupEnabled option
|
||||||
|
|
||||||
```ps1
|
1. Open PowerShell as an admin and enter the following cmdlet to turn on the automatic package cleanup functionality:
|
||||||
|
|
||||||
|
```PowerShell
|
||||||
Set-AppvClientConfiguration -AutoCleanupEnabled 1
|
Set-AppvClientConfiguration -AutoCleanupEnabled 1
|
||||||
```
|
```
|
||||||
|
|
||||||
The command runs and you should see the following info on the PowerShell screen:
|
After running the cmdlet, you should see the following info on the PowerShell screen:
|
||||||
|
|
||||||
<table border="1">
|
|Name|Value|SetbyGroupPolicy|
|
||||||
<tr>
|
|---|---|---|
|
||||||
<thead>
|
|AutoCleanupEnabled|1|False|
|
||||||
<th>Name</th>
|
|
||||||
<th>Value</th>
|
|
||||||
<th>SetbyGroupPolicy</th>
|
|
||||||
</thead>
|
|
||||||
</tr>
|
|
||||||
<tbody>
|
|
||||||
<tr>
|
|
||||||
<td>AutoCleanupEnabled</td>
|
|
||||||
<td>1</td>
|
|
||||||
<td>False</td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
2. Run the following command to make sure the configuration is ready to automatically cleanup your packages.
|
1. Run the following cmdlet to check if the configuration has the cleanup setting turned on.
|
||||||
|
|
||||||
```ps1
|
```PowerShell
|
||||||
Get-AppvClientConfiguration
|
Get-AppvClientConfiguration
|
||||||
```
|
```
|
||||||
You should see the **AutoCleanupEnabled** option turned on (shows a value of "1") in the configuration list.
|
If the **AutoCleanupEnabled** option shows a value of **1** in the configuration list, that means the setting is turned on.
|
||||||
|
|
||||||
## Cleanup by using Group Policy settings
|
## Clean up with Group Policy settings
|
||||||
Using Group Policy, you can turn on the **Enable automatic cleanup of unused appv packages** setting to automatically cleanup your unpublished App-V packages from your App-V client devices.
|
|
||||||
|
|
||||||
**To turn on the Enable automatic cleanup of unused appv packages setting**
|
Using Group Policy, you can turn on the **Enable automatic cleanup of unused App-V packages** setting to automatically clean up your unpublished App-V packages from your App-V client devices.
|
||||||
|
|
||||||
1. Open your Group Policy editor and double-click the Administrative Templates\System\App-V\PackageManagement\Enable automatic cleanup of unused appv packages setting.
|
### Turn on the Enable automatic cleanup of unused App-V packages setting
|
||||||
|
|
||||||
2. Click **Enabled**, and then click **OK**.
|
1. Open your Group Policy editor and select the **Administrative Templates\System\App-V\PackageManagement\Enable automatic cleanup of unused App-V packages** setting.
|
||||||
|
|
||||||
After your Group Policy updates, the setting is turned on and will cleanup any unpublished App-V packages on the App-V Client after restarting.
|
2. Select **Enabled**, then select **OK**.
|
||||||
|
|
||||||
|
After your Group Policy updates and you reset the client, the setting will clean up any unpublished App-V packages on the App-V client.
|
||||||
|
|
||||||
|
## Have a suggestion for App-V?
|
||||||
|
|
||||||
|
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
### Related topics
|
|
||||||
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
|
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
|
||||||
|
|
||||||
- [Download the Microsoft Application Virtualization 5.0 Client UI Application](https://www.microsoft.com/en-us/download/details.aspx?id=41186)
|
- [Download the Microsoft Application Virtualization 5.0 Client UI Application](https://www.microsoft.com/en-us/download/details.aspx?id=41186)
|
||||||
|
|
||||||
- [Using the App-V Client Management Console](appv-using-the-client-management-console.md)
|
- [Using the App-V Client Management Console](appv-using-the-client-management-console.md)
|
||||||
|
|
||||||
|
|
||||||
**Have a suggestion for App-V?**<p>
|
|
||||||
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
|
||||||
@ -6,207 +6,26 @@ ms.pagetype: mdop, appcompat, virtualization
|
|||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.date: 04/19/2017
|
ms.date: 06/15/2018
|
||||||
---
|
---
|
||||||
|
|
||||||
# Available Mobile Device Management (MDM) settings for App-V
|
# Available Mobile Device Management (MDM) settings for App-V
|
||||||
With Windows 10, version 1703, you can configure, deploy, and manage your App-V apps by using these Mobile Device Management (MDM) settings. For the full list of available settings, see the [EnterpriseAppVManagement CSP](https://msdn.microsoft.com/en-us/windows/hardware/commercialize/customize/mdm/enterpriseappvmanagement-csp) page.
|
|
||||||
|
|
||||||
<table>
|
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](https://msdn.microsoft.com/en-us/windows/hardware/commercialize/customize/mdm/enterpriseappvmanagement-csp) page.
|
||||||
<tr>
|
|
||||||
<th>Policy name</th>
|
|Policy name|Supported versions|URI full path|Data type|Values|
|
||||||
<th>Supported versions</th>
|
|---|---|---|---|---|
|
||||||
<th>Details</th>
|
|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.|
|
||||||
</tr>
|
|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.|
|
||||||
<tr>
|
|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.|
|
||||||
<td>Name</td>
|
|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.|
|
||||||
<td>Windows 10, version 1703</td>
|
|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.|
|
||||||
<td>
|
|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.|
|
||||||
<ul>
|
|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.|
|
||||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<em><enterprise_id></em>/<em><package_family_name></em>/<em><package_full_name></em>/Name</li>
|
|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.|
|
||||||
<li><strong>Data type.</strong> String</li>
|
|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.|
|
||||||
<li><strong>Value.</strong> Read-only data, provided by your App-V packages.</li>
|
|LastError|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/<br>AppVPublishing/LastSync/LastError|String|Read-only data, provided by your App-V packages.|
|
||||||
</ul>
|
|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.|
|
||||||
</td>
|
|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.|
|
||||||
</tr>
|
|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.|
|
||||||
<tr>
|
|PublishXML|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/<br>AppVPublishing/Sync/PublishXML|String|Custom value, entered by admin.|
|
||||||
<td>Version</td>
|
|Policy|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/<br>AppVDynamicPolicy/configurationid/Policy|String|Custom value, entered by admin.|
|
||||||
<td>Windows 10, version 1703</td>
|
|
||||||
<td>
|
|
||||||
<ul>
|
|
||||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<em><enterprise_id></em>/<em><package_family_name></em>/<em><package_full_name></em>/Version</li>
|
|
||||||
<li><strong>Data type.</strong> String</li>
|
|
||||||
<li><strong>Value.</strong> Read-only data, provided by your App-V packages.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Publisher</td>
|
|
||||||
<td>Windows 10, version 1703</td>
|
|
||||||
<td>
|
|
||||||
<ul>
|
|
||||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<em><enterprise_id></em>/<em><package_family_name></em>/<em><package_full_name></em>/Publisher</li>
|
|
||||||
<li><strong>Data type.</strong> String</li>
|
|
||||||
<li><strong>Value.</strong> Read-only data, provided by your App-V packages.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>InstallLocation</td>
|
|
||||||
<td>Windows 10, version 1703</td>
|
|
||||||
<td>
|
|
||||||
<ul>
|
|
||||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<em><enterprise_id></em>/<em><package_family_name></em>/<em><package_full_name></em>/InstallLocation</li>
|
|
||||||
<li><strong>Data type.</strong> String</li>
|
|
||||||
<li><strong>Value.</strong> Read-only data, provided by your App-V packages.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>InstallDate</td>
|
|
||||||
<td>Windows 10, version 1703</td>
|
|
||||||
<td>
|
|
||||||
<ul>
|
|
||||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<em><enterprise_id></em>/<em><package_family_name></em>/<em><package_full_name></em>/InstallDate</li>
|
|
||||||
<li><strong>Data type.</strong> String</li>
|
|
||||||
<li><strong>Value.</strong> Read-only data, provided by your App-V packages.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Users</td>
|
|
||||||
<td>Windows 10, version 1703</td>
|
|
||||||
<td>
|
|
||||||
<ul>
|
|
||||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<em><enterprise_id></em>/<em><package_family_name></em>/<em><package_full_name></em>/Users</li>
|
|
||||||
<li><strong>Data type.</strong> String</li>
|
|
||||||
<li><strong>Value.</strong> Read-only data, provided by your App-V packages.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>AppVPackageID</td>
|
|
||||||
<td>Windows 10, version 1703</td>
|
|
||||||
<td>
|
|
||||||
<ul>
|
|
||||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<em><enterprise_id></em>/<em><package_family_name></em>/<em><package_full_name></em>/AppVPackageID</li>
|
|
||||||
<li><strong>Data type.</strong> String</li>
|
|
||||||
<li><strong>Value.</strong> Read-only data, provided by your App-V packages.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>AppVVersionID</td>
|
|
||||||
<td>Windows 10, version 1703</td>
|
|
||||||
<td>
|
|
||||||
<ul>
|
|
||||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<em><enterprise_id></em>/<em><package_family_name></em>/<em><package_full_name></em>/AppVVersionID</li>
|
|
||||||
<li><strong>Data type.</strong> String</li>
|
|
||||||
<li><strong>Value.</strong> Read-only data, provided by your App-V packages.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>AppVPackageUri</td>
|
|
||||||
<td>Windows 10, version 1703</td>
|
|
||||||
<td>
|
|
||||||
<ul>
|
|
||||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<em><enterprise_id></em>/<em><package_family_name></em>/<em><package_full_name></em>/AppVPackageUri</li>
|
|
||||||
<li><strong>Data type.</strong> String</li>
|
|
||||||
<li><strong>Value.</strong> Read-only data, provided by your App-V packages.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>LastError</td>
|
|
||||||
<td>Windows 10, version 1703</td>
|
|
||||||
<td>
|
|
||||||
<ul>
|
|
||||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastError</li>
|
|
||||||
<li><strong>Data type.</strong> String</li>
|
|
||||||
<li><strong>Value.</strong> Read-only data, provided by your App-V client.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>LastErrorDescription</td>
|
|
||||||
<td>Windows 10, version 1703</td>
|
|
||||||
<td>
|
|
||||||
<ul>
|
|
||||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastErrorDescription</li>
|
|
||||||
<li><strong>Data type.</strong> String</li>
|
|
||||||
<li><strong>Values.</strong>
|
|
||||||
<ul>
|
|
||||||
<li><strong>0.</strong> No errors returned during publish.</li>
|
|
||||||
<li><strong>1.</strong> Unpublish groups failed during publish.</li>
|
|
||||||
<li><strong>2.</strong> Publish no-group packages failed during publish.</li>
|
|
||||||
<li><strong>3.</strong> Publish group packages failed during publish.</li>
|
|
||||||
<li><strong>4.</strong> Unpublish packages failed during publish.</li>
|
|
||||||
<li><strong>5.</strong> New policy write failed during publish.</li>
|
|
||||||
<li><strong>6.</strong> Multiple non-fatal errors occurred during publish.</li>
|
|
||||||
</ul>
|
|
||||||
</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>SyncStatusDescription</td>
|
|
||||||
<td>Windows 10, version 1703</td>
|
|
||||||
<td>
|
|
||||||
<ul>
|
|
||||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncStatusDescription</li>
|
|
||||||
<li><strong>Data type.</strong> String</li>
|
|
||||||
<li><strong>Values.</strong>
|
|
||||||
<ul>
|
|
||||||
<li><strong>0.</strong> App-V publishing is idle.</li>
|
|
||||||
<li><strong>1.</strong> App-V connection groups publish in progress.</li>
|
|
||||||
<li><strong>2.</strong> App-V packages (non-connection group) publish in progress.</li>
|
|
||||||
<li><strong>3.</strong> App-V packages (connection group) publish in progress.</li>
|
|
||||||
<li><strong>4.</strong> App-V packages unpublish in progress.</li>
|
|
||||||
</ul>
|
|
||||||
</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>SyncProgress</td>
|
|
||||||
<td>Windows 10, version 1703</td>
|
|
||||||
<td>
|
|
||||||
<ul>
|
|
||||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncProgress</li>
|
|
||||||
<li><strong>Data type.</strong> String</li>
|
|
||||||
<li><strong>Values.</strong>
|
|
||||||
<ul>
|
|
||||||
<li><strong>0.</strong> App-V Sync is idle.</li>
|
|
||||||
<li><strong>1.</strong> App-V Sync is initializing.</li>
|
|
||||||
<li><strong>2.</strong> App-V Sync is in progress.</li>
|
|
||||||
<li><strong>3.</strong> App-V Sync is complete.</li>
|
|
||||||
<li><strong>4.</strong> App-V Sync requires device reboot.</li>
|
|
||||||
</ul>
|
|
||||||
</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>PublishXML</td>
|
|
||||||
<td>Windows 10, version 1703</td>
|
|
||||||
<td>
|
|
||||||
<ul>
|
|
||||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/Sync/PublishXML</li>
|
|
||||||
<li><strong>Data type.</strong> String</li>
|
|
||||||
<li><strong>Value.</strong> Custom value, entered by admin.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
<tr>
|
|
||||||
<td>Policy</td>
|
|
||||||
<td>Windows 10, version 1703</td>
|
|
||||||
<td>
|
|
||||||
<ul>
|
|
||||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVDynamicPolicy/configurationid/Policy</li>
|
|
||||||
<li><strong>Data type.</strong> String</li>
|
|
||||||
<li><strong>Value.</strong> Custom value, entered by admin.</li>
|
|
||||||
</ul>
|
|
||||||
</td>
|
|
||||||
</tr>
|
|
||||||
</table>
|
|
||||||
@ -1,67 +1,60 @@
|
|||||||
---
|
---
|
||||||
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)
|
||||||
description: How to Configure Access to Packages by Using the Management Console
|
description: How to configure access to packages by using the App-V Management console.
|
||||||
author: MaggiePucciEvans
|
author: MaggiePucciEvans
|
||||||
ms.pagetype: mdop, appcompat, virtualization
|
ms.pagetype: mdop, appcompat, virtualization
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.date: 04/19/2017
|
ms.date: 06/15/2018
|
||||||
---
|
---
|
||||||
|
# How to configure access to packages by using the Management console
|
||||||
|
|
||||||
|
>Applies to: Windows 10, version 1607
|
||||||
# How to Configure Access to Packages by Using the Management Console
|
|
||||||
|
|
||||||
**Applies to**
|
|
||||||
- Windows 10, version 1607
|
|
||||||
|
|
||||||
Before you deploy an App-V virtualized package, you must configure the Active Directory Domain Services (AD DS) security groups that will be allowed to access and run the applications. The security groups may contain computers or users. Entitling a package to a computer group publishes the package globally to all computers in the group.
|
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.
|
||||||
|
|
||||||
Use the following procedure to configure access to virtualized packages.
|
Use the following procedure to configure access to virtualized packages.
|
||||||
|
|
||||||
**To grant access to an App-V package**
|
## Grant access to an App-V package
|
||||||
|
|
||||||
1. Find the package you want to configure:
|
1. Find the package you want to configure:
|
||||||
|
|
||||||
1. Open the App-V Management console.
|
1. Open the App-V Management console.
|
||||||
|
|
||||||
2. To display the **AD ACCESS** page, right-click the package to be configured, and select **Edit active directory access**. Alternatively, select the package and click **EDIT** in the **AD ACCESS** pane.
|
1. Right-click the package to be configured, then select **Edit active directory access** to display the **AD Access** page. Alternatively, select the package and select **Edit** in the **AD Access** pane.
|
||||||
|
|
||||||
2. Provision a security group for the package:
|
2. Provision a security group for the package:
|
||||||
|
|
||||||
1. Go to the **FIND VALID ACTIVE DIRECTORY NAMES AND GRANT ACCESS** page.
|
1. Go to the **Find valid Active Directory names and grant access** page.
|
||||||
|
|
||||||
2. Using the format **mydomain** \\ **groupname**, type the name or part of the name of an Active Directory group object, and click **Check**.
|
1. Using the format **mydomain** \\ **groupname**, enter the name or part of the name of an Active Directory group object, then select **Check**.
|
||||||
|
|
||||||
**Note**
|
>[!NOTE]
|
||||||
Ensure that you provide an associated domain name for the group that you are searching for.
|
>Ensure that you provide an associated domain name for the group that you are searching for.
|
||||||
|
|
||||||
|
3. Grant access to the package by first selecting the desired group, then selecting **Grant Access**. The newly added group is displayed in the **AD entities with access** pane.
|
||||||
|
|
||||||
3. To grant access to the package, select the desired group and click **Grant Access**. The newly added group is displayed in the **AD ENTITIES WITH ACCESS** pane.
|
4. Select **Close** to accept the default configuration settings and close the AD Access page.
|
||||||
|
|
||||||
4.
|
To customize configurations for a specific group, select the **Assigned configurations** drop-down menu, then select **Custom**. To make changes to your custom configurations, select **Edit**. After you grant access, select **Close**.
|
||||||
|
|
||||||
To accept the default configuration settings and close the **AD ACCESS** page, click **Close**.
|
## Remove access to an App-V package
|
||||||
|
|
||||||
To customize configurations for a specific group, click the **ASSIGNED CONFIGURATIONS** drop-down and select **Custom**. To configure the custom configurations, click **EDIT**. After you grant access, click **Close**.
|
|
||||||
|
|
||||||
**To remove access to an App-V package**
|
|
||||||
|
|
||||||
1. Find the package you want to configure:
|
1. Find the package you want to configure:
|
||||||
|
|
||||||
1. Open the App-V Management console.
|
1. Open the App-V Management console.
|
||||||
|
|
||||||
2. To display the **AD ACCESS** page, right-click the package to be configured, and select **Edit active directory access**. Alternatively, select the package and click **EDIT** in the **AD ACCESS** pane.
|
1. To display the **AD Access** page, right-click the package to be configured, then select **Edit active directory access**. Alternatively, select the package, then select **Edit** in the **AD Access** pane.
|
||||||
|
|
||||||
2. Select the group you want to remove, and click **DELETE**.
|
2. Select the group you want to remove, then select **Delete**.
|
||||||
|
|
||||||
3. To close the **AD ACCESS** page, click **Close**.
|
3. Select **Close**.
|
||||||
|
|
||||||
## Have a suggestion for App-V?
|
## Have a suggestion for App-V?
|
||||||
|
|
||||||
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
[Operations for App-V](appv-operations.md)
|
* [Operations for App-V](appv-operations.md)
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user