I take the time to teach and empower my users, most admins neither make or take the time to do so. I'm sure you've gone on a rant once or twice about how stupid someone was for doing something they know better than to do. I don't think being able to restore any (as in all messages ever sent or received) random message is a requirement for 99.99% of the companies out there. The White House can't even do it (go figure!) If you've never had to restore a mailbox because you've designed around Exchanges limitations then you fully understand that there are shortcomings, as with every other piece of software on the planet. Well done!
John W. Cook Systems Administrator Partnership For Strong Families 315 SE 2nd Ave Gainesville, Fl 32601 Office (352) 393-2741 x320 Cell (352) 215-6944 Fax (352) 393-2746 MCSE, MCTS, MCP+I, A+, N+, VSP4, VTSP4 -----Original Message----- From: Ben Scott [mailto:mailvor...@gmail.com] Sent: Monday, August 17, 2009 11:18 PM To: NT System Admin Issues Subject: Re: Mail server software On Mon, Aug 17, 2009 at 8:45 PM, John Cook <john.c...@pfsf.org> wrote: > If they choose to ignor what I instruct them > to do how is that not stupid? If it's simply a question of not following instructions, perhaps. I may have been taking your comments in broader context than you intended. This discussion is basically about meeting requirements. Calling someone's requirements "stupid" is rarely a good idea. ("Infeasible", perhaps.) Perhaps you didn't intend for your comments to be applied to others. Of course, I wonder why you're sharing your opinion if you don't think it should apply to anyone else... ;-) It's also worth noting that when many people repeatedly "misuse" a system, that's often a sign of poor human-factors engineering. I see this on a daily basis, throughout the world, not just in IT. Bad traffic intersections. Confusing industrial controls. Overly complicated tax forms. Things that work well generally work the way people work. > ... was the last time you had to restore a mailbox? I haven't, so far, knock on wood. But that's largely because I've designed around the limitations of Exchange in that area. Had we had other options, we might well have gone in a different direction, because it was easier/cheaper/faster/etc. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
