deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 10:23:37 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Acrolinx enhancement effort

Browse Source
This commit is contained in:
Siddarth Mandalika
2022-03-29 17:18:17 +05:30
parent 61f8dc827a
commit c038667431
16 changed files with 250 additions and 250 deletions
Download Patch File Download Diff File Expand all files Collapse all files

42
windows/client-management/mdm/policy-csp-appvirtualization.md
View File

@ -361,15 +361,15 @@ ADMX Info:
<!--Description-->
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.
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, for example, 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 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 deletion occurs, and won't 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.
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 report data is being transmitted 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 components won't factor into the block size calculations; the potential exists for a large package list to result in transmission failures over low bandwidth or unreliable connections.
<!--/Description-->
@ -412,7 +412,7 @@ ADMX Info:
<!--/Scope-->
<!--Description-->
Specifies the file paths relative to %userprofile% that do not roam with a user's profile. Example usage: /FILEEXCLUSIONLIST='desktop;my pictures'.
Specifies the file paths relative to %userprofile% that don't roam with a user's profile. Example usage: /FILEEXCLUSIONLIST='desktop;my pictures'.
<!--/Description-->
@ -455,7 +455,7 @@ ADMX Info:
<!--/Scope-->
<!--Description-->
Specifies the registry paths that do not roam with a user profile. Example usage: /REGISTRYEXCLUSIONLIST=software\classes;software\clients.
Specifies the registry paths that don't roam with a user profile. Example usage: /REGISTRYEXCLUSIONLIST=software\classes;software\clients.
<!--/Description-->
@ -541,7 +541,7 @@ ADMX Info:
<!--/Scope-->
<!--Description-->
Migration mode allows the App-V client to modify shortcuts and FTA's for packages created using a previous version of App-V.
Migration mode allows the App-V client to modify shortcuts and FTAs for packages created using a previous version of App-V.
<!--/Description-->
@ -584,7 +584,7 @@ ADMX Info:
<!--/Scope-->
<!--Description-->
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.
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 aren't used during publishing. Example: %localappdata%\Microsoft\AppV\Client\Integration.
<!--/Description-->
@ -627,7 +627,7 @@ ADMX Info:
<!--/Scope-->
<!--Description-->
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.
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 aren't used during publishing. Example: %allusersprofile%\Microsoft\AppV\Client\Integration.
<!--/Description-->
@ -676,7 +676,7 @@ 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 On Logon: Triggers a global publishing refresh on a sign in(Boolean).
Global Publishing Refresh Interval: Specifies the publishing refresh interval using the GlobalRefreshIntervalUnit. To disable package refresh, select 0.
@ -684,7 +684,7 @@ Global Publishing Refresh Interval Unit: Specifies the interval unit (Hour 0-23,
User Publishing Refresh: Enables user publishing refresh (Boolean).
User Publishing Refresh On Logon: Triggers a user publishing refresh on logon (Boolean).
User Publishing Refresh On Logon: Triggers a user publishing refresh on a sign in (Boolean).
User Publishing Refresh Interval: Specifies the publishing refresh interval using the UserRefreshIntervalUnit. To disable package refresh, select 0.
@ -737,7 +737,7 @@ 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 On Logon: Triggers a global publishing refresh on a sign in (Boolean).
Global Publishing Refresh Interval: Specifies the publishing refresh interval using the GlobalRefreshIntervalUnit. To disable package refresh, select 0.
@ -745,7 +745,7 @@ Global Publishing Refresh Interval Unit: Specifies the interval unit (Hour 0-23,
User Publishing Refresh: Enables user publishing refresh (Boolean).
User Publishing Refresh On Logon: Triggers a user publishing refresh on logon (Boolean).
User Publishing Refresh On Logon: Triggers a user publishing refresh on la sign in (Boolean).
User Publishing Refresh Interval: Specifies the publishing refresh interval using the UserRefreshIntervalUnit. To disable package refresh, select 0.
@ -798,7 +798,7 @@ 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 On Logon: Triggers a global publishing refresh on a sign in (Boolean).
Global Publishing Refresh Interval: Specifies the publishing refresh interval using the GlobalRefreshIntervalUnit. To disable package refresh, select 0.
@ -806,7 +806,7 @@ Global Publishing Refresh Interval Unit: Specifies the interval unit (Hour 0-23,
User Publishing Refresh: Enables user publishing refresh (Boolean).
User Publishing Refresh On Logon: Triggers a user publishing refresh on logon (Boolean).
User Publishing Refresh On Logon: Triggers a user publishing refresh on a sign in (Boolean).
User Publishing Refresh Interval: Specifies the publishing refresh interval using the UserRefreshIntervalUnit. To disable package refresh, select 0.
@ -859,7 +859,7 @@ 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 On Logon: Triggers a global publishing refresh on a sign in (Boolean).
Global Publishing Refresh Interval: Specifies the publishing refresh interval using the GlobalRefreshIntervalUnit. To disable package refresh, select 0.
@ -867,7 +867,7 @@ Global Publishing Refresh Interval Unit: Specifies the interval unit (Hour 0-23,
User Publishing Refresh: Enables user publishing refresh (Boolean).
User Publishing Refresh On Logon: Triggers a user publishing refresh on logon (Boolean).
User Publishing Refresh On Logon: Triggers a user publishing refresh on a sign in (Boolean).
User Publishing Refresh Interval: Specifies the publishing refresh interval using the UserRefreshIntervalUnit. To disable package refresh, select 0.
@ -920,7 +920,7 @@ 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 On Logon: Triggers a global publishing refresh on a sign in (Boolean).
Global Publishing Refresh Interval: Specifies the publishing refresh interval using the GlobalRefreshIntervalUnit. To disable package refresh, select 0.
@ -928,7 +928,7 @@ Global Publishing Refresh Interval Unit: Specifies the interval unit (Hour 0-23,
User Publishing Refresh: Enables user publishing refresh (Boolean).
User Publishing Refresh On Logon: Triggers a user publishing refresh on logon (Boolean).
User Publishing Refresh On Logon: Triggers a user publishing refresh on a sign in (Boolean).
User Publishing Refresh Interval: Specifies the publishing refresh interval using the UserRefreshIntervalUnit. To disable package refresh, select 0.
@ -1018,7 +1018,7 @@ ADMX Info:
<!--/Scope-->
<!--Description-->
This setting controls whether virtualized applications are launched on Windows 8 machines connected via a metered network connection (e.g. 4G).
This setting controls whether virtualized applications are launched on Windows 8 machines connected via a metered network connection (for example, 4G).
<!--/Description-->
@ -1276,7 +1276,7 @@ ADMX Info:
<!--/Scope-->
<!--Description-->
Specifies that streamed package contents will be not be saved to the local hard disk.
Specifies that streamed package contents won't be saved to the local hard disk.
<!--/Description-->
@ -1319,7 +1319,7 @@ ADMX Info:
<!--/Scope-->
<!--Description-->
If enabled, the App-V client will support BrancheCache compatible HTTP streaming. If BranchCache support is not desired, this should be disabled. The client can then apply HTTP optimizations which are incompatible with BranchCache
If enabled, the App-V client will support BrancheCache compatible HTTP streaming. If BranchCache support isn't desired, this setting should be disabled. The client can then apply HTTP optimizations that are incompatible with BranchCache.
<!--/Description-->