Datasheet

Listing 1-1: The unattend.xml File
<?xml version=”1.0” ?>
<unattend xmlns=”urn:schemas-microsoft-com:unattend”
xmlns:wcm=”http://schemas.microsoft.com/WMIConfig/2002/State”>
<servicing>
<!--Install a selectable update in a package that is in the
Windows Foundation namespace-->
<package action=”configure”>
<assemblyIdentity name=”Microsoft-Windows-Foundation-Package”
version=”6.0.5308.6” language=”neutral” processorArchitecture=”x86”
publicKeyToken=”31bf3856ad364e35” versionScope=”nonSxS” />
<selection name=”IIS-WebServerRole” state=”true”/>
<selection name=”WAS-WindowsActivationService” state=”true”/>
<selection name=”WAS-ProcessModel” state=”true”/>
<selection name=”IIS-WebServer” state=”true”/>
<selection name=”IIS-CommonHttpFeatures” state=”true”/>
</package>
</servicing>
</unattend>
Notice that the <servicing> element contains one or more <selection> child elements, and each
child element specifies a particular update. The
<selection> child element features two attributes
named
name and state. The name attribute contains the update name to be installed or uninstalled. Set
the
state attribute to true to install or false to uninstall the specified update.
Upgrade
If you’re upgrading from Windows XP to Windows Vista, or from Windows Server 2003 to Windows
Server 2008, and if your old operating system has IIS installed, the Windows Vista or Windows Server
2008 setup automatically scans through the capabilities of the installed IIS and ensures that the new
install of IIS 7 supports those features and capabilities. Unfortunately, due to the monolithic architecture
of IIS 5.1 and IIS 6.0, this installation ends up installing almost all of the feature modules of IIS 7. I highly
recommend that after the upgrade you use one of the previously discussed installation options to unin-
stall the updates that you do not need to decrease the attack surface and footprint of your Web server.
Summary
This chapter first covered the IIS 7 package updates and their constituent feature modules, and showed
you how to custom-build your own Web server from the desired package updates to decrease the foot-
print of your Web server. The chapter then provided in-depth coverage of five different IIS7 setup
options. The chapter also gave an overview of the main systems that make up the IIS7 and ASP.NET
integrated infrastructure. As discussed, one of these systems is the IIS7 and ASP.NET integrated configu-
ration system, which will be discussed thoroughly in the next chapter.
21
Chapter 1: IIS 7 and ASP.NET Integrated Architecture
52539c01.qxd:WroxPro 9/17/07 6:51 PM Page 21