List of registry keys that are migrated when you upgrade from IIS 5.1 or IIS 6.0 to IIS 7.0

When you upgrade from Microsoft Internet Information Services (IIS) 5.1 on Microsoft Windows XP or IIS 6.0 on Windows Server 2003 to IIS 7.0 on Windows Vista or on Windows Server 2008, some IIS registry keys and values are not migrated. This article lists the registry keys that are migrated and the registry keys that are not migrated.

Registry keys that are migrated

When you upgrade from IIS 5.1 or IIS 6.0 to IIS 7.0, the following registry keys are migrated:

• Registry keys and values that are located under the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W3SVC\Parameters key in IIS 5.1 and in IIS 6.0 are migrated to the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\WAS\Parameters registry key in IIS 7.0. This registry key includes the following values:
  • AllowWMSSpew
  • AlwaysLogEvents
  • BreakOnFailureCausingShutdown
  • StartupWaitHintInMilliseconds
  • UseSharedWPDesktop
• Registry keys and values that are located under the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\INETINFO\Parameters key in IIS 5.1 and in IIS 6.0 are migrated to the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\WAS\Parameters\apphost registry key in IIS 7.0. This registry key includes the following values:
  • MaxConcurrency
  • MaxPoolThreads
  • PoolThreadLimit
  • ThreadPoolExactThreadCount
  • ThreadPoolMaxContextSwitch
  • ThreadPoolMaxCPU
  • ThreadPoolRefTraceCounter
  • ThreadPoolStartDelay
  • ThreadPoolStartupThreadCount
  • ThreadTimeout
• All registry keys and values that are located under the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W3SVC\ASP\LanguageEngines registry key are migrated without any changes.

Registry keys that are not migrated

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

The following registry keys are not migrated from IIS 5.1 and IIS 6.0 to IIS 7.0:

• Registry keys and values that are located under the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InetInfo\Parameters key in IIS 5.1 and in IIS 6.0 are not migrated to IIS 7.0. This registry key includes the following values:
  • CacheSecurityDescriptor
  • CheckCertRevocation
  • DataSetCacheSize
  • DigestContextCacheTTL
  • DigestPartialContextCacheTTL
  • DisableLazyContentPropagation
  • DisableMemoryCache
  • DoDirMonitoringForUNC
  • ErrorLoggingDir
  • FileAttributeCheckThreshold
  • IncrementalSiteIDCreation
  • ListenBackLog
  • LogBufferSize
  • MaxCachedFileSize
  • MemCacheSize
  • MinFileBytesPerSec
  • ObjectCacheTTL
  • UserTokenTTL
• Registry keys and values that are located under the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters key in IIS 5.1 and in IIS 6.0 are not migrated to IIS 7.0. This registry key contains settings for the IIS 6.0 WWW service and includes the following values:
  • Default value
    
    Note This value determines whether IIS recognizes the HTTP TRACE method.
  • LogErrorRequests
  • LogSuccessfulRequests
  • MaxConcurrentCgisExecuting
  • SSIEnableCmdDirective
  • TryExceptDisable
  • UploadReadAhead
  • UsePoolThreadForCGI
• Registry keys and values that are located under the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP\Parameters key in IIS 5.1 and in IIS 6.0 are not migrated to IIS 7.0. This registry key contains settings for active server pages and includes the following values:
  • DisableLazyContentPropagation
  • ThreadMax
  • DisableComPlusCpuMetric
  • AspMaxResponseHeaderLength
  • AspMaxPropertyStringLength
  • DisableCachedResponseOnUNCAccessFailure
  • F5AttackDetectionEnabled
  • HangDetRequestThreshold
  • HangDetThreadHungThreshold
  • HangDetConsecIllStatesThreshold
  • HangDetEnabled
  • EnableChangeNotificationForUNC
  • FileMonitoringTimeoutSeconds
  • MaxCSR
  • MaxCPU
  • DisableOOMRecycle
• Registry keys and values that are located under the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSFTPSVC\Parameters key in IIS 5.1 and in IIS 6.0 are not migrated to IIS 7.0. This registry key contains settings for the FTP service and includes the following values:
  • Default value
    
    Note This value determines whether the FTP service supports annotating a directory with custom messages.
  • AnonymousHomeDirInfoGrace
  • AnonymousHomeDirInfoInterval
  • CacheAnonymousHomeDirInfo
  • EnablePortAttack
  • LowercaseFiles
  • MaxPassiveAcceptEvents
• By default, the following registry key is not installed:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\ASP\LanguageEngines
  To add a language, you must create this registry key, add a subkey for the language that you want, and then add some values. To do this, follow these steps:
  1. Click Start
     Collapse this imageExpand this image

     
     , type regedit in the Start Search box, and then click regedit in the Programs list.
     
     
     Collapse this imageExpand this image

     
     If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
  2. Locate and then click the following registry subkey:
     HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\ASP
  3. On the Edit menu, point to New, and then click Key.
  4. In the New Key #1 box, type LanguageEngines, and then press ENTER.
  5. On the Edit menu, point to New, and then click Key.
  6. In the New Key #1 box, type LanguageName, and then press ENTER.
     
     Note LanguageName represents the name of the language that you want to add.
  7. On the Edit menu, point to New, and then click String Value.
  8. In the New Value #1 box, type Write, and then press ENTER.
  9. Right-click Write, and then click Modify.
  10. In the Value data box, type Response.WriteEquiv | , and then click OK.
  11. On the Edit menu, point to New, and then click String Value.
  12. In the New Value #1 box, type WriteBlock, and then press ENTER.
  13. Right-click WriteBlock, and then click Modify.
  14. In the Value data box, type Response.WriteBlockEquiv | , and then click OK.
  15. Close Registry Editor.