| ActiveMac | Anonymous | Create a User | Reviews | News | Forums | Advertise |
|
|
|
User Controls |
|
New User |
|
Login |
|
Edit/View My Profile |
|
|
|
|
|
|
|
ActiveMac |
|
Articles |
|
Forums |
|
Links |
|
News |
|
News Search |
|
Reviews |
|
|
|
|
|
|
|
News Centers |
|
Windows/Microsoft |
|
DVD |
|
ActiveHardware |
|
Xbox |
|
MaINTosh |
|
News Search |
|
|
|
|
|
|
|
ANet Chats |
|
The Lobby |
|
Special Events Room |
|
Developer's Lounge |
|
XBox Chat |
|
|
|
|
|
|
|
FAQ's |
|
Windows 98/98 SE |
|
Windows 2000 |
|
Windows Me |
|
Windows "Whistler" XP |
|
Windows CE |
|
Internet Explorer 6 |
|
Internet Explorer 5 |
|
Xbox |
|
DirectX |
|
DVD's |
|
|
|
|
|
|
|
TopTechTips |
|
Registry Tips |
|
Windows 95/98 |
|
Windows 2000 |
|
Internet Explorer 4 |
|
Internet Explorer 5 |
|
Windows NT Tips |
|
Program Tips |
|
Easter Eggs |
|
Hardware |
|
DVD |
|
|
|
|
|
|
|
Latest Reviews |
|
Applications |
|
Microsoft Windows XP Professional |
|
Norton SystemWorks 2002 |
|
|
|
Hardware |
|
Intel Personal Audio Player 3000 |
|
Microsoft Wireless IntelliMouse Explorer |
|
|
|
|
|
|
|
Site News/Info |
|
About This Site |
|
Affiliates |
|
ANet Forums |
|
Contact Us |
|
Default Home Page |
|
Link To Us |
|
Links |
|
Member Pages |
|
Site Search |
|
Awards |
|
|
|
|
|
|
|
Credits |
 |
Complex .Net migration worries users | |
|
||
| Time: 07:44 EST/12:44 GMT | News Source: VNUNet | Posted By: Byron Hinson | ||
|
Microsoft has clarified the migration path for Exchange on Windows 2000 to .Net, but the complex answer could be a taste of wider migration issues ahead. The software giant confirmed that Exchange Server 2000 will not run on its .Net Server operating system, and that users will have to wait until at least next year to migrate to .Net Exchange, codenamed Titanium. Titanium is due in beta this month with a final release scheduled for the first half of 2003. Microsoft has promised that Titanium will be backwards compatible with Windows 2000 (with Service Pack 3 installed), making it possible to upgrade to Titanium before upgrading to .Net itself. | ||
|
Write Comment
Return to News |
Displaying 1 through 25 of 138 Last | Next |
The time now is
4:24:57 AM
ET.
Any comment problems? E-mail us |
| #1 By 6253 (12.237.219.240) at 8/13/2002 10:34:39 AM |
|
This is completely inexcusable. It was understandable that E2K required W2K because of AD. But there isn't a good reason that Microsoft couldn't roll up its sleeves and get E2K SP3 (or even SP4) to work with .NET Server, especially since there's still time left to change .NET Server.
How can Microsoft expect ISVs to make third-party apps compatible with .NET Server if they can't make their own apps compatible with their own OS? How can they expect customers to deploy .NET Server when mission-critical apps like messaging can't move? It's not just that this issue pisses me off. It's also completely bewildering. This can only hurt sales of .NET Server (or E2K, or both). How can they be so stupid and lazy? Did the Exchange group just wake up and say, "Uh, we didn't know a new OS was coming"? |
| #2 By 415 (68.54.10.120) at 8/15/2002 2:04:31 AM |
| You can't always maintain backwards compatibility, so ,.|.. ..|., you too! |
|
Write Comment
Return to News |
Displaying 1 through 25 of 138 Last | Next |
The time now is
4:24:57 AM
ET.
Any comment problems? E-mail us |
