Is Exchange 2003 best for me?

[bleedingeyes]

I need to find a network email solution to replace my Microsft Outlook with roaming clients. Here is my network layout.

Three Advance 2000 servers. 2 of which running DNS server with AD. The third server is a recent addition to resolve my email problem but has not been configured. I had plans to install Exchange but I am not sure if I should.

20 lan computers and a few notebooks. All lan users (except admin) have roaming accounts.

We have a colocated unix box that provides our pop and SMTP services.

We also have another unix server in our rack that is to replace our colocated server soon (within 4 months).

Problem: Several users will have extremely long login times and logout times. Some times their profile can not be saved. I believe that it is a result from the profile being way too large. Some user's PST files are greater than 1.5 gigs.

I understand that microsoft outlook 2000 was not designed for roaming profiles and that the work around is to move the PST file to the file server where the profile resides. We have been using this method for years but since our network have grown from 5 users to 20+, we have experienced corrupt PST files, losing contacts, long boot ups, long shut downs and error messges that state could not save XXXXXXXXX.prn file (I beleive to be a outlook 2000 tmp file that is really a PST file because it can be greater than 1 gig).

I had plans to install exchange 2003 but during the installation I did not see where I could use a colocated SMTP and pop server. I am afraid that exchange may be too large, and too problematic for a solution. I really just need a better way to have roaming email network that appears just like microsft outlook. (I do like the fact that exchange 2003 has a web based outlook interface). All suggestions are welcomed.

 

[Superenigmatix]

Sounds like Exchange is a great solution for you - I would try and get away from PST files as fast as possible - especially ones that large. When you hit 2Gb they will lock up on you and any data over the 2Gb limit will not normally be recoverable.

You should also be able to do away with POP once you are converted over completely and bring all mail in through SMTP. I don't know how convoluted all your e-mail addresses, domains, etc, etc are but this is a good way to make yourself simplify it!

Look at the MS report - Exchange Server 2003 Deployment Guide - should be found at

http://www.microsoft.com/exchange/library

While I'm at it I would also recommend an application called Mail Marshal (

http://www.marshalsoftware)

that acts as the SMTP server, as a content filter, and runs (multiple) AV programs on all mail before it hits the mail server - it's saved my company's bacon many a time, we've never had a virus get through in the five years I've been here.

cheers

sE

 

[bleedingeyes]

Superenigmatix: Since I have a unix based machine that could easily serve as a SMTP server, should I and could I use it as the SMTP instead of Exchange? I have over fifty outside email accounts that do not need access to my local network. When using exchange, do I have to give those fifty users local accounts? This is a security issue for us. Thanks a lot for your time.

 

[Marcs41]

You can use it to relay the Exchange feed, and it will shield the Exchange server from the outside as well.
So, in your case, I would keep the unix machine, but move the internal users over to Exchange, there is a wealth of 'goodies' with 2003 which can improve teamwork etc.

Marc
_{If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!}
How Do I Get Great Answers To my Tek-Tips Questions? See faq219-2884