Datasheet
tion are on a server that was upgraded to Longhorn or have been migrated to a new installation of
Longhorn, you may need to create new accounts and assign the correct permissions.
The second caveat that will catch you on transfers to a new IIS installation is the modularity of IIS 7.0.
On a default install of IIS 7.0, components such as classic ASP, ASP.NET, and ISAPI filters and extensions
are not installed; thus these functions will not work if you simply copy the site contents and code over to
a new default IIS 7.0 installation. You must install components in IIS 7.0 that were used in your site
under IIS 6.0 for the transfer to work seamlessly. Upgrades of existing IIS 6.0 setups will retain all their
previous functionality but will not receive any new functionality unless specifically configured.
Additional Features
As in previous versions, IIS 7.0 includes FTP and SMTP services. SMTP remains unchanged from
Windows Server 2003 and IIS 6.0, as does the version of FTP that ships with Windows Server 2008. A
new FTP server is available as a free download from Microsoft’s web site at
www.iis.net, and this ver-
sion incorporates many of the requested changes from customers as well as tight integration with web
sites to simplify publishing through FT. Windows Server 2008 drops the POP3 service that was intro-
duced in Windows Server 2003. Both FTP and SMTP are covered in detail in Chapter 10.
FTP
Windows Vista shipped with exactly the same FTP code and functions found in Windows Server 2003
and IIS 6.0, and Windows Server 2008 ships with the same code as well. A new FTP server, shipped as a
free download from
www.iis.net, includes secure FTP using SSL certificates. This has been one of the
primary reasons for using third-party FTP servers. In addition, the new version of FTP for Windows
Server 2008 is integrated with the IIS 7.0 management functions, including extensibility of the authenti-
cation process. This means that FTP can use ASP.NET authentication, including membership and roles
features, and will not require Windows CALs. Both versions of FTP are covered in detail in Chapter 10.
SMTP
SMTP is still available on Windows Server 2008, as it was on Windows Server 2003, without the need to
purchase Microsoft Exchange Server. Unchanged from the Windows Server 2003 implementation, SMTP
code is actually developed and owned by the Windows Exchange Server development team. The SMTP
service in Windows Server 2008 is not meant to be a full-featured implementation, but rather a simpli-
fied service that provides minimum functionality without the need for additional services. Most profes-
sional users of IIS will want to install another mail server product, such as Microsoft’s Exchange Server.
That doesn’t mean that SMTP in Windows Server 2008 is a lightweight product. It is still functional
for sending mail from applications on IIS 7.0, and it is a fully compliant implementation of SMTP that
functions well in an Internet environment. While not having the configurability of Microsoft’s
Exchange Server, it will still function with multiple virtual servers and serve multiple SMTP domains
while providing for security through relay permissions and IP restrictions as well as Windows login
account access.
Windows Server 2008 no longer provides a POP3 server, and no IMAP functionality is available without
additional products installed. Chapter 10 goes into more detail on SMTP installation and configuration.
25
Chapter 1: Background on IIS and New Features in IIS 7.0
97823c01.qxd:WroxPro 2/4/08 6:47 PM Page 25