Category: At least Windows Vista
SSL Cipher Suite Order
This policy setting determines the cipher suites used by the Secure Socket Layer (SSL). If you enable this policy setting SSL cipher suites are prioritized in the order specified. If you disable or do not configure this policy setting the factory default cipher suite order is used. SSL2 SSL3 TLS 1. 0 and TLS 1. 1 cipher suites:TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_RC4_128_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P521 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P521TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P384 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P521 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P256 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P521 TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHATLS_RSA_WITH_RC4_128_MD5 SSL_CK_RC4_128_WITH_MD5 SSL_CK_DES_192_EDE3_CBC_WITH_MD5 TLS_RSA_WITH_NULL_SHATLS_RSA_WITH_NULL_MD5 TLS 1. 2 SHA256 and SHA384 cipher suites:TLS_RSA_WITH_AES_128_CBC_SHA256TLS_RSA_WITH_AES_256_CBC_SHA256TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P521TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P256TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P384TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P521TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P384TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P521TLS_DHE_DSS_WITH_AES_128_CBC_SHA256TLS_DHE_DSS_WITH_AES_256_CBC_SHA256TLS_RSA_WITH_NULL_SHA256TLS 1. 2 ECC GCM cipher suites:TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P256TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P384TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P521TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P384TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P521How to modify this setting:1. Open a blank notepad document. 2. Copy and paste the list of available suites into it. 3. Arrange the suites in the correct order; remove any suites you don’t want to use. 4. Place a comma at the end of every suite name except the last. Make sure there are NO embedded spaces. 5. Remove all the line breaks so that the cipher suite names are on a single long line. 6. Copy the cipher-suite line to the clipboard then paste it into the edit box. The maximum length is 1023 characters.
Tag Windows Customer Experience Improvement data with Study Identifier
This policy setting will enable tagging of Windows Customer Experience Improvement data when a study is being conducted. If you enable this setting then Windows CEIP data uploaded will be tagged. If you do not configure this setting or disable it then CEIP data will not be tagged with the Study Identifier.
Allow Corporate redirection of Customer Experience Improvement uploads
If you enable this setting all Customer Experience Improvement Program uploads are redirected to Microsoft Operations Manager server. If you disable this setting uploads are not redirected to a Microsoft Operations Manager server. If you do not configure this setting uploads are not redirected to a Microsoft Operations Manager server.
Limit the maximum number of ranges that can be added to the file in a BITS job
This policy setting limits the 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 policy 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 policy setting BITS will limit ranges to 500 ranges per file. Note: BITS Jobs created by services and the local administrator account do not count toward this limit.
Limit the maximum number of files allowed in a BITS job
This policy setting limits the 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 policy 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 policy 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 toward this limit.
Limit the maximum number of BITS jobs for each user
This policy setting limits the 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 policy 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 policy setting BITS will use the default user BITS job limit of 300 jobs. Note: This limit must be lower than the setting specified in the “Maximum number of BITS jobs for this computer” policy setting or 300 if the “Maximum number of BITS jobs for this computer” policy setting is not configured. BITS jobs created by services and the local administrator account do not count toward this limit.
Limit the maximum number of BITS jobs for this computer
This policy setting limits the 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 policy setting to raise or lower the maximum number of user BITS jobs. If you enable this policy setting BITS will limit the maximum number of BITS jobs to the specified number. If you disable or do not configure this policy 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 toward this limit.
Limit the maximum network bandwidth used for Peercaching
This policy setting limits the network bandwidth that BITS uses for peer cache 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 percent of the bandwidth of the slowest active network interface. For example if a computer has both a 100 Mbps network card and a 56 Kbps modem and both are active BITS will use a maximum of 30 percent of 56 Kbps. You can change the default behavior of BITS and specify a fixed maximum bandwidth that BITS will use for peer caching. If you enable this policy 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 policy setting or do not configure it the default value of 30 percent of the slowest active network interface will be used. Note: This setting has no effect if the “Allow BITS peer caching” policy setting is disabled or not configured.
Do not allow the computer to act as a BITS Peercaching server
This policy setting specifies whether the computer will act as a BITS peer caching server. By default when BITS peer caching is enabled the computer acts as both a peer caching server (offering files to its peers) and a peer caching client (downloading files from its peers). If you enable this policy 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 policy setting the computer will offer downloaded and cached files to its peers. Note: This setting has no effect if the “Allow BITS peer caching” setting is disabled or not configured.
Do not allow the computer to act as a BITS Peercaching client
This policy setting specifies whether the computer will act as a BITS peer caching client. By default when BITS peer caching is enabled the computer acts as both a peer caching server (offering files to its peers) and a peer caching client (downloading files from its peers). If you enable this policy setting the computer will no longer use the BITS peer caching 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 policy setting the computer attempts to download peer-enabled BITS jobs from peer computers before reverting to the origin server. Note: This policy setting has no effect if the “Allow BITS peer caching” policy setting is disabled or not configured.