Ewww, I'm not sure which was worse 4.0 or 5.0. 4.0 was a god send going from MS Mail. 5.0 was a disaster from a version upgrade standpoint... 5.5was what 5.0 "should" have been...
On Fri, Feb 29, 2008 at 1:11 PM, Michael B. Smith < [EMAIL PROTECTED]> wrote: > You are a real old-timer! I've only been using Exchange since 5.0. > > > > In that time, since 1996, I've had to use repair + isinteg 3 times. I can > remember the nightmares. Two were related to hard disk failures when the > company was doing only mailbox backups. The third was due to a failed SBS 4 > to SBS 2000 upgrade. I've probably seen a true need to do a defrag 10 times > in those 12 years. This covers my consluting to literally hundreds of > customers. > > > > Regards, > > > > Michael B. Smith > > MCSE/Exchange MVP > > http://TheEssentialExchange.com <http://theessentialexchange.com/> > > > > *From:* Don Ely [mailto:[EMAIL PROTECTED] > *Sent:* Friday, February 29, 2008 3:58 PM > *To:* NT System Admin Issues > *Subject:* Re: Response from GoExchange, Lucid8 Support > > > > Your product is useless to "real" Exchange admins. Your product offers no > intrinsic value and at best your product increases the risk of making things > worse... > > > > Bottom line, your product holds no value. > > > > I know enough about your product to make such a broad statement. > > > > Given that, maybe you can explain where I am wrong in my assumption about > your product. Having managed Exchange environments since the Exchange > 4.0days I'm pretty sure I have a strong handle on the Jet Database, Eseutil, > and Isinteg. I also have a keen handle on when to use these utilities and > when I shouldn't. I can also say that in all of my years of managing > Exchange and we're going on 13 years, I have never run Eseutil or Isinteg on > servers I had to manage. I can count on both hands the number of times I > have to use either utility as a conslutant. > > > > All of that said, where would I find value in your product. Seriously, I > would really like to know the answer to this question and without use case > scenario's, etc... I would like clear, techincal reasons to implement such > a product. > > On Fri, Feb 29, 2008 at 12:12 PM, Dane Cue <[EMAIL PROTECTED]> wrote: > > WL, I read your post and; > > 1. Your snide comments really hold no value. > > Q: I have to ask myself and so should others why anyone would make such a > silly suggestion for an Anti-Product that they in fact know nothing about? > > A: If you dont hae an answer, make an off color comment, wave your arms > and jump up and down. Ooh look at me everyone, the world is flat i tell you > flat.... > > > 2. Regarding your statement about Microsofts, you seem to be arguing > against yourself, i.e. no one from MS would ever say this and if they did > its a rogue party with an MS email? So even if I were at liberty to qoute > MS sources you would more then likely call the person an idiot or something > else degrading. > > Also you fail to miss the major point of our rather detailed answer: Here > is the orginal text: > > A final note. We have heard from Microsoft themselves which have stated on > various occasions (to us and other customers) > • "With 2K7 you don't need GOexchange anymore like you did with 2K3" > • Rather humorously we also previously heard "With 2K3 you don't > need GOexchange anymore like you did with 2K" > in other words with every generation of Exchange it's admitted we provided > a valuable service for the older product but we were no longer "Needed" for > the newest product, that is until the next generation is released that > solves all the problems that didn't exist. > > END.. > > Now MS is a great company that makes some incredible products, but anyone > that has been in the industry for any length of time knows the scopre here > and its not just about Exchange i.e. > > Buy Version 1.x its awesome and has no issues > > Buy Version 2.x its awesome and solves issues that 1.x had and is solid as > a rock, requires no xxx or yyy like 1.x > > Buy version 3.x its awesome, solves issues with 2.x and is solid as a > rock, requires no xxx or yyy or zzz like 2.x > > So the latest version is always great and solves real problems that the > old version had and therefore you no longer need to do whatever you used to > do, until the new version comes out and then the process is repeated. > > In relation to GOexchange, MS and others made these statements when > Exchange 2000 came out, then 2003 and now 2007 and each and every time its > been false, i.e. GOexchange continues to add value to clients around the > world. Bottom line here is that until MS move's away from JET, GOexchange > will continue to provide benefit to all that utilize it. > > I hope this helps and I am happy to converse with you openly on this forum > as long as you can behave like a professional and deliver thoughtful and > informed responses. > > DC > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > > > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
