I was on the McAfee tech support line back then... It was SO nice when your users had half a clue...(getting a modem up an running, downloading a file, downloading PKzip, and then unzipping the app all took at least half a clue back then)
Then they started selling it in stores... I still have nightmares...
Minnesota Public Radio's "The Story" show with Dick Gordon did a piece on Mohamed Fikry, an almost 5 million mile customer with American Airlines... and they pulled the SAME CRAP. Twice! Once because a customer heard him speaking "a foreign language on the phone" (it was Spanish) and once because a flight attendant thought she'd seen him "backstage".
5 Million Miles! with the same airline... And to top it off, they had the FBI pull him from the plane AFTER they flew to the destination! If he were such a threat, why let him fly at ALL... Gotta love airline customer service.
Link to the story http://thestory.org/archive/the_story_669_Business_Class_Terrorist.mp3/view
Create a "stand alone root", NOT a domain root, on a server. Then add links to it, where they point to shares on workstations.
This acts more like a bunch of symbolic links to the various boxes, with one entry point the the share. Not the same data everywhere, like a domain root would be.
It depends on the implementation (and possibly the raid level). Some raid cards will let you expand the container after you've replaced all of the drives with new ones of a larger size. Then you have to expand the partition, or put another partition into the new space. I've done this with Compaq hardware running Win2k in a RAID 1 (mirrored pair).
The "Raid 5 can't do what I heard" isn't quite what's going on, again, depending on the implementation. Most raid cards I've used allow you to add drives to the array and expand the array to the new drive(s) without downing the server or requiring a rebuild.
~1200 users 100 meg standard limit. Some users have more. 25 meg transfer limit keep deleted email 7 days, purged mailbox 30 days
Keep the stores at 35 gig or smaller for a 4 hr recovery window... We put that on a 40 gig lun. If you lose the partition you only lose the one store.
If you're using Veritas Netbackup, seperate all of your store backups into seperate jobs or you have to read through many more gigs of data to get 1 store back, and then do it again if you've lost more than one store.
Multi gig mailboxes are stupid. Exchange is NOT a filestore!
Some businesses are required, by law, to have email reviewed. Specifically, stock brokerages can not accept buy or sell orders over email, can't publish certain types of recommendations electronically, etc. To insure this doesn't happen mail to and from brokers has to be monitored by the Compliance dept of the brokerage. Also all of that mail must be archived for three years. We have the SEC to thank for that. We are implementing a system to do this now, and yes HR is pushing to be able to scan mail for violations of the policy. We (IS) are not involved in anything more than insuring the technology of the system works. You should limit yourself to that as well. Ken
Slashdot Mirror
I was on the McAfee tech support line back then... It was SO nice when your users had half a clue...(getting a modem up an running, downloading a file, downloading PKzip, and then unzipping the app all took at least half a clue back then)
Then they started selling it in stores... I still have nightmares...
Minnesota Public Radio's "The Story" show with Dick Gordon did a piece on Mohamed Fikry, an almost 5 million mile customer with American Airlines... and they pulled the SAME CRAP. Twice! Once because a customer heard him speaking "a foreign language on the phone" (it was Spanish) and once because a flight attendant thought she'd seen him "backstage". 5 Million Miles! with the same airline... And to top it off, they had the FBI pull him from the plane AFTER they flew to the destination! If he were such a threat, why let him fly at ALL... Gotta love airline customer service. Link to the story http://thestory.org/archive/the_story_669_Business_Class_Terrorist.mp3/view
Not a replication DFS, but a namespace DFS.
Create a "stand alone root", NOT a domain root, on a server.
Then add links to it, where they point to shares on workstations.
This acts more like a bunch of symbolic links to the various boxes, with one entry point the the share. Not the same data everywhere, like a domain root would be.
http://www.microsoft.com/windowsserver2003/technologies/storage/dfs/default.mspx
It depends on the implementation (and possibly the raid level). Some raid cards will let you expand the container after you've replaced all of the drives with new ones of a larger size. Then you have to expand the partition, or put another partition into the new space. I've done this with Compaq hardware running Win2k in a RAID 1 (mirrored pair).
The "Raid 5 can't do what I heard" isn't quite what's going on, again, depending on the implementation. Most raid cards I've used allow you to add drives to the array and expand the array to the new drive(s) without downing the server or requiring a rebuild.
So RTFM for the card you're going to use.
Get Shavlik HFNetChkPro. Its free for a year for 50 machines. Scans for all of the MS products, plus Adobe, Winzip, and others...
Shavlik wrote the MS Baseline Security Analyser, the product is solid. www.shavlik.com
No, I don't work for them...
~1200 users
100 meg standard limit. Some users have more.
25 meg transfer limit
keep deleted email 7 days, purged mailbox 30 days
Keep the stores at 35 gig or smaller for a 4 hr recovery window... We put that on a 40 gig lun. If you lose the partition you only lose the one store.
If you're using Veritas Netbackup, seperate all of your store backups into seperate jobs or you have to read through many more gigs of data to get 1 store back, and then do it again if you've lost more than one store.
Multi gig mailboxes are stupid. Exchange is NOT a filestore!
There has been an off and on effort at naming standarization in the past, but its always been an uphill battle.
VGrep from the Virus Bulletin site (www.virusbtn.com) is a continuously updated tool that cross-references the virus names.
Ken
Some businesses are required, by law, to have email reviewed. Specifically, stock brokerages can not accept buy or sell orders over email, can't publish certain types of recommendations electronically, etc. To insure this doesn't happen mail to and from brokers has to be monitored by the Compliance dept of the brokerage. Also all of that mail must be archived for three years. We have the SEC to thank for that. We are implementing a system to do this now, and yes HR is pushing to be able to scan mail for violations of the policy. We (IS) are not involved in anything more than insuring the technology of the system works. You should limit yourself to that as well. Ken