<displayName>enter display name here</displayName>
<description>enter description here</description>
<resources>
<stringTable>
<!-- Supported Platforms -->
<string id="SUPPORTED_WindowsXPSP2WindowsNETSP1orBITS20">Windows XP SP2 or Windows Server 2003 SP1, or computers with BITS 2.0 installed.</string>
<string id="SUPPORTED_WindowsXPWindowsNETorBITS15">Windows XP or Windows Server 2003, or computers with BITS 1.5 installed.</string>
<!-- Supported Platforms -->
<!-- Component name -->
<string id="BITS">Background Intelligent Transfer Service (BITS)</string>
<!-- Component name -->
<!-- inactive job timeout -->
<string id="BITS_Job_Timeout">Timeout for inactive BITS jobs</string>
<string id="BITS_Job_Timeout_Help">This 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. Once 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 setting, you can configure the inactive job time-out to specified number of days.
If you disable or do not configure this setting, the default value of 90 (days) will be used for the inactive job timeout.</string>
<string id="BITS_MaxDownloadTimeText">This setting limits the amount of time that 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, not real-time. 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 15 days (54000 seconds).
If you enable this setting, you can set the maximum job download time to the specified number of seconds.
If you disable or do not configure this setting, the default value of 15 days (54000 seconds) will be used for the maximum job download time.</string>
<!-- max job download time -->
<!-- max bandwidth -->
<string id="BITS_MaxBandwidth">Maximum network bandwidth for BITS background transfers</string>
<string id="BITS_MaxBandwidth_Help">This setting limits the network bandwidth that BITS uses for background transfers (this setting does not affect foreground transfers).
You can specify a limit to use during a specific time interval and a limit to use at all other times. For example, limit the use of network bandwidth to 10 Kbps from 8AM to 5PM, and use all available unused bandwidth the rest of the time.
If you enable this 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 two kilobits BITS will continue to use approximately two kilobits. To prevent BITS transfers from occurring, specify a limit of 0.
If you disable or do not configure this setting, BITS uses all available unused bandwidth.
Note: You should base the limit on the speed of the network link, not the computers network interface card (NIC).
Consider using this setting to prevent BITS transfers from competing for network bandwidth when the client has a fast network card (10Mbs), but is connected to the network via a slow link (56Kbs).</string>
<string id="BITS_EnablePeercachingText">This setting determines if the BITS Peer-caching feature is enabled on a specific computer. By default, the files in a BITS job are downloaded only from the originating server specified by the jobΓÇÖs owner. Each client computer will download its own copy of the files from the origin server.
If BITS Peer-caching is enabled, BITS will cache download jobs and make the content available to other BITS peers. When running a download job, BITS will first request the files for the job from one of its peers in the same IP subnet. If none of the peers in the subnet have the requested files, BITS will download the files for the job from the original server.
If you enable this setting, BITS will cache jobs, respond to content requests from peers, and download job content from peers if possible.
If you disable this setting or do not configure it, the peer-caching feature will be disabled and BITS will download files directly from the original server.</string>
<!-- enable peercaching -->
<!-- peercache size limit -->
<string id="BITS_MaxCacheSize">Limit the BITS Peercache size</string>
<string id="BITS_MaxCacheSizeText">This setting specifies the maximum amount of disk space that can be used for the BITS Peercache, as a percentage of the total system disk size. BITS will add files to the Peercache and make those files available to peers until the cache content reaches the specified cache size. By default, BITS will use 1% of the total system disk for the peercache.
If you enable this setting, you can enter the percentage of disk space to be used for the BITS peercache. You can enter a value between 1% and 80%.
If you disable this setting or do not configure it, the default size of the BITS peercache is 1% of the total system disk size.
Note: This setting has no effect if the "Allow BITS Peercaching"setting is disabled or not configured.</string>
<!-- peercache size limit -->
<!-- max peercaching content age limit-->
<string id="BITS_MaxContentAge">Limit age of items in the BITS Peercache</string>
<string id="BITS_MaxContentAgeText">This setting specifies the maximum age of files in the Peercache. In order to make the most efficient use of disk space, by default BITS removes any files in the cache older than 14 days.
If you enable this setting, you can specify the maximum age of files in the cache in days. You can enter a value between 1 and 120 Days.
If you disable this setting or do not configure it, files older than 14 days will be removed from the Peercache.
Note: This setting has no effect if the "Allow BITS Peercaching"setting is disabled or not configured.</string>
<!-- max peercaching content age limit-->
<!-- disable peercache client-->
<string id="BITS_DisablePeercachingClient">Do not allow the computer to act as a BITS Peercaching client</string>
<string id="BITS_DisablePeercachingClientText">This setting specifies whether the computer will act as a BITS peercaching client. By default, when BITS peercaching is enabled, the computer acts as both a peercaching server (offering files to its peers) and a peercaching client (downloading files from its peers).
If you enable this setting, the computer will no longer use the BITS Peercaching feature to download files; files will be downloaded only from the origin server. However, the computer will still make files available to its peers.
If you disable or do not configure this setting, the computer attempts to download peer enabled BITS jobs from peer computers before reverting to the origin server.
Note: This setting has no effect if the "Allow BITS Peercaching"setting is disabled or not configured.</string>
<!-- disable peercache client-->
<!-- disable peercache server-->
<string id="BITS_DisablePeercachingServer">Do not allow the computer to act as a BITS Peercaching server</string>
<string id="BITS_DisablePeercachingServerText">This setting specifies whether the computer will act as a BITS peercaching server. By default, when BITS peercaching is enabled, the computer acts as both a peercaching server (offering files to its peers) and a peercaching client (downloading files from its peers).
If you enable this setting, the computer will no longer cache downloaded files and offer them to its peers. However, the computer will still download files from peers.
If you disable or do not configure this setting, the computer will offer downloaded and cached files to its peers.
Note: This setting has no effect if the "Allow BITS Peercaching"setting is disabled or not configured.</string>
<!-- disable peercache server-->
<!-- limit peercache bandwidth-->
<string id="BITS_MaxBandwidthServedForPeers">Maximum network bandwidth used for Peercaching</string>
<string id="BITS_MaxBandwidthServedForPeersText">This setting limits the network bandwidth that BITS uses for peercache transfers (this setting does not affect transfers from the origin server).
To prevent any negative impact to a computer caused by serving other peers, by default BITS will use up to 30% of the bandwidth of the slowest active network interface. For example, if a computer has both a 100Mbps network card, and a 56 Kbps modem, and both are active, BITS will use a maximum of 30% of 56Kbps.
You can change the default behavior of BITS, and specify a fixed maximum bandwidth that BITS will use for Peercaching.
If you enable this setting, you can enter a value in bits per second (bps) between 1048576 and 4294967200 to use as the maximum network bandwidth used for peer-caching.
If you disable this setting or do not configure it, the default value of 30% of the slowest active network interface will be used.
Note: This setting has no effect if the ΓÇ£Allow BITS peercachingΓÇ¥ setting is disabled or not configured.</string>
<!-- limit peercache bandwidth-->
<!-- max jobs per computer -->
<string id="BITS_MaxJobsPerMachine">Maximum number of BITS jobs for this computer</string>
<string id="BITS_MaxJobsPerMachineText">This setting specifies the maximum number of BITS jobs that can be created for all users of the computer. By default, BITS limits the total number of jobs that can be created on the computer to 300 jobs. You can use this setting to raise or lower the maximum number of user BITS jobs.
If you enable this setting, BITS will limit the maximum number of BITS jobs to the specified number.
If you disable or do not configure this setting, BITS will use the default BITS job limit of 300 jobs.
Note: BITS Jobs created by services and the local administrator account do not count towards this limit.</string>
<!-- max jobs per computer -->
<!-- max jobs per user -->
<string id="BITS_MaxJobsPerUser">Maximum number of BITS jobs for each user</string>
<string id="BITS_MaxJobsPerUserText">This setting specifies the maximum number of BITS jobs that can be created by a user. By default, BITS limits the total number of jobs that can be created by a user to 60 jobs. You can use this setting to raise or lower the maximum number of BITS jobs a user can create.
If you enable this setting, BITS will limit the maximum number of BITS jobs a user can create to the specified number.
If you disable or do not configure this setting, BITS will use the default user BITS job limit of 300 jobs.
Note: This limit must be lower than the setting specified in ΓÇ£Maximum number of BITS jobs for this computerΓÇ¥, or 300 if the ΓÇ£Maximum number of BITS jobs for this computerΓÇ¥ setting is not configured. BITS Jobs created by services and the local administrator account do not count towards this limit.</string>
<!-- max jobs per computer -->
<!-- max files per job -->
<string id="BITS_MaxFilesPerJob">Maximum number of files allowed in a BITS job</string>
<string id="BITS_MaxFilesPerJobText">This setting specifies the maximum number of files that a BITS job can contain. By default, a BITS job is limited to 200 files. You can use this setting to raise or lower the maximum number of files a BITS jobs can contain.
If you enable this setting, BITS will limit the maximum number of files a job can contain to the specified number.
If you disable or do not configure this setting, BITS will use the default value of 200 for the maximum number of files a job can contain.
Note: BITS Jobs created by services and the local administrator account do not count towards this limit.</string>
<!-- max files per job -->
<!-- max ranges per file -->
<string id="BITS_MaxRangesPerFile">Maximum number of ranges that can be added to the file in a BITS job</string>
<string id="BITS_MaxRangesPerFileText">This setting specifies the maximum number of ranges that can be added to a file in a BITS job. By default, files in a BITS job are limited to 500 ranges per file. You can use this setting to raise or lower the maximum number ranges per file.
If you enable this setting, BITS will limit the maximum number of ranges that can be added to a file to the specified number.
If you disable or do not configure this setting, BITS will limit ranges to 500 ranges per file.
Note: BITS Jobs created by services and the local administrator account do not count towards this limit.</string>
<!-- max ranges per file -->
</stringTable>
<presentationTable>
<presentation id="BITS_Job_Timeout">
<decimalTextBox refId="BITS_Job_Timeout_Time" defaultValue="90">Inactive Job Timeout in Days:</decimalTextBox>
</presentation>
<presentation id="BITS_MaxDownloadTime">
<decimalTextBox refId="BITS_MaxDownloadSeconds" defaultValue="54000">Active Job Timeout in seconds:</decimalTextBox>
</presentation>
<presentation id="BITS_MaxBandwidth">
<decimalTextBox refId="BITS_MaxTransferRateText" defaultValue="10" spinStep="10">Limit background transfer rate (Kbps) to:</decimalTextBox>
<decimalTextBox refId="BITS_MaxBandwidthServedForPeersList" defaultValue="1048576">Maximum network bandwidth used for Peercaching (bps):</decimalTextBox>
</presentation>
<presentation id="BITS_MaxJobsPerMachine">
<decimalTextBox refId="BITS_MaxJobsPerMachineList" defaultValue="300">Maximum number of BITS jobs for this computer:</decimalTextBox>
</presentation>
<presentation id="BITS_MaxJobsPerUser">
<decimalTextBox refId="BITS_MaxJobsPerUserList" defaultValue="60">Maximum number of BITS jobs for each user:</decimalTextBox>
</presentation>
<presentation id="BITS_MaxFilesPerJob">
<decimalTextBox refId="BITS_MaxFilesPerJobList" defaultValue="200">Maximum number of files allowed in a BITS job:</decimalTextBox>
</presentation>
<presentation id="BITS_MaxRangesPerFile">
<decimalTextBox refId="BITS_MaxRangesPerFileList" defaultValue="500">Maximum number of ranges that can be added to the file in a BITS job:</decimalTextBox>
