All Things Microsoft > Microsoft as a Company

No server Longhorn, but big .NET Server changes due in 2004

(1/1)

TB:
http://www.theregister.co.uk/content/4/28210.html

_________________________________________________

Microsoft's next major version of Windows, Longhorn, will be a client OS only, Microsoft's objective being not to trouble its customers with a major server OS upgrade so soon after .NET Server 2003 ships. But from what Microsoft senior vp for Windows Brian Valentine was saying at Microsoft IT Forum in Copenhagen this week, Longhorn the client is going to be sufficiently radical for companies to have to make major changes in their server OS anyway.

Valentine confirmed that Longhorn would be client only, and said it would be due no sooner than mid- to late 2004. But the new file system for Longhorn will require major server side changes, delivered as a service pack or some kind of add-on pack. According to The Register's eye-witness he said Longhorn used a genuine new store, rather than a "lashup of .NET frame work 'children of OLE-DB' strung together."

Effectively, although Microsoft isn't planning a server upgrade synced with Longhorn, it will be issuing an upgrade of sorts as a kind of monster service pack from hell when Longhorn ships, this to be followed by a further major server release in the Blackcomb timeframe.

So people who don't have any compelling need to switch over to .NET Server might well take the view that life will be a lot easier if they just stick with Windows 2000 until Longhorn ships, then install the lot in one go. Under the circumstances, the service/add-on pack plus .NET Server combo should surely be called .NOT Longhorn Server.
__________________________________________________

It looks like Microsoft have upped the ante in their fight against open source. So when Longhorn ships any company that wants to use Longhorn clients will now pracitcally be FORCED to using M$ servers too? Wow, great marketing strategy.... .NOT!

hm_murdock:
why will a server OS require a service pack to interact with a client OS in the same family, based on the same kernel?

does the server get direct filesystem access? that's the only reason it would need an update. that idea troubles me

Navigation

[0] Message Index