Tag: Computer Configuration
Limit the BITS Peercache size
This policy setting limits the maximum amount of disk space that can be used for the BITS peer cache as a percentage of the total system disk size. BITS will add files to the peer cache and make those files available to peers until the cache content reaches the specified cache size. By default BITS will use 1 percent of the total system disk for the peercache. If you enable this policy setting you can enter the percentage of disk space to be used for the BITS peer cache. You can enter a value between 1 percent and 80 percent. If you disable or do not configure this policy setting the default size of the BITS peer cache is 1 percent of the total system disk size. Note: This policy setting has no effect if the “Allow BITS peer caching” setting is disabled or not configured.
Limit the age of files in the BITS Peercache
This policy setting limits the maximum age of files in the Background Intelligent Transfer Service (BITS) peer cache. In order to make the most efficient use of disk space by default BITS removes any files in the peer cache that have not been accessed in the past 90 days. If you enable this policy setting you can specify in days the maximum age of files in the cache. You can enter a value between 1 and 120 days. If you disable or do not configure this policy setting files that have not been accessed for the past 90 days will be removed from the peer cache. Note: This policy setting has no effect if the “Allow BITS Peercaching” policy setting is disabled or not configured.
Allow BITS Peercaching
This policy setting determines if the Background Intelligent Transfer Service (BITS) peer caching feature is enabled on a specific computer. By default the files in a BITS job are downloaded only from the origin server specified by the job’s owner. If BITS peer caching is enabled BITS caches downloaded files and makes them available to other BITS peers. When transferring a download job BITS first requests the files for the job from its peers in the same IP subnet. If none of the peers in the subnet have the requested files BITS downloads them from the origin server. If you enable this policy setting BITS downloads files from peers caches the files and responds to content requests from peers. Using the “Do not allow the computer to act as a BITS peer caching server” and “Do not allow the computer to act as a BITS peer caching client” policy settings it is possible to control BITS peer caching functionality at a more detailed level. However it should be noted that the “Allow BITS peer caching” policy setting must be enabled for the other two policy settings to have any effect. If you disable or do not configure this policy setting the BITS peer caching feature will be disabled and BITS will download files directly from the origin server.
Set up a maintenance schedule to limit the maximum network bandwidth used for BITS background transfers
This policy setting limits the network bandwidth that Background Intelligent Transfer Service (BITS) uses for background transfers during the maintenance days and hours. Maintenance schedules further limit the network bandwidth that is used for background transfers. If you enable this policy setting you can define a separate set of network bandwidth limits and set up a schedule for the maintenance period. You can specify a limit to use for background jobs during a maintenance schedule. For example if normal priority jobs are currently limited to 256 Kbps on a work schedule you can further limit the network bandwidth of normal priority jobs to 0 Kbps from 8:00 A. M. to 10:00 A. M. on a maintenance schedule. If you disable or do not configure this policy setting the limits defined for work or nonwork schedules will be used. Note: The bandwidth limits that are set for the maintenance period supersede any limits defined for work and other schedules.
Set up a work schedule to limit the maximum network bandwidth used for BITS background transfers
This policy setting limits the network bandwidth that Background Intelligent Transfer Service (BITS) uses for background transfers during the work and nonwork days and hours. The work schedule is defined using a weekly calendar which consists of days of the week and hours of the day. All hours and days that are not defined in a work schedule are considered non-work hours. If you enable this policy setting you can set up a schedule for limiting network bandwidth during both work and nonwork hours. After the work schedule is defined you can set the bandwidth usage limits for each of the three BITS background priority levels: high normal and low. You can specify a limit to use for background jobs during a work schedule. For example you can limit the network bandwidth of low priority jobs to 128 Kbps from 8:00 A. M. to 5:00 P. M. on Monday through Friday and then set the limit to 512 Kbps for nonwork hours. If you disable or do not configure this policy setting BITS uses all available unused bandwidth for background job transfers.
Limit the maximum network bandwidth for BITS background transfers
This policy setting limits the network bandwidth that Background Intelligent Transfer Service (BITS) uses for background transfers. (This policy setting does not affect foreground transfers. ) You can specify a limit to use during a specific time interval and at all other times. For example limit the use of network bandwidth to 10 Kbps from 8:00 A. M. to 5:00 P. M. and use all available unused bandwidth the rest of the day’s hours. If you enable this policy setting BITS will limit its bandwidth usage to the specified values. You can specify the limit in kilobits per second (Kbps). If you specify a value less than 2 kilobits BITS will continue to use approximately 2 kilobits. To prevent BITS transfers from occurring specify a limit of 0. If you disable or do not configure this policy setting BITS uses all available unused bandwidth. Note: You should base the limit on the speed of the network link not the computer’s network interface card (NIC). This policy setting does not affect Peercaching transfers between peer computers (it does affect transfers from the origin server); the “Limit the maximum network bandwidth used for Peercaching” policy setting should be used for that purpose. Consider using this setting to prevent BITS transfers from competing for network bandwidth when the client computer has a fast network card (10Mbs) but is connected to the network via a slow link (56Kbs).
Limit the maximum BITS job download time
This policy setting limits the amount of time that Background Intelligent Transfer Service (BITS) will take to download the files in a BITS job. The time limit applies only to the time that BITS is actively downloading files. When the cumulative download time exceeds this limit the job is placed in the error state. By default BITS uses a maximum download time of 90 days (7776000 seconds). If you enable this policy setting you can set the maximum job download time to a specified number of seconds. If you disable or do not configure this policy setting the default value of 90 days (7776000 seconds) will be used.
Timeout for inactive BITS jobs
This policy setting specifies the number of days a pending BITS job can remain inactive before the job is considered abandoned. By default BITS will wait 90 days before considering an inactive job abandoned. After a job is determined to be abandoned the job is deleted from BITS and any downloaded files for the job are deleted from the disk. Note: Any property changes to the job or any successful download action will reset this timeout. Consider increasing the timeout value if computers tend to stay offline for a long period of time and still have pending jobs. Consider decreasing this value if you are concerned about orphaned jobs occupying disk space. If you enable this policy setting you can configure the inactive job timeout to specified number of days. If you disable or do not configure this policy setting the default value of 90 (days) will be used for the inactive job timeout.
Specify timeout for fast user switching events
This policy setting specifies the number of seconds a pending fast user switch event will remain active before the switch is initiated. By default a fast user switch event is active for 10 seconds before becoming inactive. If you enable this policy setting you can configure the fast user switch event timeout to specify the number of seconds the event remains active. This value cannot exceed 60 seconds. If you disable or do not configure this policy setting a default value of 10 seconds is used for fast-user switch event timeouts.
Disallow Autoplay for non-volume devices
This policy setting disallows AutoPlay for MTP devices like cameras or phones. If you enable this policy setting AutoPlay is not allowed for MTP devices like cameras or phones. If you disable or do not configure this policy setting AutoPlay is enabled for non-volume devices.