Microsoft to launch .Net server as Windows Server 2003?
Posted by Mr magoo on 09 January 2003 - 11:03 · 26 comments & 2452 views
About the Author
Full name: Unknown
Forum name:
Mr magoo
Contact: via forum PM
Submissions: Normal · Headline
Full name: Unknown
Forum name:
Mr magooContact: via forum PM
Submissions: Normal · Headline
Slashdot It!
Submit to reddit
Submit to blinklist
Bookmark on del.icio.us
Add to furl
Share on Facebook
Add to Windows Live
Add to Google- Advertisement
-
-
#1 Posted by jkuy9 on 09 Jan 2003 - 11:16
- Not really surprising. Although I did like .NET Server as a name. Microsoft are rubbish when it comes to creating names for their products, they make a good name for something in development but change it to something very boring, like Windows Media Player 9 Series
-
(10 replies)
#2 Posted by xStainDx on 09 Jan 2003 - 11:18
- this thing has more name changes then the number of fingers on 1 of my hands!
-
#2.2 Posted by Tom Servo on 09 Jan 2003 - 11:20
- Dunno, that's what I remember: Windows XP Server Windows 2003 Server Windows.NET Server Windows.NET Server 2003 Windows Server 2003 (now)
-
#2.5 Posted by Neobond on 09 Jan 2003 - 11:28
- I remember them starting it as Windows 2002 Server (at least thats what Paul Thurrott speculated way back when) [url=http://www.neowin.net/comments.php?id=4663&category=main&highlight=Windows+2002+Server]http://www.neowin.net/comments.php?id=4663&category=main&highlight=Windows+2002+Server[/url] (our reference to it)
-
#2.6 Posted by xStainDx on 09 Jan 2003 - 12:16
- yeah, until it was delayed about 6 times, it was to be released last year.
-
#2.7 Posted by Jason on 09 Jan 2003 - 14:11
- [neoquote=#2.2 by Tom Servo]Dunno, that's what I remember: Windows XP Server Windows 2003 Server Windows.NET Server Windows.NET Server 2003 Windows Server 2003 (now)[/neoquote] Correct there has been a lot, but yo uhave to get the name right to maket the product.
-
#2.8 Posted by silly_walk on 09 Jan 2003 - 14:19
- They made it more confusing by adding the .NET like a year ago, and just now they realize this and change it back? Special people in their Marketing dept., apparently.
-
#2.9 Posted by JaggedFlame on 09 Jan 2003 - 14:25
- Same jokers who came up with XP, I guess... This, though, is a good move. I was wondering what the hell kinda ganja was in the marketing department.
-
#3 Posted by ahodes1 on 09 Jan 2003 - 11:20
- Now, I'm not trying to say I don't like the name change, but I think by RC2 the name should be pretty well finalized. How many names has it had now? Beta 3 it was Windows .net server, RC2 it was Windows.net Server 2003, now Windows Server 2003. Kinda bout that time where you make up your mind and make a commitment, don't you think? I do think, however, that Windows Server 2003 is a better name, so kudos to them I suppose.
-
(2 replies)
#4 Posted by SMG on 09 Jan 2003 - 11:24
- cant they make up their minds?
-
#4.1 Posted by xStainDx on 09 Jan 2003 - 11:25
- we're talking about Microsoft Corp, ya know that company up in Redmond.
They always change everything, up to the last minute possible!
-
#4.2 Posted by JaggedFlame on 09 Jan 2003 - 14:26
- Like what?
-
(1 reply)
#5 Posted by _Pablo on 09 Jan 2003 - 12:05
- The problem is that the whole .Net branding has become very confused - is it a technology/platform/marketing? So much so that it is confusing customers, many of whom may assume that Windows .Net Server was only needed for rolling out .Net applications - which could lessen the take-up and threaten the upgrade cycle. So Windows Server it is and it is also back to the tried and tested method of built-in marketing obsolescence with a year as part of the name! After all, Windows 2000 is beginning to look old when its name is written down!
-
#5.1 Posted by Neobond on 09 Jan 2003 - 12:16
- [quote]So Windows Server it is and it is also back to the tried and tested method of built-in marketing obsolescence with a year as part of the name! After all, Windows 2000 is beginning to look old when its name is written down![/quote]
successful marketting really is in the name
-
(1 reply)
#6 Posted by Jason on 09 Jan 2003 - 14:41
- Until it has .Net managed APIs it shouldn't have the .Net name
-
#6.1 Posted by JaggedFlame on 09 Jan 2003 - 22:14
- It's a sort of launchpad for other .NET servers, such as SQL or Exchange, which do utilize .NET. So, .NET Server isn't really that outrageous a name for it.
-
#7 Posted by Huy on 10 Jan 2003 - 02:21
- 'Windows 2003 Server' would have been cool
Kind of like Windows 2000 Server, Advanced Server, et al
But 'Windows Server 2003' is good too
-
(1 reply)
#8 Posted by phantomAI on 10 Jan 2003 - 06:28
- longhorn or blackcomb will probably be named Windows.Net
-
#9 Posted by ye110man on 10 Jan 2003 - 17:59
- i think this is a sign that they're droping the whole .net naming altogether. i wonder if they're going to keep the xp naming. the next office was supposed to be called office.net. now it'll probably be called office xp 2003 or just office 2003. i hope they do drop the xp. let's go back to the windows 95 to windows 2000 days. better yet let's go back to the version numbering. at least for the non-windows products. just call the next office, office 11 or office xi.
-
#10 Posted by lexp on 10 Jan 2003 - 23:13
- Longhorn will be .NET by architecture - all its' functionality will be in MSIL code all be .NET -wrapped. Windows 2003 Server is TRUE name for this product, cos' it contains only .NET Framework and maybe UDDI in .NET. All its' stuff is COM-based or even native dll. My opinion.
-
#11 Posted by sdazzo on 11 Jan 2003 - 08:51
- I thought Whistler was .net. I remeber receiving something in the mail from Microsoft about XML-Enabled products and how it was the future, blah blah blah, and in one section it said, and i qoute, "..next version of Windows code-named "Whistler" server family.
"The product name Microsoft(R) Windows(R) .NET Server 2003 will be changing to Windows Server 2003. Microsoft is making an effort to clarify the naming and branding strategy for .NET. As support for Web services becomes intrinsic across our entire product line, we are moving toward a consistent naming and branding strategy to better enable partners to affiliate with this strategy and customers to identify .NET-enabled products. The first product to be affected is Windows .NET Server 2003. The new name for the next version of Windows is Windows Server 2003. This information still needs to be treated confidential under NDA and will not be public until Thursday, January 9, 2003. This will not affect our time frame for launch, which is still planned for April 2003."
The specific reason for the name change is thus :
"In response to customer and partner feedback to provide clarity around our .NET strategy and programs. Specifically, we are moving toward a branding approach where ".NET Connected" is the way we communicate our products (and our partners' products) that enable customers to easily and consistently connect disparate information, systems, and devices to meet their people and business needs, regardless of underlying platform or programming languages. "
Intreged? It would appear MS are launching yet another strategy / brand ideal here; perhaps the same thing under a different name. Either way, this will probably just cause more confusion amongst customers. Ah well! Read more for further details and a quick FAQ thing from MS on the topic.
Details:
* We are pursuing an overall effort to clarify the naming and branding strategy around .NET. As support for Web services becomes intrinsic across our entire product line, we are moving toward a consistent naming and branding strategy to better enable partners to affiliate with this strategy and customers to identify .NET-enabled products.
* The next version of Windows Server will be formally called Windows Server 2003. The reason for this is to simplify the product's naming and reconcile it with our branding strategy for .NET.
* Windows Server 2003 will carry the "Microsoft .NET Connected" logo indicating its ability to easily and consistently connect disparate information, systems, and devices to meet customers' people and business needs (regardless of underlying platform or programming language). This logo is also available to our partners building solutions on the Microsoft platform to help customers identify solutions and products that support standards-based interoperability.
* The more complete integration of .NET Web services and products is one of several major enhancements in Windows Server 2003 -- all aimed at providing a highly connected, productive, and dependable infrastructure with excellent economic value for our customers.
Questions & Answers:
Q) Why the name change?
A) In response to customer and partner feedback to provide clarity around our .NET strategy and programs. Specifically, we are moving toward a branding approach where ".NET Connected" is the way we communicate our products (and our partners' products) that enable customers to easily and consistently connect disparate information, systems, and devices to meet their people and business needs, regardless of underlying platform or programming languages.
Q) Why make this change now?
A) Product naming, features, etc. are never final until the product ships -- this is both in response to customer feedback as well as part of a larger effort to provide clarity for customers and partners interested in affiliating with and benefiting from Microsoft .NET.
Q) What changes technically in the Windows Server product as a result of this name change?
A) There are no feature changes in the product. This is a naming change, and does not affect the functionality of the product in any way.
Q) Will this cause a slip in the Windows Server 2003 product schedule?
A) No -- we remain on track for a worldwide launch of Windows Server 2003 in April 2003.
Q) Is this an indication that Microsoft is backing away from .NET?
A) Quite the opposite -- Windows Server 2003 is a major step forward in our effort to provide a highly connected, productive, and dependable infrastructure with excellent economic value for our customers. Windows Server 2003, with integration of the Microsoft .NET Framework, UDDI services, and other XML Web services support has set the industry bar for Web service development and performance -- combined with the new security, scalability, and performance of Windows Server 2003 and we are delivering a platform optimized for the next generation of enterprise computing.