Well, I won't mention the company name, obviously, however, some of the things they have learned/experienced include:
No easy way to lock down a DL to prevent users from e-mailing it. I believe this has to be done as a registry change Something happened in their replication topology, and their DR servers weren't getting new data. Then they fixed that, and ran their DR servers out of space. Then they failed over to their HA node for a hardware issue, and found out their replica copies weren't purging old e-mail, and that is an issue for them for retention policy reasons. -----Original Message----- From: Ben Scott [mailto:[email protected]] Sent: Friday, October 09, 2009 2:28 PM To: NT System Admin Issues Subject: Re: Lotus Notes On Fri, Oct 9, 2009 at 1:19 PM, Wulff Jr, Ronald J. <[email protected]> wrote: > If you want some real world feedback, I can provide some on a major > institution that went from Exchange 2003 to Notes 8.0 and the overall > experience I'd like to hear that story. Many moons ago, I had to deal with some Notes client support for some satellite offices that were customers of mine. I never touched the server stuff. I found client to be, frankly, the worst UI of any major program I've ever used. But my experience is rather dated, so I'm curious what more recent stuff is like. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ * * * This E-mail, along with any attachments, is considered confidential and may well be legally privileged. If you have received it in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Thank you for your cooperation. * * * To ensure compliance with Treasury Department regulations, we inform you that, unless otherwise indicated in writing, any U.S. Federal tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (1) avoiding penalties under the Internal Revenue Code or applicable state and local provisions or (2) promoting, marketing or recommending to another party any tax-related matters addressed herein. Disclaimer Version RS.US.1.01.03 pdc1 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
