Microsoft is developing versions of its Windows operating system with only a subset of the Windows code base, designed for specific server tasks, in a move that could reduce maintenance costs for customers and create products that are less vulnerable to attack.
The new "role-based" products may appear in 2007, when the server version of Longhorn is scheduled for release. Offering a smaller code base would mark a significant technical shift for Microsoft and could help it to better address the competitive threat posed by Linux. But it also presents significant engineering challenges for the company, industry analysts say.
Microsoft already sells two role-based versions of Windows--one for storage and one for Web serving. They essentially conceal from users the parts of Windows that are not needed for the task at hand, making them easier to install and use. But those products still are based on the entire Windows code base.
With its Longhorn release, Microsoft hopes to offer role-based versions of Windows for tasks such as storage, file, or print serving that include only a part of the overall Windows code, says Martin Taylor, Microsoft general manager for platform strategy.
"Today, it's still the entire code base. There's no reduction in the bits you get; things are just roped off," Taylor says. "We want to get to a model of role-based deployment where you might just have the bits you need for that function. ... It's one of our design goals for Longhorn."
Many enterprises separate tasks such as e-mail and Web hosting, assigning them to individual servers or groups of servers. Microsoft would continue to sell the full version of Windows for use as a general purpose operating system, but could offer the role-based products for servers assigned to particular tasks, he says.
Added Security, Lower Costs
Such a move could benefit customers in two primary ways: better security and lower maintenance costs, says Michael Cherry, lead analyst at Directions on Microsoft, a research company in Kirkland, Washington.
Reducing the amount of code on a server would reduce the "attack surface area," Cherry says, meaning hackers would have less code to aim at with their viruses. A virus last month that targeted a component for viewing JPEG image files affected Windows Server 2003, he notes, even though customers managing their servers remotely don't need that component on their servers.
Having less code should also mean lower maintenance costs, in part because customers will not have to apply patches to the parts of Windows that do not exist on their servers. "If you have a server whose role is definable and distinct, and you only load enough [code] to carry out that role, then it's got to bring the total cost of ownership down," Cherry says.
A Microsoft spokesperson confirms that the goals of providing a smaller Windows "footprint" are to cut maintenance costs and provide a "reduced surface attack area."
Taylor didn't say whether the role-based server editions would be lower in price than the full versions of Windows. The role-based products it sells today--Windows Storage Server 2003 and Windows Server 2003 Web Edition--are cheaper than the full versions of Windows Server 2003, although usage restrictions apply.
Removing parts of Windows presents engineering challenges. For starters, Microsoft must ensure that ISVs (independent software vendors) can continue to write applications for its operating system without worrying about which components are available to them, Taylor says.
"The nice thing about Windows today is that Windows is Windows," he says.
Microsoft is also keen not to limit the software's management capabilities. For example, the current Web Edition of Windows cannot serve as a domain controller, which means it can't be used to manage group policies, Internet authentication services, and other tasks.
"You have trade-offs in cost and trade-offs in manageability, so it's a fine balance," Taylor says.
He did not provide an exact timetable for the products, but says development work is "pretty far down the path."
Microsoft can predict, broadly speaking, what roles its customers want their server software to fill, but it can't predict every combination, Taylor says. For example, a customer might want to install a print server and a Web server on one system, and a storage server on another. He suggests that Microsoft may engineer the products in a way that allows customers to decide at deployment time which parts of the operating system they want to use.
"We can predict the roles, but some customers might want Web and print on the same server," Taylor says. "Instead of delivering these preconfigured, maybe there's a way to do it with a bit more customer input."
Some industry insiders have speculated that Microsoft would reduce the code base for certain server versions of Windows. When it developed Windows XP Embedded several years ago, part of the task was to figure out which parts of the operating system could be removed without disturbing the software's internal dependencies, Cherry notes.
"That knowledge of how the components work together could allow them to build versions of Windows with only specific functionality. ... It could be used to develop several other products," Cherry says.
The proposed changes to Windows come as Microsoft faces perhaps its toughest challenger yet in the form of Linux. The open source operating system has been gaining traction among governments and businesses, in part because some view it as a cheaper and more secure alternative.
One advantage of the Linux source code being publicly available is that customers--or more commonly systems integrators or resellers--can take the kernel apart and use only the components they want, to build a DNS (Domain Name System) server, for example, says Neil Macehiter, a research director at U.K. analyst company Ovum.
"I think they need to move to this model of having role- or function-based servers to compete better with Linux," he says.