RE: Exchange Server 5

  • From: "Jeffrey Robillard" <jrobill@xxxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Thu, 3 Jan 2002 12:51:43 -0500

One of the huge problems with exchange server 5, which makes it worth the 
investment really,  is that it has no spam blocking filters.   If you go to 
websites about spam and find out how to make exchange server 5 do spam blocking 
the recommended option is "replacement".

If you go to exchange 5.5, which the upgrade wizard seemed pretty capable, keep 
in mind that to upgrade the information store you will need free space greater 
than that of the info store itself.   If your info store is 10gb you will need 
like 20gb free to do the upgrade or it will just puke half way through.   

Also,  you cant go straight from 5 to 2000.


-----Original Message-----
From: Chris Thompson [mailto:chris@xxxxxxxxxxxxxxxxxxxxxxxxx]
Sent: Thursday, January 03, 2002 12:18 PM
To: [ExchangeList]
Subject: [exchangelist] Exchange Server 5


http://www.MSExchange.org/


I just recently inherited a site with a couple of NT 4 Servers and an
Exchange 5 server. It's been a while since I've had to maintain an
Exchange Server...come to think of it, I haven't even laid hands on an
Exchange Server since about 1997.
I seem to be able to find very little reference to Exchange Server 5 on
the Internet. There seems to be a good deal of information on Exchange
Server 5.5 and 2000. Is there an upgrade path from 5 to 5.5 that doesn't
involve a significant investment (times are tough)? And what would the
benefit be in upgrading the Exchange Server? This organization is using
this single Exchange Server in a small business setting with about 20
clients for internal email as well as SMTP Internet email.

Thanks for your advice.
Regards,
   Chris Thompson

chris@xxxxxxxxxxxxxxxxxxxxxxxxx

------------------------------------------------------
You are currently subscribed to this MSExchange.org Discussion List as: 
jrobill@xxxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')


Other related posts: