Internet Information Server

Internet Information Server 7, part of WS '08, offers more security features. Like the rest of the operating system, IIS has been componentized. There are more than 40 different pieces that can be installed to build a Web server, says Ralston. IIS 7 includes many security improvements, he adds. For example, a remote procedure call can't write to the registry or file system anymore because the security token for the account it runs under no longer has those privileges baked in.

IIS 7 is the most interesting part of Server 2008 for Zimmerman at CenterPoint Properties. "All of our applications are Web-based, so we like to keep current," he says. He points to improvements in streaming-media capabilities and in how IIS interacts with Active Server Pages, as well as the ease with which WS '08 can propagate configuration updates to Web server farms, as compelling reasons to upgrade.

It's not, however, compelling enough to make an IIS migration a top priority. "We don't have the time and project plan to focus on Windows Server 2008 right now," Zimmerman says. For now, he will continue to deploy Windows Server 2003 as needed and gradually begin upgrading later this year, starting with noncritical servers, he says.

SP2: The new SP1

While it's typical for organizations to wait for the first service pack before deploying a new operating system from Microsoft, in Computerworld's survey, just over a third of respondents said they'd wait for the next service pack before deploying WS '08. Small companies were the most cautious.

One reason may be the perception that WS '08 has already had its first service pack, since Microsoft rolled up Vista's SP1 into the initial release of the product. Indeed, Microsoft has announced that the first true service pack for WS '08 will be labeled "SP2."

But while Vista and WS '08 do share a common code base, the server OS is far more modular and has many features that aren't part of Vista. At best, Vista SP1 was a partial service pack for WS '08. "SP2 is the old SP1," says Vanguard's Moore. "I'm not convinced that they've fixed all of the quality issues. We'll wait until SP2." Vanguard will begin a gradual rollout only when SP2 finally ships, he says.

Pacific Coast's Okuma is also cautious. "Our organization will definitely wait" for SP2, he says.

But that's not stopping Mawson at Woods & Aitken. SP1 "was already integrated into Server 2008, so that didn't play into the decision for us," he says, adding that he has seen no crashes so far with his test server.

Zimmerman currently has WS '08 running on a test machine. "We like it," he says but notes that he'll wait for the next service pack. "We kind of hang out until [SP2 ships], unless there's some overwhelming argument that it's stable," he adds.

"Sometime after SP2 comes out, we will start to look at rolling through a refresh," says Moore. He expects to start sometime next year. The rollout will require six months of planning and 12 to 18 months to complete.

Perhaps the biggest reason why SP2 doesn't matter is that the update is likely to arrive before many organizations can initiate major deployments. Redman says SP2 is important but not a concern on his planning horizon: "By the time we get around to [deploying Windows Server], there usually is [a service pack]." The real bottleneck, he says, is evaluation and planning time. "It could take us six months to a year to finish looking at the features, play with them and see what it will buy us," he says.