Jon A
Guest
|
 Posted:
Wed Jan 05, 2005 10:14 pm Post subject:
iMail to Exchange 2003 Migration. Worth the wait ? |
|
|
Hi,
Been asked to assess changing from an iMail installation to Exchange 2003
iMail has worked well. It's used for POP3, SMTP and some server-side rules
(to route e-mail sent to 1 recipient to a group etc.). We don't use global
address lists etc.
The e-mail server is located in remote data centre. It's not part of a
domain and works as a standalone server.
I know Exchange can do all this and plenty more besides. The free
integrated spam engine which is a definite plus for moving to Exchange.
But ... my colleague thinks Exchange is too heavyweight for these e-mail
requirements, it'll take longer to configure, backup, patch and support etc.
Are some of you using it as a basic e-mail server like we would ?
If there's no domain, does it need to be a domain controller or have AD ?
TIA
Jon A
London, UK
|
|
Glen Trafford
Guest
|
| Posted:
Thu Jan 06, 2005 8:26 am Post subject:
Re: iMail to Exchange 2003 Migration. Worth the wait ? |
|
|
Exchange has to have an AD domain. It can reside on the same box as the
server in small environments.
Not sure about the longer to backup. It would depend more on the amount of
data. There is built in capability for backup in Windows that does support
exchange.
Cost would be an issue and SBS - Small Business Server is an option here.
It is a big change going to the domain concept, but could make sharing info
a lot easier.
You have options to use OWA. Spam can be covered by IMF (free from MS) but
you will need to look at buying anti virus software.
Exchange does run in small companies. It depends on the level of comfort
with Exchange and Microsoft And perceived risk in terms of support both from
the vendor and the IT community. Ease of use would be a big factor as well.
Glen
"Jon A" <jon@pitstart.com> wrote in message
news:Oly9TF08EHA.1392@tk2msftngp13.phx.gbl...
| Quote: | Hi,
Been asked to assess changing from an iMail installation to Exchange 2003
iMail has worked well. It's used for POP3, SMTP and some server-side
rules
(to route e-mail sent to 1 recipient to a group etc.). We don't use
global
address lists etc.
The e-mail server is located in remote data centre. It's not part of a
domain and works as a standalone server.
I know Exchange can do all this and plenty more besides. The free
integrated spam engine which is a definite plus for moving to Exchange.
But ... my colleague thinks Exchange is too heavyweight for these e-mail
requirements, it'll take longer to configure, backup, patch and support
etc.
Are some of you using it as a basic e-mail server like we would ?
If there's no domain, does it need to be a domain controller or have AD ?
TIA
Jon A
London, UK
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in