1. Marcel Trümpy Platform Technology Advisor Microsoft Switzerland marcel.truempy@microsoft.com http://blogs.technet.com/chitpro-de

2. Large focus on Web Workload in the enterprise and hosting world Web 2.0, SaaS, SOA New version of Windows Web Server 2008 Redesigned IIS7 Web Server Deep integration with ASP.net Interoperability with non-Microsoft languages IIS on Windows Server Core

3. Windows Web Server 2008 is built for Internet Web serving Increased hardware limits: 4 processors and 4GB of RAM (32 GB on x64 version) Removed features unnecessary for web severing Web (IIS) is only default role (two others possible): Windows SharePoint Services, Windows Media Services (download and install) Benefits Small footprint, Lower Cost Supports More Web Application Scenarios SQL Server allowed for local Web applications Full use rights for IIS, ASP.NET and.NET FX 3.0

5. Proven Scalability MySpace - 23 Billion Page* Views/Month Microsoft.com - 10k Req/sec & 300K Concurrent Connections Match.com -30 million page view daily Proven Security No critical IIS 6 hotfixes since RTM Proven Trust 54% of Fortune 1000 use IIS (port80software.com) A solid foundation to build on.

6. *As of 4/4/07

7. Site density on shared servers is too low Configuration corruption and replication issues Too few options for site owner administration Site/server failures too difficult or too long to troubleshoot Not enough flexibility for customization Current support for PHP apps is inadequate

8. New Modular Architecture and Request Pipeline Redesigned Configuration System New UI and Suite of Management Tools Deep ASP.Net Integration Detailed Tracing and Troubleshooting Tools Delegated Remote Administration Granular Feature Delegation Shared Configuration for Web farms FastCGI Module for PHP Hosting

9. Monolithic implementation Install all or nothing… Extend server functionality only through ISAPI… Send Response LogCompress NTLMBasic CGI Static File Authentication Anon ASP.NET PHP ISAPI … … Determine Handler

10. Server functionality is split into ~ 40 modules... Modules plug into a generic request pipeline… Modules extend server functionality through a public module API. Send Response LogCompress NTLMBasic Determine Handler CGI Static File ISAPI Authentication Anon SendResponse Authentication Authorization ResolveCache ExecuteHandler UpdateCache … … … …

11. Install, manage, and patch only the modules you use… Reduces attack surface (10 modules installed by default) Reduces in-memory footprint Provides fine grained control Replace server modules provided by Microsoft with your own custom components, or add new components from  IIS.NET BEWARE of how to take them off! Server Manager & OCSetup vs. IIS Manager

14. Not on Server Core

15. Classic ASP Web Server CGI and ISAPI Web Server Static file Web Server (images, Office documents, etc.) PHP Web Server IIS Server Core installation Lean, efficient footprint Minimal surface of attack and maintenance Headless (remote) management

16. Ultimate low footprint web server Lower memory requirement Lean OS configuration Minimize attack and maintenance surface Seamless integration with IIS7’s new componentized architecture Powerful IIS command-line management interface “Reusable” WMI and AppCmd scripts and batch files

18. OCList OCSetup PKGMGR AppCmd MWA OCSetup AppCmd MWA WMI

19. Installing IIS 7.0 features OCList for dependencies OCSetup to install components + dependencies Enable remote acess and configuration start /wait ocsetup IIS-WebServerRole;WAS- WindowsActivationService;WAS-ProcessModel;IIS- WebServer netsh advfirewall firewall set rule group="Remote Administration" new enable=yes winrm set winrm/config/client @{TrustedHosts="iiscoredemo"}

21. No more metabase.bin or metabase.xml files! Configure IIS and ASP.NET properties in the same file Built for simple, schema-based extensibility Machine Independent Can be shared across multiple machines

22. ApplicationHost.config Administration.config Server Wide Settings Global Feature Delegation IIS Manager Users ApplicationHost.config Administration.config Server Wide Settings Global Feature Delegation IIS Manager Users Sites Server Server Changes “Global” Individual Site Changes

23. Global settings and location tags.NET Framework ASP.net global settings Global web.config.NET global settings Machine.config IIS 7 Server Applicationhost.config Web.config IIS7 Delegated settings.NET settings

24. PowerShell appcmd.exe XML config files

29. DCOM only, not a firewall-friendly protocol No way to delegate control of sites or applications Windows administrators only XML MetaBase Administrator Developers Site Owners Application Owners

30. XML applicationHost.config Administrator web.config XML Internet Developers Site Owners Application Owners Administrators can manage entire Web server Almost the same as sitting at the box Managing sites and applications Admins and non-admins Windows users and IIS manager users Control of site and application settings Administrator decides what non-admins can view/change (feature delegation) HTTPS based Secure firewall-friendly protocol

31. wwwroot App1 App2

32. Administrator decides which features non- admins can control Site owners control delegated settings No elevated privileges required! Delegated settings are in web.config Site or nested at application level Shares web.config with ASP.NET configuration Xcopy deploy configuration and content Take precautions to protect overwrites

33. DelegatedDelegated Not delegated Hidden and not delegated

36. Microsoft ships the following for Windows Server 2008: A brand-new, feature-rich FTP service An updated, feature-compatible version of FPSE A redesigned WebDAV implementation All are available as free downloads: http://www.iis.net

37. Current Scenario: IIS administrators needed to create two sites in the past. Cause: HTTP and FTP sites stored their settings separately. Solution: FTP 7 integrates with the IIS 7.0 configuration system.

38. Current Scenario: Hosting multiple FTP sites requires unique IP addresses. Cause: FTP protocol architecture lacks the flexibility of HTTP’s host headers. Solution: FTP 7 introduces “virtual host” support.

39. Current Scenario: FTP user isolation in IIS 6 required physical directories. Cause: FTP user isolation infrastructure could not support virtual directories. Solution: FTP 7 user isolation allows both virtual and physical directories.

40. Current Scenario: Server administrators have no way to limit disk usage for FTP sites. Cause: FTP does not support quotas. Solution: FTP 7 integrates with File Server Resource Manager directory quotas in Windows Server 2008.

42. In-depth technical articles and samples Connect with other IIS experts on blogs & forums Free advice and assistance in forums Download centre with IIS solutions

43. These books can be found at all major book stores and online retailers

44. Course IDTitle 6045 Managing Internet Information Services 7.0 and Windows Media Server in Windows Server 2008 For training information and availability: www.microsoft.com/learning

45. © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.