They did it. I wasn't convinced that Microsoft would ever get it done, but they've finally released Windows Server 2003. Sure, they did a ninth-inning renaming of the operating system from Windows .NET Server to Windows Server 2003. But there are still many features that the .NET developer should be salivating over. In this article, I will count down the top ten features that you should know about.
Though not officially part of Windows Server 2003, Active Directory Application
Mode (ADAM) represents a better way for developers to use directory stores.
In ADAM, you can install an Active Directory instance that is not tied to a
domain controller. No longer are you required to intermingle the IT department's
Active Directory instance with your application data. ADAM and Active Directory
share most of their source code so that all of the old ADSI and
APIs work just as you would expect.
Gone are the days of having to use convoluted APIs to add virtual directories and sites to the IIS Metabase. The new IIS 6.0 Metabase is just an XML file. In addition, the new metabase can be set so that manual edits to the XML file are automatically reflected in the running instance of IIS 6.0.
After being able to play around with MSMQ for the past year in Windows XP, finally there's a Server OS that supports it. For the uninitiated, MSMQ 3.0 adds:
Background Intelligent Transfer Service (BITS) is an IIS server extension that allows you to write your own "Windows Update"-style background downloading of new content or product updates. BITS automatically resumes downloads as a connection comes and goes.
Hidden beneath the covers of Windows Server 2003 is the Windows System Resource Manager (WSRM). The WSRM allows you to specify CPU and memory allocation policies for different applications. The purpose of the WSRM is to allow you to host multiple applications on a single server and limit how many server resources to which a single application is entitled.
While it is easy to get "Web Gardens" confused with "Web Farms," the concept is similar. A Web Farm hosts a single web application on multiple machines, and a Web Garden allows multiple processes to service a single web application. Since there are multiple processes to handle requests for the web application, there should be reduced contention for OS resources.
In IIS 6.0, each web application belongs to an Application Pool. These pools are used to improve the health of each application, as well as the server itself. The pools each have four types of settings:
If you have been keeping up with ONDotnet.com's articles, you should already know about the changes in the .NET Framework 1.1. More importantly, Windows Server 2003 comes pre-installed with the new version of the framework. No more explaining that your application needs the .NET runtime to be installed as well. Microsoft is treating the Framework like Win32 API before ... it's all in there.
While IIS 6.0 provides quite a lot of new functionality to keep web sites functional
in the worst of days, Microsoft went the extra step of moving the HTTP serving
to a Kernel Mode Driver. What this means is that no matter how many processes
in IIS 6.0 are brought down, the HTTP serving will continue. The
serves and caches web pages right in the kernel, so not only is there improved
isolation between application processes, the performance is markedly improved.
Security has become the daily mantra of Microsoft these days, and this version of the OS proves it. After initial installation, absolutely nothing is turned on. In obvious contrast to previous incarnations of the OS, Windows Server 2003 has almost no surface area to lure hackers. Of course, one of the first things you will find yourself doing is turning on services (e.g., IIS, File Server, Print Services, DNS, etc.). Only what you specifically install will be enabled.
Shawn Wildermuth is the founder of ADOGuy.com and is the author of "Pragmatic ADO.NET" for Addison-Wesley.
Return to ONDotnet.com
Copyright © 2009 O'Reilly Media, Inc.