RE: Report of MS Exchange disaster
Well first off, AV isn't even an option anymore. It is a must have. As for OWA, if they want it, put it on a separate box. In your case, a PC would do just fine. Backup Server? You don't necessarily need one of those. But you should have a recovery box. Once again, for 35 users, a PC would do just fine. Outsourcing sucks -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Paul Done Sent: Wednesday, October 24, 2001 9:09 AM To: Exchange Discussions Subject: Report of MS Exchange disaster Hello All! I am writing a report to management about a disater we had on our Microsoft exchange server a couple of weeks ago. I am hoping you might provide me with horror stories and/or best practice in your shops. My operation is small (=35) but would like to show success. If so we (15000+) may move off a 10 year old featureless UNIX. Among many things I am recommending for change follow: *Antivirus protection on the Exchange server - (DOH! -no we don't have it!) Would appreciate you suggestions/experience - I am looking at Sybari Antigen *Disabling OWA - only two people of 35 used it Good idea or not...? *Backup server A minimum configured backup server for rapid switch *Recommending against outsourced management of EX Looking for horror stories Thank you for your help. I am searching archives, but as you may know the good nature OT conversation proves a little thick to dig through. Paul _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
Re: Report of MS Exchange disaster
*Antivirus -Antigen can be configured to scan with more than one virus engine... handy, when one engine comes out before another one does. And that is just the start. *OWA -Running it internally? Depends -do you have non-MS clients? My *nix and Mac users liked OWA. Travelling users liked it as well, as long as you secure it as much as possible before putting it in the DMZ. *Outsourcing -Think about it like this. When you are hosting inhouse, your job is on the line, you will be a lot more conscientious than a company that can shift blame when/if something goes wrong. You have more control over your environment, and you *know* exactly who has access to your box. Hope that helps. ~ -K.Borndale Network Administrator Sybari Software 631.630.8569 -direct dial 631.439.0689 -fax http://www.sybari.com One man's ceiling is another man's floor |+--- || Paul Done| || [EMAIL PROTECTED]| || Sent by: | || bounce-exchange-148870@ls| || .swynk.com | || | || | || 10/24/2001 12:09 PM | || Please respond to| || Exchange Discussions | || | |+--- | | | | To: Exchange Discussions [EMAIL PROTECTED] | | cc: | | Subject: Report of MS Exchange disaster | | Hello All! I am writing a report to management about a disater we had on our Microsoft exchange server a couple of weeks ago. I am hoping you might provide me with horror stories and/or best practice in your shops. My operation is small (=35) but would like to show success. If so we (15000+) may move off a 10 year old featureless UNIX. Among many things I am recommending for change follow: *Antivirus protection on the Exchange server - (DOH! -no we don't have it!) Would appreciate you suggestions/experience - I am looking at Sybari Antigen *Disabling OWA - only two people of 35 used it Good idea or not...? *Backup server A minimum configured backup server for rapid switch *Recommending against outsourced management of EX Looking for horror stories Thank you for your help. I am searching archives, but as you may know the good nature OT conversation proves a little thick to dig through. Paul _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Report of MS Exchange disaster
*Antivirus: You're on good track. *OWA: If they need it, let'em have it. Great for access from home, or roaming users. And yes, put it on a separate box. *Backup: Use NTBACKUP for now. It'll work just fine. When you actually migrate the 15000+ users to Exchange, you may want to look at other units/sw that can provide you more features (if you need them that is). BackupExec or CommVault is what you'd want. *Outsourcing: Do you really want Hanjish people running your Exchange? S. -Original Message- From: Paul Done [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 12:09 PM To: Exchange Discussions Subject: Report of MS Exchange disaster Hello All! I am writing a report to management about a disater we had on our Microsoft exchange server a couple of weeks ago. I am hoping you might provide me with horror stories and/or best practice in your shops. My operation is small (=35) but would like to show success. If so we (15000+) may move off a 10 year old featureless UNIX. Among many things I am recommending for change follow: *Antivirus protection on the Exchange server - (DOH! -no we don't have it!) Would appreciate you suggestions/experience - I am looking at Sybari Antigen *Disabling OWA - only two people of 35 used it Good idea or not...? *Backup server A minimum configured backup server for rapid switch *Recommending against outsourced management of EX Looking for horror stories Thank you for your help. I am searching archives, but as you may know the good nature OT conversation proves a little thick to dig through. Paul _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Report of MS Exchange disaster
Thank you for your input, please keep them coming. Spoke with Kevin Laprelle at Sybari - did a real good job and I am more inclined than before with Sybari. Waiting to hear from Trend Micro...(good / bad) Another thought I have had, is what about education? I have figured that I should educate myself (i.e. classes, books and certs) and have done some of these, but I have never approached management about this. In this report I am trying to suggest it is in their best interest - and stop shafting myself to benefit them. What do you think? Paul -Original Message- From: Soysal, Serdar [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 10:59 AM To: Exchange Discussions Subject: RE: Report of MS Exchange disaster *Antivirus: You're on good track. *OWA: If they need it, let'em have it. Great for access from home, or roaming users. And yes, put it on a separate box. *Backup: Use NTBACKUP for now. It'll work just fine. When you actually migrate the 15000+ users to Exchange, you may want to look at other units/sw that can provide you more features (if you need them that is). BackupExec or CommVault is what you'd want. *Outsourcing: Do you really want Hanjish people running your Exchange? S. -Original Message- From: Paul Done [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 12:09 PM To: Exchange Discussions Subject: Report of MS Exchange disaster Hello All! I am writing a report to management about a disater we had on our Microsoft exchange server a couple of weeks ago. I am hoping you might provide me with horror stories and/or best practice in your shops. My operation is small (=35) but would like to show success. If so we (15000+) may move off a 10 year old featureless UNIX. Among many things I am recommending for change follow: *Antivirus protection on the Exchange server - (DOH! -no we don't have it!) Would appreciate you suggestions/experience - I am looking at Sybari Antigen *Disabling OWA - only two people of 35 used it Good idea or not...? *Backup server A minimum configured backup server for rapid switch *Recommending against outsourced management of EX Looking for horror stories Thank you for your help. I am searching archives, but as you may know the good nature OT conversation proves a little thick to dig through. Paul _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Report of MS Exchange disaster
Glad you're enjoying the view up there, Doug! I kind of enjoy your soapbox rants! If you can see my point [1], could you please tell me what it might have been? Mike Morrison NT/SMS/Exchange Administrator Ben Jerry's Homemade, Inc. [1] And not the one on top of my head! -Original Message- From: Doug Hampshire [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 4:15 PM To: Exchange Discussions Subject: RE: Report of MS Exchange disaster * AV- there are several great solutions with the top being Trend ScanMail and Sybari. (I prefer Trend, but YMMV). According to DBP [1], you should run local AV as well on your Exchange server. Of course local AV needs to be correctly configured to not scan the important Exchange stuff. * OWA - It depends. If the 2 people are the CEO and the CIO, then you might want to continue supporting it. Bottom line, OWA deployment is based on business requirements, not raw numbers. * Minimum backup - NT Backup on the Exchange server to a insert tape unit of choice attached to the Exchange boxen. * Outsourcing - I'm of the old school [3] of keeping business critical processes in house if you have the expertise, time, and resources to support it. I'd be worried that the outsourcing company would be here today/gone tomorrow. And size and revenue have nothing to so with their ability to stay in business. [1] Doug's Best Practices [2] [2] After all, it's all about me :-) [4] [3] Not implying my age [4] Hey Mike, the view from up on my soapbox is really good today. I can almost see your point from up here. [5] [5] I crack myself up [6] [6] Hi Sherry [7] [7] Apologies for not saying hi in so long. -Original Message- From: Paul Done [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 9:09 AM To: Exchange Discussions Subject: Report of MS Exchange disaster Hello All! I am writing a report to management about a disater we had on our Microsoft exchange server a couple of weeks ago. I am hoping you might provide me with horror stories and/or best practice in your shops. My operation is small (=35) but would like to show success. If so we (15000+) may move off a 10 year old featureless UNIX. Among many things I am recommending for change follow: *Antivirus protection on the Exchange server - (DOH! -no we don't have it!) Would appreciate you suggestions/experience - I am looking at Sybari Antigen *Disabling OWA - only two people of 35 used it Good idea or not...? *Backup server A minimum configured backup server for rapid switch *Recommending against outsourced management of EX Looking for horror stories Thank you for your help. I am searching archives, but as you may know the good nature OT conversation proves a little thick to dig through. Paul _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Report of MS Exchange disaster
I believe that your point was that you were going to send me some Pint Coupons. It was a very good point. -Original Message- From: Mike Morrison [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 1:29 PM To: Exchange Discussions Subject: RE: Report of MS Exchange disaster Glad you're enjoying the view up there, Doug! I kind of enjoy your soapbox rants! If you can see my point [1], could you please tell me what it might have been? Mike Morrison NT/SMS/Exchange Administrator Ben Jerry's Homemade, Inc. [1] And not the one on top of my head! -Original Message- From: Doug Hampshire [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 4:15 PM To: Exchange Discussions Subject: RE: Report of MS Exchange disaster * AV- there are several great solutions with the top being Trend ScanMail and Sybari. (I prefer Trend, but YMMV). According to DBP [1], you should run local AV as well on your Exchange server. Of course local AV needs to be correctly configured to not scan the important Exchange stuff. * OWA - It depends. If the 2 people are the CEO and the CIO, then you might want to continue supporting it. Bottom line, OWA deployment is based on business requirements, not raw numbers. * Minimum backup - NT Backup on the Exchange server to a insert tape unit of choice attached to the Exchange boxen. * Outsourcing - I'm of the old school [3] of keeping business critical processes in house if you have the expertise, time, and resources to support it. I'd be worried that the outsourcing company would be here today/gone tomorrow. And size and revenue have nothing to so with their ability to stay in business. [1] Doug's Best Practices [2] [2] After all, it's all about me :-) [4] [3] Not implying my age [4] Hey Mike, the view from up on my soapbox is really good today. I can almost see your point from up here. [5] [5] I crack myself up [6] [6] Hi Sherry [7] [7] Apologies for not saying hi in so long. -Original Message- From: Paul Done [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 9:09 AM To: Exchange Discussions Subject: Report of MS Exchange disaster Hello All! I am writing a report to management about a disater we had on our Microsoft exchange server a couple of weeks ago. I am hoping you might provide me with horror stories and/or best practice in your shops. My operation is small (=35) but would like to show success. If so we (15000+) may move off a 10 year old featureless UNIX. Among many things I am recommending for change follow: *Antivirus protection on the Exchange server - (DOH! -no we don't have it!) Would appreciate you suggestions/experience - I am looking at Sybari Antigen *Disabling OWA - only two people of 35 used it Good idea or not...? *Backup server A minimum configured backup server for rapid switch *Recommending against outsourced management of EX Looking for horror stories Thank you for your help. I am searching archives, but as you may know the good nature OT conversation proves a little thick to dig through. Paul _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Report of MS Exchange disaster
Oh... that point! I'll get right on it. Mike Morrison NT/SMS/Exchange Administrator Ben Jerry's Homemade, Inc. -Original Message- From: Doug Hampshire [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 4:30 PM To: Exchange Discussions Subject: RE: Report of MS Exchange disaster I believe that your point was that you were going to send me some Pint Coupons. It was a very good point. -Original Message- From: Mike Morrison [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 1:29 PM To: Exchange Discussions Subject: RE: Report of MS Exchange disaster Glad you're enjoying the view up there, Doug! I kind of enjoy your soapbox rants! If you can see my point [1], could you please tell me what it might have been? Mike Morrison NT/SMS/Exchange Administrator Ben Jerry's Homemade, Inc. [1] And not the one on top of my head! -Original Message- From: Doug Hampshire [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 4:15 PM To: Exchange Discussions Subject: RE: Report of MS Exchange disaster * AV- there are several great solutions with the top being Trend ScanMail and Sybari. (I prefer Trend, but YMMV). According to DBP [1], you should run local AV as well on your Exchange server. Of course local AV needs to be correctly configured to not scan the important Exchange stuff. * OWA - It depends. If the 2 people are the CEO and the CIO, then you might want to continue supporting it. Bottom line, OWA deployment is based on business requirements, not raw numbers. * Minimum backup - NT Backup on the Exchange server to a insert tape unit of choice attached to the Exchange boxen. * Outsourcing - I'm of the old school [3] of keeping business critical processes in house if you have the expertise, time, and resources to support it. I'd be worried that the outsourcing company would be here today/gone tomorrow. And size and revenue have nothing to so with their ability to stay in business. [1] Doug's Best Practices [2] [2] After all, it's all about me :-) [4] [3] Not implying my age [4] Hey Mike, the view from up on my soapbox is really good today. I can almost see your point from up here. [5] [5] I crack myself up [6] [6] Hi Sherry [7] [7] Apologies for not saying hi in so long. -Original Message- From: Paul Done [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 9:09 AM To: Exchange Discussions Subject: Report of MS Exchange disaster Hello All! I am writing a report to management about a disater we had on our Microsoft exchange server a couple of weeks ago. I am hoping you might provide me with horror stories and/or best practice in your shops. My operation is small (=35) but would like to show success. If so we (15000+) may move off a 10 year old featureless UNIX. Among many things I am recommending for change follow: *Antivirus protection on the Exchange server - (DOH! -no we don't have it!) Would appreciate you suggestions/experience - I am looking at Sybari Antigen *Disabling OWA - only two people of 35 used it Good idea or not...? *Backup server A minimum configured backup server for rapid switch *Recommending against outsourced management of EX Looking for horror stories Thank you for your help. I am searching archives, but as you may know the good nature OT conversation proves a little thick to dig through. Paul _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED]
RE: Report of MS Exchange disaster
Don't forget my preggers wife who has a BJ addiction right now. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Morrison Sent: Wednesday, October 24, 2001 1:33 PM To: Exchange Discussions Subject: RE: Report of MS Exchange disaster Oh... that point! I'll get right on it. Mike Morrison NT/SMS/Exchange Administrator Ben Jerry's Homemade, Inc. -Original Message- From: Doug Hampshire [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 4:30 PM To: Exchange Discussions Subject: RE: Report of MS Exchange disaster I believe that your point was that you were going to send me some Pint Coupons. It was a very good point. -Original Message- From: Mike Morrison [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 1:29 PM To: Exchange Discussions Subject: RE: Report of MS Exchange disaster Glad you're enjoying the view up there, Doug! I kind of enjoy your soapbox rants! If you can see my point [1], could you please tell me what it might have been? Mike Morrison NT/SMS/Exchange Administrator Ben Jerry's Homemade, Inc. [1] And not the one on top of my head! -Original Message- From: Doug Hampshire [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 4:15 PM To: Exchange Discussions Subject: RE: Report of MS Exchange disaster * AV- there are several great solutions with the top being Trend ScanMail and Sybari. (I prefer Trend, but YMMV). According to DBP [1], you should run local AV as well on your Exchange server. Of course local AV needs to be correctly configured to not scan the important Exchange stuff. * OWA - It depends. If the 2 people are the CEO and the CIO, then you might want to continue supporting it. Bottom line, OWA deployment is based on business requirements, not raw numbers. * Minimum backup - NT Backup on the Exchange server to a insert tape unit of choice attached to the Exchange boxen. * Outsourcing - I'm of the old school [3] of keeping business critical processes in house if you have the expertise, time, and resources to support it. I'd be worried that the outsourcing company would be here today/gone tomorrow. And size and revenue have nothing to so with their ability to stay in business. [1] Doug's Best Practices [2] [2] After all, it's all about me :-) [4] [3] Not implying my age [4] Hey Mike, the view from up on my soapbox is really good today. I can almost see your point from up here. [5] [5] I crack myself up [6] [6] Hi Sherry [7] [7] Apologies for not saying hi in so long. -Original Message- From: Paul Done [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 9:09 AM To: Exchange Discussions Subject: Report of MS Exchange disaster Hello All! I am writing a report to management about a disater we had on our Microsoft exchange server a couple of weeks ago. I am hoping you might provide me with horror stories and/or best practice in your shops. My operation is small (=35) but would like to show success. If so we (15000+) may move off a 10 year old featureless UNIX. Among many things I am recommending for change follow: *Antivirus protection on the Exchange server - (DOH! -no we don't have it!) Would appreciate you suggestions/experience - I am looking at Sybari Antigen *Disabling OWA - only two people of 35 used it Good idea or not...? *Backup server A minimum configured backup server for rapid switch *Recommending against outsourced management of EX Looking for horror stories Thank you for your help. I am searching archives, but as you may know the good nature OT conversation proves a little thick to dig through. Paul _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com
RE: Report of MS Exchange disaster
Mike, How 'bout a round of pints for everyone? [1] I am more inclined to self-taught. So the books are the way to still - I think. Need to find one of Paul Robichaux's books, apparently this is the Exchange Bible. Happy to say just got my first minion today - we'll see how it works out as soon as I find a way to shoehorn him in my office (closet). Thank you everyone, report is complete and going off to proof and management. Paul [1] Here I go adding to the fluff that makes the archive hard to search for valid info [2] [2] I like this footnote idea [3] [3] It is contagious and could go on forever -Original Message- From: Mike Morrison [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 1:33 PM To: Exchange Discussions Subject: RE: Report of MS Exchange disaster Oh... that point! I'll get right on it. Mike Morrison NT/SMS/Exchange Administrator Ben Jerry's Homemade, Inc. -Original Message- From: Doug Hampshire [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 4:30 PM To: Exchange Discussions Subject: RE: Report of MS Exchange disaster I believe that your point was that you were going to send me some Pint Coupons. It was a very good point. -Original Message- From: Mike Morrison [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 1:29 PM To: Exchange Discussions Subject: RE: Report of MS Exchange disaster Glad you're enjoying the view up there, Doug! I kind of enjoy your soapbox rants! If you can see my point [1], could you please tell me what it might have been? Mike Morrison NT/SMS/Exchange Administrator Ben Jerry's Homemade, Inc. [1] And not the one on top of my head! -Original Message- From: Doug Hampshire [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 4:15 PM To: Exchange Discussions Subject: RE: Report of MS Exchange disaster * AV- there are several great solutions with the top being Trend ScanMail and Sybari. (I prefer Trend, but YMMV). According to DBP [1], you should run local AV as well on your Exchange server. Of course local AV needs to be correctly configured to not scan the important Exchange stuff. * OWA - It depends. If the 2 people are the CEO and the CIO, then you might want to continue supporting it. Bottom line, OWA deployment is based on business requirements, not raw numbers. * Minimum backup - NT Backup on the Exchange server to a insert tape unit of choice attached to the Exchange boxen. * Outsourcing - I'm of the old school [3] of keeping business critical processes in house if you have the expertise, time, and resources to support it. I'd be worried that the outsourcing company would be here today/gone tomorrow. And size and revenue have nothing to so with their ability to stay in business. [1] Doug's Best Practices [2] [2] After all, it's all about me :-) [4] [3] Not implying my age [4] Hey Mike, the view from up on my soapbox is really good today. I can almost see your point from up here. [5] [5] I crack myself up [6] [6] Hi Sherry [7] [7] Apologies for not saying hi in so long. -Original Message- From: Paul Done [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 24, 2001 9:09 AM To: Exchange Discussions Subject: Report of MS Exchange disaster Hello All! I am writing a report to management about a disater we had on our Microsoft exchange server a couple of weeks ago. I am hoping you might provide me with horror stories and/or best practice in your shops. My operation is small (=35) but would like to show success. If so we (15000+) may move off a 10 year old featureless UNIX. Among many things I am recommending for change follow: *Antivirus protection on the Exchange server - (DOH! -no we don't have it!) Would appreciate you suggestions/experience - I am looking at Sybari Antigen *Disabling OWA - only two people of 35 used it Good idea or not...? *Backup server A minimum configured backup server for rapid switch *Recommending against outsourced management of EX Looking for horror stories Thank you for your help. I am searching archives, but as you may know the good nature OT conversation proves a little thick to dig through. Paul _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin:[EMAIL PROTECTED] _ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange
