This policy setting allows you to enable or disable Microsoft Application Virtualization (App-V) feature. Reboot is needed for disable to take effect.

Tip

This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see Understanding ADMX-backed policies.

You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to Enabling a policy.

The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see CDATA Sections.

ADMX Info:

GP English name: Enable App-V Client
GP name: EnableAppV
GP path: System/App-V
GP ADMX file name: appv.admx

AppVirtualization/AllowDynamicVirtualization

Home	Pro	Business	Enterprise	Education	Mobile	Mobile Enterprise

Scope:

[!div class = "checklist"]

Device

Enables Dynamic Virtualization of supported shell extensions, browser helper objects, and ActiveX controls.

Tip

This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see Understanding ADMX-backed policies.

You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to Enabling a policy.

The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see CDATA Sections.

ADMX Info:

GP English name: Enable Dynamic Virtualization
GP name: Virtualization_JITVEnable
GP path: System/App-V/Virtualization
GP ADMX file name: appv.admx

AppVirtualization/AllowPackageCleanup

Home	Pro	Business	Enterprise	Education	Mobile	Mobile Enterprise

Scope:

[!div class = "checklist"]

Device

Enables automatic cleanup of appv packages that were added after Windows10 anniversary release.

Tip

This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see Understanding ADMX-backed policies.

You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to Enabling a policy.

The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see CDATA Sections.

ADMX Info:

GP English name: Enable automatic cleanup of unused appv packages
GP name: PackageManagement_AutoCleanupEnable
GP path: System/App-V/PackageManagement
GP ADMX file name: appv.admx

AppVirtualization/AllowPackageScripts

Home	Pro	Business	Enterprise	Education	Mobile	Mobile Enterprise

Scope:

[!div class = "checklist"]

Device

Enables scripts defined in the package manifest of configuration files that should run.

Tip

This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see Understanding ADMX-backed policies.

You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to Enabling a policy.

The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see CDATA Sections.

ADMX Info:

GP English name: Enable Package Scripts
GP name: Scripting_Enable_Package_Scripts
GP path: System/App-V/Scripting
GP ADMX file name: appv.admx

AppVirtualization/AllowPublishingRefreshUX

Home	Pro	Business	Enterprise	Education	Mobile	Mobile Enterprise

Scope:

[!div class = "checklist"]

Device

Enables a UX to display to the user when a publishing refresh is performed on the client.

Tip

This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see Understanding ADMX-backed policies.

You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to Enabling a policy.

The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see CDATA Sections.

ADMX Info:

GP English name: Enable Publishing Refresh UX
GP name: Enable_Publishing_Refresh_UX
GP path: System/App-V/Publishing
GP ADMX file name: appv.admx

AppVirtualization/AllowReportingServer

Home	Pro	Business	Enterprise	Education	Mobile	Mobile Enterprise

Scope:

[!div class = "checklist"]

Device

Reporting Server URL: Displays the URL of reporting server.

Reporting Time: When the client data should be reported to the server. Acceptable range is 0~23, corresponding to the 24 hours in a day. A good practice is, don't set this time to a busy hour, e.g. 9AM.

Delay reporting for the random minutes: The maximum minutes of random delay on top of the reporting time. For a busy system, the random delay will help reduce the server load.

Repeat reporting for every (days): The periodical interval in days for sending the reporting data.

Data Cache Limit: This value specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The default value is 20 MB. The size applies to the cache in memory. When the limit is reached, the log file will roll over. When a new record is to be added (bottom of the list), one or more of the oldest records (top of the list) will be deleted to make room. A warning will be logged to the Client log and the event log the first time this occurs, and will not be logged again until after the cache has been successfully cleared on transmission and the log has filled up again.

Data Block Size: This value specifies the maximum size in bytes to transmit to the server at once on a reporting upload, to avoid permanent transmission failures when the log has reached a significant size. The default value is 65536. When transmitting report data to the server, one block at a time of application records that is less than or equal to the block size in bytes of XML data will be removed from the cache and sent to the server. Each block will have the general Client data and global package list data prepended, and these will not factor into the block size calculations; the potential exists for an extremely large package list to result in transmission failures over low bandwidth or unreliable connections.

Tip

This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see Understanding ADMX-backed policies.

You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to Enabling a policy.

The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see CDATA Sections.

ADMX Info:

GP English name: Reporting Server
GP name: Reporting_Server_Policy
GP path: System/App-V/Reporting
GP ADMX file name: appv.admx

AppVirtualization/AllowRoamingFileExclusions

Home	Pro	Business	Enterprise	Education	Mobile	Mobile Enterprise

Scope:

[!div class = "checklist"]

Device

Specifies the file paths relative to %userprofile% that do not roam with a user's profile. Example usage: /FILEEXCLUSIONLIST='desktop;my pictures'.

Tip

This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see Understanding ADMX-backed policies.

You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to Enabling a policy.

The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see CDATA Sections.

ADMX Info:

