Microsoft’s wide open beta testing paradigm, which combines unfettered interaction between Microsoft developers and customers and a formal system of gathering feedback from public testers, brings a whole new meaning to the word “beta.” Nowhere is proof of the vendor’s commitment to the program more evident than in the third beta release of Windows Server “Longhorn,” which looks like it’s been hit with a mega-dose of growth hormone since beta 2. And I mean that in a good way.

The Bottom Line Windows Server Longhorn beta 3 Microsoft, microsoft.com Beta   Ship Date: Beta 3 is available now; final release in 2H 2007 Cost: To be announced Platforms: AMD and Intel 32- and 64-bit x86 computers; peripherals require signed device drivers; AMD-V and Intel-VT hardware virtualization assist optional Bottom Line: In beta 3, Longhorn Server has taken solid form since its previous release. Major advances center on PowerScript, Microsoft's .Net command-line shell, which is accompanied by utilities that enable robust administration from the PowerShell command line or via text-only connections. Longhorn's firewall has been revamped for greater configurability, and the last pieces of Longhorn's virtualization story have fallen into place with Terminal Services, hypervisor-based 64-bit virtualization, and the productization of newly acquired SoftGrid. About our Reviews and Scoring Methodology

Longhorn beta 3 is distinguished not only by the strengthening of features that were wobbly in prior prereleases, but also by the addition of significant new functionality across the board. The new functionality is the focus of this preview.

Topping Microsoft’s list, and mine, is Microsoft’s fresh focus on the good, old-fashioned command line, starting with the addition of PowerShell to all Longhorn editions. PowerShell is Microsoft’s first scriptable command-line shell. Yes, there is the “DOS box” and the .bat file, both of which are among the last remaining cave paintings left behind by MS-DOS. PowerShell surpasses the expectations of, but will not be familiar to, those facile with Unix shells. It unlocks the entire .Net language suite to use for building PowerShell commands, and it promises an end to the need for command-line executables to parse untyped data sets with Unix tools such as sed, awk, and Perl. Developers can dream of being able to read scripts written by others.

Click for larger view.

In my estimation, PowerShell would be useless if it had only the inadequate command-line vocabulary of the DOS box. PowerShell has some 130 commands of its own, and Microsoft has added a command-line version of the GUI-only Server Manager, which is the master control console at the center of every Windows Server. Longhorn beta 3 also ushers in a variety of protected mechanisms for executing commands on remote systems, and IIS-style isolation can be applied to all scripted code, not just server-side scripts for Web sites. And the retro, green screen beat goes on. “Server Core” -- a subset of Windows Server that’s been stripped of its GUI -- is one of Windows Server Longhorn’s least celebrated but most welcome additions.

Out of the box security is still a Microsoft priority in this age of endless exploits. Contact with the world beyond your server is largely belayed until roles are defined and switches permitting network access are thrown, but a middle ground between shut-in and running naked on the Net has been struck with Longhorn’s sensible default firewall configuration. At install, Longhorn’s firewall, which sports a clearer and more flexible configuration interface in beta 3, is enabled and placed in a mode that opens ports only for services that are activated. This obviates the need for the little black book that admins carry to remind them of which TCP and UDP ports are used by commands and services.