On Fri, 2003-08-22 at 12:15, [EMAIL PROTECTED] wrote: > Having used, installed and cofigured exchange quite a bit in the past I can > tell you that you are wrong on most counts below.
:-) I take it you've done this in a business setting. > You can create individual PSTs from each user Not for 1400 users I won't , or configure each computer to > maintain a local copy of their mail in order to move email from one server to > another, Only about 12 staff have their own computer - the rest are all shared. So the old business idea of "One Person One Computer" just does not work. let alone backing it up and restoring it en masse between exchange > servers. PSTs can be imported into outlook regardless of the user or their > existing email configuration. Outlook on P75s with 32 Mb ram? That would be like expecting Jamie Olliver to make a cullinary masterpiece using a Macdonalds kitchen. Moving outlook mail to something else, ie > Mozilla, is a little more complicated, but is do-able by passing it into > outlook express, then on to netscape / mozilla. Other apps exist for moving > mail between other packages without resorting to individual forwarding. I think the question originally was more like "how do I move EVERYTHING to some other mailserver" Putting mail into a specific mail-reader application is not the end result required. > Using Backup Exec with the exchange option you can delete / restore individual > emails to/from tape. This is probably true for most decent backup packages. Yes - but schools don't have much money.... and decent backup packages cost a lot. We're still using NT4 server cos its too much to change to anything else. Indeed - my four linux boxes are backed up using home-grown scripts. > From memory the built in backup package in Windows 2000 server will not allow > this, but then its not really a 'real' backup package anyway (IMHO)... See above - 2000 is far newer than anything running here. > Exchange is prety misunderstood, and takes a lot of flak. Its not really a bad > package if you know how to use it (Something a lot of people say about Linux, > too :) I retract my statement earlier about "festering.." How about "simply totally unsuitable for schools" ? > PS: I'm not a Microsoft advocate, but I hate to see people shooting MS down > without a full understanding of the product they are attacking. I've never had any training on how to use exchange server - its too expensive. Do you see the problem? At least with an imap server running on a linux box I can ask google for help, and not come across the "hire an MSCE" stuff. > > On Fri, 2003-08-22 at 07:46, Terry Cole wrote: > > > With all the MS problems/virus as well as Exchange problems I have been > > > having.. > > > > Others can comment on the rest, but since I have an exchange server here > > and probably most of the problems you've had, I'll comment here. > > > > Exchange is a festering heap of fertilliser. There is no way to move > > all the existing mail from ES to any other mailserver other than > > forwarding all email manually. > > > > We have made a partial change - I run squirrelmail on the webserver > > (linux) which is a webmail/imap gateway, and that runs fairly well. > > > > Users will loose all the calendaring/schedualling/addressbook components > > of exchange server too, when you change to something else. > > > > But then - its impossible to restore a single email from a tape > > backup... you have to restore the lot to a scratch machine then forward > > it to the real server, so I have always told users to save important > > emails to disk. > > > > You might have to bite the bull's horns and change wholesale, loosing > > the old mail... which is going to be a real turn-off for users.
