mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
New round of revisions
This commit is contained in:
Heidi Lohr
@ -1,6 +1,6 @@
|
||||
---
|
||||
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
|
||||
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 for Windows 10.
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -8,35 +8,42 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
# 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
|
||||
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 of 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. The procedure is based on the following example and assumes the following package and configuration files exist on a computer:
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
* C:\\Packages\\Contoso\\MyApp.appv
|
||||
* C:\\Packages\\Contoso\\DynamicConfigurations\\deploymentconfig.xml
|
||||
|
||||
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:
|
||||
## Apply the deployment configuration file with Windows PowerShell
|
||||
|
||||
**c:\\Packages\\Contoso\\MyApp.appv**
|
||||
>[!NOTE]
|
||||
>The following procedure is an example that 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 file use different file paths than the example, feel free to replace them as needed.
|
||||
|
||||
**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, enter the following cmdlet:
|
||||
|
||||
**To Apply the Deployment Configuration File Using Windows PowerShell**
|
||||
```PowerShell
|
||||
Add-AppVClientPackage -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:
|
||||
>[!NOTE]
|
||||
>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:
|
||||
>
|
||||
```PowerShell
|
||||
Set-AppVClientPackage -Name Myapp -Path C:\Packages\Contoso\MyApp.appv -DynamicDeploymentConfiguration C:\Packages\Contoso\DynamicConfigurations\deploymentconfig.xml
|
||||
```
|
||||
|
||||
`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?
|
||||
|
||||
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
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
* [Operations for App-V](appv-operations.md)
|
||||
|
||||
@ -8,34 +8,42 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
# How to apply the user configuration file by using Windows PowerShell
|
||||
|
||||
|
||||
# How to Apply the User Configuration File by Using Windows PowerShell
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
>Applies to: Windows 10, version 1607
|
||||
|
||||
The dynamic user configuration file is applied when a package is published to a specific user and determines how the package will run.
|
||||
|
||||
Use the following procedure to specify a user-specific configuration file. The following procedure is based on the example:
|
||||
|
||||
**c:\\Packages\\Contoso\\MyApp.appv**
|
||||
* C:\\Packages\\Contoso\\MyApp.appv
|
||||
|
||||
**To apply a user Configuration file**
|
||||
## Apply a user configuration file
|
||||
|
||||
1. To add the package to the computer using the Windows PowerShell console, type the following command:
|
||||
Use the following procedure to specify a user-specific configuration file.
|
||||
|
||||
`Add-AppVClientPackage c:\Packages\Contoso\MyApp.appv`
|
||||
>[!NOTE]
|
||||
>The following procedure uses the following example file path for its package:
|
||||
>
|
||||
>* C:\\Packages\\Contoso\\MyApp.appv.
|
||||
>
|
||||
>f your package file uses a different file path than the example, feel free to replace it.
|
||||
|
||||
2. Use the following command to publish the package to the user and specify the updated the dynamic user configuration file:
|
||||
1. Enter the following cmdlet to add the package to the computer using the Windows PowerShell console:
|
||||
|
||||
`Publish-AppVClientPackage $pkg -DynamicUserConfigurationPath c:\Packages\Contoso\config.xml`
|
||||
```PowerShell
|
||||
Add-AppVClientPackage C:\Packages\Contoso\MyApp.appv
|
||||
```
|
||||
2. Enter the following cmdlet to publish the package to the user and specify the updated the dynamic user configuration file:
|
||||
|
||||
```PowerShell
|
||||
Publish-AppVClientPackage $pkg -DynamicUserConfigurationPath c:\Packages\Contoso\config.xml
|
||||
```
|
||||
|
||||
## 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
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
* [Operations for App-V](appv-operations.md)
|
||||
|
||||
@ -8,70 +8,55 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
# Automatically clean up unpublished packages on the App-V client
|
||||
|
||||
>Applies to: Windows 10, version 1703
|
||||
|
||||
# Automatically cleanup unpublished packages on the App-V client
|
||||
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 clean up your unpublished packages after a device restart.
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1703
|
||||
## Clean up with PowerShell cmdlets
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
## Cleanup by using PowerShell commands
|
||||
Using PowerShell, you can turn on the **AutoCleanupEnabled** setting to automatically cleanup your unpublished App-V packages from your App-V client devices.
|
||||
### Turn on the AutoCleanupEnabled option
|
||||
|
||||
**To turn on the AutoCleanupEnabled option**
|
||||
1. Open PowerShell as an admin and enter the following cmdlet to turn on the automatic package clean up functionality:
|
||||
|
||||
1. Open PowerShell as an admin and run the following command to turn on the automatic package cleanup functionality:
|
||||
|
||||
```ps1
|
||||
```PowerShell
|
||||
Set-AppvClientConfiguration -AutoCleanupEnabled 1
|
||||
```
|
||||
|
||||
The command runs and you should see the following info on the PowerShell screen:
|
||||
|
||||
<table border="1">
|
||||
<tr>
|
||||
<thead>
|
||||
<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>
|
||||
After running the cmdlet, you should see the following info on the PowerShell screen:
|
||||
|
||||
2. Run the following command to make sure the configuration is ready to automatically cleanup your packages.
|
||||
|Name|Value|SetbyGroupPolicy|
|
||||
|---|---|---|
|
||||
|AutoCleanupEnabled|1|False|
|
||||
|
||||
```ps1
|
||||
2. Run the following cmdlet to make sure the configuration is ready to automatically clean up your packages.
|
||||
|
||||
```PowerShell
|
||||
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
|
||||
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.
|
||||
## Clean up with Group Policy settings
|
||||
|
||||
**To turn on the Enable automatic cleanup of unused appv packages setting**
|
||||
Using Group Policy, you can turn on the **Enable automatic clean up 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 clean up 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.
|
||||
|
||||
### Related topics
|
||||
|
||||
- [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)
|
||||
|
||||
- [Using the App-V Client Management Console](appv-using-the-client-management-console.md)
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
**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).
|
||||
Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
|
||||
@ -8,9 +8,28 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
|
||||
# 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.
|
||||
|
||||
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.
|
||||
|
||||
|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||||
|
||||
|Publisher|Windows 10, version 1703||||
|
||||
|InstallLocation|Windows 10, version 1703||||
|
||||
|InstallDate|Windows 10, version 1703||||
|
||||
|Users|Windows 10, version 1703||||
|
||||
|AppVPackageID|Windows 10, version 1703||||
|
||||
|AppVVersionID|Windows 10, version 1703||||
|
||||
|AppVPackageUri|Windows 10, version 1703||||
|
||||
|LastError|Windows 10, version 1703||||
|
||||
|LastErrorDescription|Windows 10, version 1703||||
|
||||
|SyncStatusDescription|Windows 10, version 1703||||
|
||||
|SyncProgress|Windows 10, version 1703||||
|
||||
|PublishXML|Windows 10, version 1703||||
|
||||
|Policy|Windows 10, version 1703||||
|
||||
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
|
||||
Reference in New Issue
Block a user