This isn't specific to SuSE, but I'm looking for good arguments against my network going to Exchange, other than it's just bad. So, I'm asking Linux and other related mailing lists for assistance on gathering documentation on why Linux/Unix-based mail systems are better than Exchange for >2,000 user sized networks, specifically in education. Any help is grately appreciated. Khanh Tran Network Operations Sarah Lawrence College
On Thu April 14 2005 6:45 pm, Khanh Tran wrote:
This isn't specific to SuSE, but I'm looking for good arguments against my network going to Exchange, other than it's just bad. So, I'm asking
Sorry, and no insult intended to you, but someone HAS to be an idiot to even consider it based on how INSECURE it is!! I know there are MickySoft certified IT staff that are plum stupid and can't think logically - maybe it's one of them that's pushing for it.
Linux and other related mailing lists for assistance on gathering documentation on why Linux/Unix-based mail systems are better than Exchange for 2,000 user sized networks, specifically in education.
Any help is grately appreciated.
I'd simply gather all the security breech data I can find and submit it. Fred -- The only bug free software from MickySoft is still shrink-wrapped in their warehouse..."
On Thu, Apr 14, 2005 at 07:43:18PM -0400, Fred A. Miller wrote:
On Thu April 14 2005 6:45 pm, Khanh Tran wrote:
This isn't specific to SuSE, but I'm looking for good arguments against my network going to Exchange, other than it's just bad. So, I'm asking
Sorry, and no insult intended to you, but someone HAS to be an idiot to even consider it based on how INSECURE it is!! I know there are MickySoft certified IT staff that are plum stupid and can't think logically - maybe it's one of them that's pushing for it.
Linux and other related mailing lists for assistance on gathering documentation on why Linux/Unix-based mail systems are better than Exchange for 2,000 user sized networks, specifically in education.
Any help is grately appreciated.
I'd simply gather all the security breech data I can find and submit it. This isn't going to be enough for a company, if you really want them to not use it, go online and look up prices. Remember of course not just prices, but how much it would cost for the particular lisence you'd need, and make a slide show or something and show how much it's going to cost, how much you'll need to spend on it because I believe Exchange is a lisence based cost (Sorry can't help more with this but I don't work in IT, and never
have as of yet, I do research on these things myself though so just grab some information on cost, and after you have them thinking about that, THEN show the security problem this would more than likely create. Then start talking about down time. Being a Microsoft product every new worm that gets released, you'll be cleaning up after. Remind them this problem rarey exists in Unix.
Fred
-- The only bug free software from MickySoft is still shrink-wrapped in their warehouse..."
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Thursday 14 April 2005 10:39 pm, Allen wrote: <SNIP>
This isn't going to be enough for a company, if you really want them to not use it, go online and look up prices. Remember of course not just prices, but how much it would cost for the particular lisence you'd need, and make a slide show or something and show how much it's going to cost, how much you'll need to spend on it because I believe Exchange is a lisence based cost (Sorry can't help more with this but I don't work in IT, and never <SNIP>
The Bynari site has a TCO comparison chart that may be useful, although I don't think they would be the best choice for the number of users the OP is talking about. Go to Google and type "openexchange review". This provides lots of ammo. Then replace "openexchange" with the other systems that have been mentioned. Compile all the information from the reviews (which will include security, compatability, TCO, etc.) into a suitable document. From Linux.com for example: Most corporate desktop machines are currently running some version of Microsoft Windows, using Exchange and Active Directory as a primary method of achieving similar functionality to what is described above. The trouble is, attempting to make and keep Exchange and Windows secure is a hassle that any Windows sysadmin is all too familiar with. and: Microsoft Exchange is "dirtier" than its competitors, requiring constant maintenance in the form of daily garbage collection and frequent security updates. Exchange is tightly integrated with and totally dependent on the proprietary Windows-only Active Directory, and can't use NIS, LDAP, or Radius to authenticate. In contrast, Openexchange uses LDAP, which is supported by Solaris, GNU/Linux, and Free/Open/NetBSD -- the client machines are not limited to one operating system. This was just the first article I clicked on. A little searching should provide everything you need ... of course ... they will probably say "We think we'll stick with what we know" ... even though they know little to nothing about Exchange. -- Louis Richards
On Thu April 14 2005 10:39 pm, Allen wrote:
Any help is grately appreciated.
I'd simply gather all the security breech data I can find and submit it.
This isn't going to be enough for a company, if you really want them to not use it, go online and look up prices. Remember of course not just prices, but how much it would cost for the particular lisence you'd need, and make a slide show or something and show how much it's going to cost, how much you'll need to spend on it because I believe Exchange is a lisence based cost (Sorry can't help more with this but I don't work in IT, and never have as of yet, I do research on these things myself though so just grab
Well I have and do. Security issues with Exchange server are VERY REAL, and have to be included in the over all cost. The lack of stability is another!
some information on cost, and after you have them thinking about that, THEN show the security problem this would more than likely create.
Then start talking about down time. Being a Microsoft product every new worm that gets released, you'll be cleaning up after. Remind them this problem rarey exists in Unix.
I'd talk to SUSE about OpenExchange......I'd bet that they can provide you with the data you need. Fred -- The only bug free software from MickySoft is still shrink-wrapped in their warehouse..."
Khanh Tran wrote:
This isn't specific to SuSE, but I'm looking for good arguments against my network going to Exchange, other than it's just bad. So, I'm asking Linux and other related mailing lists for assistance on gathering documentation on why Linux/Unix-based mail systems are better than Exchange for >2,000 user sized networks, specifically in education.
Might be a stupid question, but what exactly are the requirements that should be met? Exchange is a Groupware, where email is only one of several services in the package. To use Exchange as a pure mailserver would be rather wasteful. Would that count as an argument against exchange? Sandy
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Khanh Tran wrote: | This isn't specific to SuSE, but I'm looking for good arguments against | my network going to Exchange, other than it's just bad. So, I'm asking | Linux and other related mailing lists for assistance on gathering | documentation on why Linux/Unix-based mail systems are better than | Exchange for >2,000 user sized networks, specifically in education. | | Any help is grately appreciated. where do i start? at the previous company that i worked for we had exchange. - - i can not think of one week that the server didn't die at least once, and we only had 150 people on the network (not 2000 like you). - - the total mailbox (i.e. everyone's mailboxes combined) size is restricted depending on what version of exchange you are using (standard, professional, etc). i.e. if you want bigger, you have to upgrade! (now where have i heard that before?) - - you have to have a license to run exchange on the server. - - you need a client access license for every computer that is going to connect to the server - - if you want web-based access to your e-mail, that's another set of licenses - -- Raoul Snyman Saturn Laboratories Web: http://www.saturnlaboratories.co.za/ E-mail: raoul.snyman@saturnlaboratories.co.za Blog: http://blog.saturnlaboratories.co.za/ Linux User #333298 (http://counter.li.org/) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCX2KxdabIu5z4rwwRAtS3AKCAuk4QRc4Owl1zS/5N21MF7JP2vwCfQLEr xIZjreOzIWKNHWlVAtQogSg= =3nVw -----END PGP SIGNATURE-----
Add to the list from the words of seasoned exchange admin (not me): - Yesterday he lost his message store, because exchange did not report disks were full. He recovered, but it required inside knowledge. - Message store is kept in only one file, that cannot be backed up online. You hae to stop service for backups. (Can't vouch for these, as I myself have no clue about M$) Best Dan Am Friday, 15. April 2005 08:44 schrieb Raoul Snyman:
- i can not think of one week that the server didn't die at least once, and we only had 150 people on the network (not 2000 like you). - the total mailbox (i.e. everyone's mailboxes combined) size is restricted depending on what version of exchange you are using (standard, professional, etc). i.e. if you want bigger, you have to upgrade! (now where have i heard that before?) - you have to have a license to run exchange on the server. - you need a client access license for every computer that is going to connect to the server - if you want web-based access to your e-mail, that's another set of licenses
participants (7)
-
Allen -
Dan Am -
Fred A. Miller -
Khanh Tran -
Louis Richards -
Raoul Snyman -
Sandy Drobic