Windows Server 2008 R2 includes new additions to the IIS7 Web server, adding fit, finish, and a few extras to the best IIS platform ever.
For the last year and a half, the IIS product team has been working hard on building IIS extensions on top of the IIS7 platform, releasing betas, RCs and RTWs that add new support for optimizing media hosting, web content publishing, site and server administration, deployment and migration, and request handling. We would not be able to innovate and build production-ready, fully supported MS software in 12-18 months like this without the architectural changes we introduced in IIS7 in Windows Server 2008. Now with Windows Server 2008 R2, we have added some improvements, fit and finish to that IIS7 platform.
Highlights of the main IIS7 improvements in the Windows Server 2008 R2 Beta today:
Integration of Content Publishing Extensions (FTP, WebDav) into the Windows Server OS
We started development on a complete rewrite of the FTP server and our WebDav implementation well before the Windows Server 2008 release. Early last year, we released the new FTP Publishing Service as a Web download for Windows Server 2008 with features like secure publishing of content using FTPS, IPv6 support, integrated management of FTP/HTTP sites using IIS Manager, and more powerful logging and authentication support. Like all of our extensions, the FTP Publishing Service for Windows Server 2008 is fully supported by Microsoft product support with rich forum support provided by expert users and our own product team. What we have done in Windows Server 2008 R2 is to integrate the FTP Publishing Service into the server OS.
From a customer perspective, that means:
With the FTP Publishing Service installed on Windows Server 2008, you had to uninstall the old FTP server before installing the new one, which is a complete replacement of the old and outdated FTP. With Windows Server 2008 R2, you can install the new FTP server as part of the IIS component install. The IIS setup will replace your old FTP server and even upgrade the new IIS7 FTP publishing service if you have installed it on Windows Server 2008.
You can take advantage of bug fixes that we have made since the release of the FTP Publishing Service in February 2008.
You can use newly added extensibility for authentication, logging, authorization and the home directory that will be documented on MSDN.
We will also ship an updated FTP Publishing Service for Windows Server 2008 for Web download on www.iis.net in May 2009 so that those customers can also take advantage of the bug fixes and extensibility. In other words:
(Web May 2009 release of FTP Publishing + Windows Server 2008) == (FTP Publishing feature in Windows Server 2008 R2)
With the following exception:
FTP Publishing Server for Windows Server 2008 is always installed with a Web download, whereas FTP is now integrated into setup for Windows Server 2008 R2 and later.
Same thing with WebDav, which released in July 2008. WebDav for Windows Server 2008 provided a brand new implementation (to spec) of the WebDAV extension to the HTTP protocol. We have included WebDav in the setup/installation for Windows Server 2008 R2, which means that you can install WebDav as part of Windows Server 2008 R2 setup. The big new feature for WebDav is support for locks. We will also ship a new version of WebDav for Windows Server 2008 that has locking -- look for this release in May 2009 as well. Same model applies:
(Web May 2009 release of WebDav + Windows Server 2008) == (WebDav Publishing feature in Windows Server 2008 R2)
With the following exception:
WebDav for Windows Server 2008 is always installed with a Web download, whereas WebDav is now integrated into setup for Windows Server 2008 R2 and later.
Integration of Administration Pack Extension into the Windows Server OS
We integrated the functionality of the IIS7 Administration Pack into the Windows Server 2008 R2 installation, which provides customers with:
Integrated administration support in IIS Manager for the ASP.NET authorization, custom errors, FastCGI, and Request Filtering features.
Configuration Manager, which gives you a visual editor for managing the IIS7 configuration system. If you want to check it out, Carlos Aguilar Mares, our IIS Dev Manager, wrote a comprehensive blog on the Config Editor's capabilities
. My favorite part of Configuration Editor is the script generation functionality -- comes in very handy with demos! :-)
We didn't incorporate the IIS Reports feature into the Windows Server OS, so if you need that particular functionality, you can use it as part of the Web download IIS Administration Pack. As with our usual policy, we will be releasing an update of the IIS Administration Pack for Windows Server 2008 users with the bug fixes and other changes that you see in Windows Server 2008 R2 (except for the setup integration).
The Administration Pack for Windows Server 2008 will release by Windows Server 2008 R2 general availability to keep on par with the Administration Pack functionality in the Windows Server 2008 R2 release.
New IIS7 PowerShell Provider and Commandlet Support in Windows Server 2008 R2
The IIS PowerShell provider, also downloadable for Windows Server 2008, lets users manage IIS, ASP.NET and custom configuration using the PowerShell programming environment. Yes, it's true -- we have IIS:/> for the PowerShell users out there. With our PowerShell support, we have implemented three levels of support:
PowerShell provider: Use the provider if you are familiar with the IIS configuration system and want to adminster config directly in the PS programming environment.
Low-level commandlets: Use our collection of low-level commandlets to manage every IIS setting if you want this level of fine-grained control.
Task-oriented commandlets: Use our many task-oriented commandlets to manage websites (ex: New-WebSite to create a site), backup and restore web server configuration, and other common tasks.
With the integration into Windows Server 2008 R2, you can install the PowerShell provider and 60+ commandlets using Windows Server setup.
As with FTP and WebDav:
(summer 2009 Web release of PowerShell + Windows Server 2008) == (PowerShell feature in Windows Server 2008 R2)
With the following exception:
PowerShell for Windows Server 2008 is always installed with a Web download, whereas PowerShell is now integrated into setup for Windows Server 2008 R2 and later.
Check out Thomas Deml, Group Program Manager and PowerShell guru's blog, for more information about our PowerShell support (http://blogs.iis.net/thomad).
Rich Application Hosting on Server Core
With Windows Server 2008 R2, you can host ASP.NET applications on IIS installations running Server Core. ASP.NET/CLR did some work to refactor and make sure that the managed code environment for ASP.NET pages could work on Server and voila! We have support for not just images, media, PHP, and classic ASP pages on Server Core but also ASP.NET applications.
The PowerShell 2.0 release in Windows Server 2008 R2 handles remote management now, which comes in handy with Server Core installations and our new IIS7 PowerShell provider. So not only can you host all your apps on IIS with Server Core, it is also much easier to administer them locally and remotely using our new IIS PowerShell provider and commandlets. For overall PowerShell mojo, check out the Windows PowerShell blog.
Improvements to FastCGI Support
IIS7 supports PHP hosting through our FastCGI implementation, which we substantially overhauled and improved in IIS7. Enhancements for PHP support on Windows Server 2008 R2 include:
Support in IIS Manager for administering FastCGI settings.
Automatic recycling of php-cgi.exe whenever php.ini changes. In this release, IIS monitors changes to a file for each process pool and recycle FastCGI process for the process pool when a change to the file is made. By default, this feature is turned off. If you turn it on (by setting a property in the user interface), you can specify a file path to monitor changes.
FREB support for FastCGI, so you can troubleshoot PHP and other FastCGI-compliant apps more effectively.
MaxInstance is now dynamic -- if maxInstance is set to 0, IIS automatically detects the system load and adjusts the maxInstances count. This allows us to optimize performance for our PHP support.
New support for controlling FastCGI error behavior based on specific errors.
IIS Core Changes
We have also made a number of changes to our core IIS7 platform, based on customer request and our own development experience for extensions using the IIS7 platform:
Support for custom tracing in the configuration system. This new feature will come in handy for troubleshooting config.
The ability to audit or trace configuration changes through configuration polling -- this was a request from our hosters in particular who want to monitor changes to the configuration system by their customers.
Support for ASP.NET to support different CLR versions (for example, CLR 4.0). With multiple versions of the CLR in use, this feature is important for developers to be able to switch versions. We have also backported this functionality to Windows Server 2008 SP2.
Better control over application pools with the ability to set the CLR setting per application pool and to monitor performance with new Application Pool performance counters.
Delegateable custom errors, which was a top request from developers to be able to change custom errors locally or remotely as a non-server admin.
IPv6 support for IP restriction list.
More fine-grained control over request filtering, specifically for query strings to help prevent SQL injection attacks on applications hosted on the server. Request filtering also now supports request-specific rules so that SQL Injection rules apply to specified requests only.
Nego2 support, which will allow for built-in support of LiveID providers, FedSSP, and more granular Kerberos/NTLM enablement.
Support for Managed Service Accounts for domain accounts that don't require a password.
AppPool identity support -- this one calls for a whole separate blog posting, so stay tuned for that.
Support for application pool warm-up for large applications that want to "prime" an application pool for better performance on the intial request.
IIS Best Practice Analyzer
Windows Server 2008 R2 introduces a new feature in Server Manager called the Best Practice Analyzer. The BPA provides a single console experience within Server Manager to manage best practice rules for configuration across different server roles, like Exchange, AD, and IIS. In Server Manager, you can run the BPA against some IIS rules that focus on best practices for security and performance -- for example, checking to make sure that basic authentication is not enabled without SSL. This list of BPA rules for IIS is not exhaustive by any means but it does give a good core set of guidance to get started. We will also be updating and increasing the rule set automatically through Server Manager. Note that this functionality lives in Server Manager only, and is not hosted in IIS Manager.
And of course, we have fixed bugs along the way.
Your feedback helped us refine IIS7, which is the best Web server platform yet. You can download the Windows Server 2008 R2 beta today here. A nice way to bring in 2009!
Thanks for reading,