Datasheet
IIS 6.0, in case your application is not able to run in the new IIS 7.0 integrated pipeline mode. Secondly,
an optional IIS 6.0 Metabase Compatibility module can be installed for those applications or scripts that
query the IIS metabase. Installing this module installs an ABO mapper that transparently redirects calls
to metabase properties to the corresponding section in the new applicationHost.config file. All existing
scripts and code (whether they read or write to the metabase) should continue to workThis mapper does
not allow any new IIS 7.0 functionality to be configured, and scripts using it are limited to IIS 6.0 fea-
tures. For example, an existing script could create a new web site but could not configure failed request
tracing for that site, because there are no metabase properties related to request tracing. ASP.NET config-
urations are also unavailable through this wrapper.
Figure 1-6
There are two possible compatibility issues you may face in migrating sites from IIS 6.0. The first has to
do with the new security model for Vista/Longhorn. Because the security model is one of least privi-
leges, if you have altered the default settings or accounts for IIS 6.0 on Windows Server 2003, you may
need to correct permission errors that show up in IIS 7.0. Depending on whether the site and/or applica-
24
Part 1: Introduction and Deployment
97823c01.qxd:WroxPro 2/4/08 6:47 PM Page 24