GP English name: Roaming File Exclusions
GP name: Integration_Roaming_File_Exclusions
GP path: System/App-V/Integration
GP ADMX file name: appv.admx

AppVirtualization/AllowRoamingRegistryExclusions

Home	Pro	Business	Enterprise	Education	Mobile	Mobile Enterprise

Scope:

[!div class = "checklist"]

Device

Specifies the registry paths that do not roam with a user profile. Example usage: /REGISTRYEXCLUSIONLIST=software\classes;software\clients.

Tip

This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see Understanding ADMX-backed policies.

You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to Enabling a policy.

The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see CDATA Sections.

ADMX Info:

GP English name: Roaming Registry Exclusions
GP name: Integration_Roaming_Registry_Exclusions
GP path: System/App-V/Integration
GP ADMX file name: appv.admx

AppVirtualization/AllowStreamingAutoload

Home	Pro	Business	Enterprise	Education	Mobile	Mobile Enterprise

Scope:

[!div class = "checklist"]

Device

Specifies how new packages should be loaded automatically by App-V on a specific computer.

Tip

This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see Understanding ADMX-backed policies.

You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to Enabling a policy.

The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see CDATA Sections.

ADMX Info:

GP English name: Specify what to load in background (aka AutoLoad)
GP name: Steaming_Autoload
GP path: System/App-V/Streaming
GP ADMX file name: appv.admx

AppVirtualization/ClientCoexistenceAllowMigrationmode

Home	Pro	Business	Enterprise	Education	Mobile	Mobile Enterprise

Scope:

[!div class = "checklist"]

Device

Migration mode allows the App-V client to modify shortcuts and FTA's for packages created using a previous version of App-V.

Tip

This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see Understanding ADMX-backed policies.

You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to Enabling a policy.

The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see CDATA Sections.

ADMX Info:

GP English name: Enable Migration Mode
GP name: Client_Coexistence_Enable_Migration_mode
GP path: System/App-V/Client Coexistence
GP ADMX file name: appv.admx

AppVirtualization/IntegrationAllowRootGlobal

Home	Pro	Business	Enterprise	Education	Mobile	Mobile Enterprise

Scope:

[!div class = "checklist"]

Device

Specifies the location where symbolic links are created to the current version of a per-user published package. Shortcuts, file type associations, etc. are created pointing to this path. If empty, symbolic links are not used during publishing. Example: %localappdata%\Microsoft\AppV\Client\Integration.

Tip

This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see Understanding ADMX-backed policies.

You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to Enabling a policy.

The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see CDATA Sections.

ADMX Info:

GP English name: Integration Root User
GP name: Integration_Root_User
GP path: System/App-V/Integration
GP ADMX file name: appv.admx

AppVirtualization/IntegrationAllowRootUser

Home	Pro	Business	Enterprise	Education	Mobile	Mobile Enterprise

Scope:

[!div class = "checklist"]

Device

Specifies the location where symbolic links are created to the current version of a globally published package. Shortcuts, file type associations, etc. are created pointing to this path. If empty, symbolic links are not used during publishing. Example: %allusersprofile%\Microsoft\AppV\Client\Integration.

Tip

This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see Understanding ADMX-backed policies.

You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to Enabling a policy.

The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see CDATA Sections.

ADMX Info:

GP English name: Integration Root Global
GP name: Integration_Root_Global
GP path: System/App-V/Integration
GP ADMX file name: appv.admx

AppVirtualization/PublishingAllowServer1

Home	Pro	Business	Enterprise	Education	Mobile	Mobile Enterprise

Scope:

[!div class = "checklist"]

Device

Publishing Server Display Name: Displays the name of publishing server.

Publishing Server URL: Displays the URL of publishing server.

Global Publishing Refresh: Enables global publishing refresh (Boolean).

Global Publishing Refresh On Logon: Triggers a global publishing refresh on logon (Boolean).

Global Publishing Refresh Interval: Specifies the publishing refresh interval using the GlobalRefreshIntervalUnit. To disable package refresh, select 0.

Global Publishing Refresh Interval Unit: Specifies the interval unit (Hour 0-23, Day 0-31).

User Publishing Refresh: Enables user publishing refresh (Boolean).

User Publishing Refresh On Logon: Triggers a user publishing refresh on logon (Boolean).

User Publishing Refresh Interval: Specifies the publishing refresh interval using the UserRefreshIntervalUnit. To disable package refresh, select 0.

User Publishing Refresh Interval Unit: Specifies the interval unit (Hour 0-23, Day 0-31).

Tip

This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see Understanding ADMX-backed policies.

You must specify the data type in the SyncML as <Format>chr</Format>. For an example SyncML, refer to Enabling a policy.

The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see CDATA Sections.

ADMX Info:

GP English name: Publishing Server 1 Settings
GP name: Publishing_Server1_Policy
GP path: System/App-V/Publishing
GP ADMX file name: appv.admx

AppVirtualization/PublishingAllowServer2

Home	Pro	Business	Enterprise	Education	Mobile	Mobile Enterprise