Critical Windows fix on the way

TalkBack 16 of 46:

Next »

« Previous

• Thread View
• Flat View

Milly I feel your pain...

I am an MCSD, MCDBA, Novell Master CNE, and working on the Novell CLP. I am also a small business owner. We develop custom applications for the financial lending industry. I have been in this business for 25 years. Having said that....

The true problem with the issue at hand goes to the core windows product. The original manner in which windows was developed. By trying to take a "modular" approach (DLL's) Microsoft has caused their own nightmare. Your points about the 3rd party apps breaking are a direct result of this approach.

The lion reared it's head when Microsoft decided to get into networking. Prior to that, they were a desktop company. This goes to the heart of their problems. Because most users liked the windows dekstop OS, they naturally got a boost when they tried the network OS. As a result they got in over their head and have never really gotten a real network OS to work properly.

Longhorn is their first real network OS. It remains to be seen if they can truly put together a network OS instead of dekstop OS with network features.

Novell went through this in the early 90's. They saw the light when they abandoned the NetWare 2.x architecture. (Server and Desktop functionality). MS would have been wise to do the same.

Linux takes the same approach, for the most part. The Server OS is designed to be a server. NOT a desktop. Not intended to be both. The desktop product is a desktop and not intended to be a server.

This critical difference is real. Just the thought of using a server as a desktop and vice versa makes me cringe.

Their customer service issues only make these problems worse. Because of the duality of the system, proper customer support is very difficult at best, and impossible at worst. Case in point is an issue that revolves around a server service running on a desktop platform. Because you have XP installed you MUST deal with the desktop support, even though it is really a server issue. This results in not getting through to the proper people, or taking days to do so.

Since you are an MVP, I am wondering what insights you might have into how MS plans to address these issues with Longhorn. It is my understanding that they are finally going to split the desktop and server OS's (for real this time). Is this true? Will we be able to run Longhorn without a GUI? (This is critical for a server, since the GUI kills resources, as well as opens up holes).

I like most of the true IT people in this forum like the "intelligent" debate that can take place. I look forward to hearing from you.

Posted by: htotten   Posted on: 01/08/05 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• Why Isn't Server Virtualization Saving Us More? A Few Small Changes May Dramatically Increase Your Efficiency VMware Companies have rapidly adopted server virtualization over the past few ... Download Now
• Building the Virtualized Enterprise with VMware Iinfrastructure VMware VMware virtualization software has been adopted by over 120,000 enterprise ... Download Now
• Addressing Compliance Requirements for Privacy, Data Retention, and e-Discovery Trend Micro Protecting individual and financial data, retaining data, and meeting ... Download Now