"But it worked before!"
May. 19th, 2006 04:20 pmOnly two phrases make the hair on the back of my neck stand on end (which is especially hard since I shave my head to the scalp). For the record, the other phrase is "Your ex wife is on the phone."
Raise your hand; how many people know what happens (or can happen, I should say) if an antivirus product starts attempting to yank data out of an Exchange log file? You are quite possibly looking at reinstalling Exchange, or at best restoring from a backup.
----
Me: What has happened is that [file-level scanner] detected a virus or code that resembles a virus and attempted to clean it as per its configuration; therefore, that log file is now corrupt. You should have had exclusions in place to keep [file-level scanner] out of Exchange's business.1
Exchange Adminis-traitor: WHAT?! Oh GREAT. What the hell are you going to do about it?
Me: ... From here there isn't anything I can do; if you have a backup you c...
EA: How did this happen after two years?! It has worked fine that whole time!2
Me: There are errors going back several days.3 If you haven't had those in place for two years, you've honestly been very lucky.
EA: So how come this doesn't happen to everyone?! Explain THAT.
Me: Most people put the proper exclusions in place from the offset since they are well documented.4 Not everyone's -- or really anyone's -- Exchange configuration, logs, store and what have you are identical.
EA: But it worked before!
----
Listen, jerk-off. I don't give a rat's left testicle if it "worked before." It's not working now, nor will it ever work again lest ye shut the fuck up. Here's an analogy for your dumb ass:
You have worked at the same company for two years. The restrooms are right next to one another; Women's room on the left, Men's room on the right. You've never questioned why the Men's room had no urinals; you just assumed that it was the status quo2 and went about your business (no pun intended).
One day the company recognizes its oversight after a woman finally brings up the fact that the urinals in the Women's room shouldn't be in there.1 Realizing that the signs were just switched, the company swaps them so the restrooms are as they should be. They send an urgent bulletin to everyone about the change.4 You don't bother reading it -- because hey, you're YOU -- and you get up, walk into the restroom and whip it out. Next thing you know, security is escorting you out and Suzy from Acquisitions is snickering to her friends about how terribly bored your wife must be. All this because you can't be arsed to pay attention to the signs.3 It worked before, right?
Assdolphin.
Raise your hand; how many people know what happens (or can happen, I should say) if an antivirus product starts attempting to yank data out of an Exchange log file? You are quite possibly looking at reinstalling Exchange, or at best restoring from a backup.
----
Me: What has happened is that [file-level scanner] detected a virus or code that resembles a virus and attempted to clean it as per its configuration; therefore, that log file is now corrupt. You should have had exclusions in place to keep [file-level scanner] out of Exchange's business.1
Exchange Adminis-traitor: WHAT?! Oh GREAT. What the hell are you going to do about it?
Me: ... From here there isn't anything I can do; if you have a backup you c...
EA: How did this happen after two years?! It has worked fine that whole time!2
Me: There are errors going back several days.3 If you haven't had those in place for two years, you've honestly been very lucky.
EA: So how come this doesn't happen to everyone?! Explain THAT.
Me: Most people put the proper exclusions in place from the offset since they are well documented.4 Not everyone's -- or really anyone's -- Exchange configuration, logs, store and what have you are identical.
EA: But it worked before!
----
Listen, jerk-off. I don't give a rat's left testicle if it "worked before." It's not working now, nor will it ever work again lest ye shut the fuck up. Here's an analogy for your dumb ass:
You have worked at the same company for two years. The restrooms are right next to one another; Women's room on the left, Men's room on the right. You've never questioned why the Men's room had no urinals; you just assumed that it was the status quo2 and went about your business (no pun intended).
One day the company recognizes its oversight after a woman finally brings up the fact that the urinals in the Women's room shouldn't be in there.1 Realizing that the signs were just switched, the company swaps them so the restrooms are as they should be. They send an urgent bulletin to everyone about the change.4 You don't bother reading it -- because hey, you're YOU -- and you get up, walk into the restroom and whip it out. Next thing you know, security is escorting you out and Suzy from Acquisitions is snickering to her friends about how terribly bored your wife must be. All this because you can't be arsed to pay attention to the signs.3 It worked before, right?
Assdolphin.
no subject
Date: 2006-05-19 10:36 pm (UTC)no subject
Date: 2006-05-19 11:16 pm (UTC)O.o
no subject
Date: 2006-05-19 11:29 pm (UTC)Assmonkey
Asskangaroo
Assplatypus
Assbeetle
no subject
Date: 2006-05-20 12:42 am (UTC)no subject
Date: 2006-05-20 01:46 am (UTC)no subject
Date: 2006-05-20 03:52 am (UTC)no subject
Date: 2006-05-20 04:00 am (UTC)And, by the way, the database isn't a single monolithic file; you've got the MAPI database and the "all others" database.
If you really have 100gigs of mail storage, then buy the Enterprise Edition. It doesn't cost THAT much more.
no subject
Date: 2006-05-20 04:01 am (UTC)no subject
Date: 2006-05-20 05:22 am (UTC)If you have a 100-gig mail store then a) you need what is talked about below, b) your mail storage policies are clearly too lax, c) your users are stupid, d) I hear NAS devices are all the rage this season, and e) Exmerge is your friend.
no subject
Date: 2006-05-20 05:26 am (UTC)...perhaps not.
no subject
Date: 2006-05-20 05:43 am (UTC)no subject
Date: 2006-05-20 12:09 pm (UTC)no subject
Date: 2006-05-20 12:17 pm (UTC)no subject
Date: 2006-05-20 12:35 pm (UTC)no subject
Date: 2006-05-21 03:22 pm (UTC)no subject
Date: 2006-05-21 04:22 pm (UTC)no subject
Date: 2006-05-22 05:59 pm (UTC)