END OF 5.5 SUPPORT

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Craig Dayton (anonymous_at_discussions.microsoft.com)
Date: 02/25/04


Date: Wed, 25 Feb 2004 12:37:28 -0800

Has anyone heard if Microsoft is going to be ending
Exchange 5.5 support? I know that support for NT 4.0 ends
January 1, 2005, but I have not heard anything yet about
Exchange. If you know or can point me in the right
direction, I'd appreciate it.

Thank you,

Craig



Relevant Pages

  • Re: Exch 2003 & Win2003 sp1
    ... Microsoft Online Partner Support ... Microsoft technology partners in the United States and Canada. ... It is always strongly recommended that you fully backup the server, ... >> Configuration Wizard is run on an Exchange server on which Exchange ...
    (microsoft.public.exchange2000.general)
  • RE: Repairing / modyfing Exchange
    ... > Customer Service and Support for more immediate assistance. ... > This service gives you access to Microsoft technical support engineers who ... As you mentioned, you have reinstalled the Exchange, and overwrote the ... > database by using the old Server's database files, ...
    (microsoft.public.windows.server.sbs)
  • Exchange enhancements in iPhone 3.1 cause some users grief
    ... Exchange enhancements in iPhone 3.1 cause some users grief ... Improved support for Microsoft's Exchange Server's security policy features, ...
    (comp.sys.mac.advocacy)
  • Re: Exchange connection via 3rd party proxy server SBS SP1 Standard?
    ... contact CSS for better support. ... | wireless connection, which is very slow. ... | I now what to change my internet connection and make sure that Exchange ... | Client connecting here must go via a proxy Server installed on this ...
    (microsoft.public.windows.server.sbs)
  • Re: Best email solution for small company
    ... Mdaemon support is $60 per incident. ... I don't know why you think it would be worse with Mdaemon. ... already had an exchange structure and an IT group 1 1/2 people) it was ...
    (microsoft.public.exchange.admin)