Table B.1: IIS Metabase Properties That Have Changed Since IIS 5.0
IIS Metabase Properties
| Recommendation
|
---|
AspThread GateEnabled
AspThread GateLoadHigh
AspThread GateLoadLow
AspThread GateSleepMax
AspThread GateTimeSlice
| In IIS 5.0, these metabase properties are provided for the configuration of performance features.In IIS 6.0, these performance features are provided by other means. As a result, IIS 6.0 no longer uses these metabase properties.Remove any references to these metabase properties from Web sites, applications, or setup programs.For more information about improving performance in IIS 6.0, see "Designing Scalability into Server Environments" in IIS 6.0 Help, which is accessible from IIS Manager. |
CPUAppEnabled
CPUCGIEnabled
CPUCGILimit
CPUEnableActiveProcs
CPUEnableAllProcLogging
CPUEnableAppLogging
CPUEnableCGILogging
CPUEnableEvent
CPUEnableKernelTime
CPUEnablePageFaults
CPUEnableProcType
CPUEnableTerminatedProcs
CPUEnableTotalProcs
CPUEnableUserTime
CPULimitLogEvent
CPULimitPause
CPULimitPriority
CPULimitProcStop
CPULimitsEnabled
CPULoggingInterval
CPULoggingMask
CPULoggingOptions
| In IIS 5.0, these metabase properties are provided for the configuration of processor (CPU) management features.In IIS 6.0, processor management (CPU throttling) is provided by other means. As a result, IIS 6.0 no longer uses these metabase properties.Remove any references to these IIS metabase properties from Web sites, applications, or setup programs.The following metabase properties reference and implement CPU throttling in IIS 6.0:
CPULimit
CPUResetInterval
CPUAction
For more information about CPU throttling in IIS 6.0, see the CPULimit, CPUResetlnterval, and CPUAction properties in the "Metabase Property Reference" in IIS 6.0 Help, which is accessible from IIS Manager. |
CPUResetlnterval
| In IIS 5.0, this property enables the monitoring of processor utilization at the Web site level. IIS 5.0 was unable to monitor individual processes for a Web site, such as multiple processes in an ASP.NET Web garden.In IIS 6.0, this property enables the monitoring of processor utilization at the worker process level. You cannot monitor the processor utilization for individual Web sites unless there is only one Web site in the application pool.For more information about how to configure this value for worker processes in an application pool, see the CPUResetlnterval property in the "Metabase Property Reference" in IIS 6.0 Help, which is accessible from IIS Manager. |
DisableSocketPooling
| In IIS 4.0 and IIS 5.0, Windows Sockets (WinSock) listens for HTTP requests that use Transmission Control Protocol (TCP). WinSock uses the concept of sockets to provide TCP connectivity. As a result, IIS 4.0 and IIS 5.0 are bound to the scalability constraints of using sockets through WinSock. In IIS 5.0, socket pooling addresses these scalability problems, in cases where a large number of Web sites were configured with individual IP addresses.In IIS 5.0, socket pooling allows for socket resources to be shared between multiple Web sites and thus provides significant improvements — up to two to three times the scaling capacity of earlier versions of IIS.In IIS 6.0, HTTP.sys is responsible for listening for HTTP requests and provides similar functionality to the DisableSocketPooling metabase property.To configure HTTP.sys, use Httpcfg.exe.
| Note | On new installations of Windows Server 2003 and IIS 6.0, the DisableSocketPooling metabase property still exists; however, IIS 6.0 ignores the property. |
|
HcDoDynamicCompression
| In IIS 6.0, the DoDynamicCompresssion metabase property replaces this property.For more information, see the DoDynamicCompression metabase property in the "Metabase Property Reference" in IIS 6.0 Help, which is accessible from IIS Manager. |
HcDoStaticCompression
| In IIS 6.0, the DoStaticCompression metabase property replaces this property.For more information, see the DoStaticCompression property in the "Metabase Property Reference" in IIS 6.0 Help, which is accessible from IIS Manager. |
HcMimeType
| In IIS 5.0, this metabase property indicates which Multipurpose Internet Mail Extensions (MIME) types are supported by the compression scheme.IIS 6.0, HTTP compression is performed in a different way, and this metabase property is no longer used.Remove any references to this metabase property from Web sites, applications, or setup programs. |
PutReadSize
| In IIS 5.0, this metabase property is provided to support the Web Distributed Authoring and Versioning (WebDAV) component, but is untested and unsupported.In IIS 6.0, this functionality is integrated with the WebDAV component. As a result, IIS 6.0 no longer uses this metabase property.Remove any references to this metabase property from Web sites, applications, or setup programs.For more information about WebDAV in IIS 6.0, see "About WebDAV" in IIS 6.0 Help, which is accessible from IIS Manager. |
UNCAuthenticationPassthrough
| In IIS 5.0, this metabase property enables pass-through user authentication for Universal Naming Convention (UNC) virtual root access, which is for authentication schemes that support delegation.In IIS 6.0, pass-through authentication occurs automatically when the UNCUserName and UNCPassword metabase properties are not specified. As a result, IIS 6.0 no longer uses this metabase property.Remove any references to this metabase property from Web sites, applications, or setup programs.For more information, see the UNCUserName and UNCPassword properties in the "Metabase Property Reference" in IIS 6.0 Help, which is accessible from IIS Manager. |