A book by you on this would sell. I want it to keep going. You should do weekly installments on the history of Microsoft Messaging platforms.
Nathan > -----Original Message----- > From: Dupler, Craig [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, November 13, 2001 1:33 PM > To: Exchange Discussions > Subject: RE: Hi > > > Ok (and for Darcy too). > > So let's talk about the Outlook Disaster first, since that > has a lot of old > time stuff and it is a perfect segue into the problems we face keeping > Exchange moving forward. > > So everyone knows the Exchange architecture at the 80,000 > foot level, right? > There is a store, rules engine, and an MTA on the server, > with a bunch of > services connectors. The GAL is now a redirector to the AD. > On the client > side you have a MAPI services layer that is a part of WOSA > and can support > any U/I or client for things like messaging, calendar and > directory - yes? > Ok, back in the beginning, the Exchange team built all of > these pieces. > Every last one of them, and was trying to keep them architecturally > consistent. They did some things better than others. One of > the teams weak > points was in extending the core services with tools for > doing workgroup > stuff. They/we understood that we didn't want to copy Notes with its > relatively closed view of the world (think Notes documents). Somehow > Exchange needed to make it possible for Office and really any > application to > work well in a collaborative way. > > Ok, knowing that and doing it are two different things. The > Exchange team > had its hands full and was not doing all that great with its workgroup > tools. There was an EDK (Exchange development kit), but it > was not very > well developed. Ok, David Goodhand (did I spell that right?) > anyway, David > was really sharp about what needed to happen, but he got his > funding from > the Office crew. So, totally independently from the Exchange > team, David > got the funding to develop a whole new client system - Outlook. As a > messaging tool it was a piece of crap, and quite poor relative to the > Exchange client (Capone), but as a workgroup tool it was night and day > better. But the real problem was Microsoft was not working > as a team. They > were quite viciously competing with themselves. It got so > bad that only two > weeks after Exchange 4.0 went RTM, the Office group released > a press story > titled "Microsoft Gets a Whole New Outlook" and started with > words to the > effect that 'Microsoft was dumping Exchange and replacing it > with Outlook . > . .' It was a PR disaster of course, because nobody outside > of the Exchange > developers and beta testers understood that Exchange the > server and Exchange > the client were two different things and that the client was > two things and > that MAPI and Exchange server were not going any place. > Plus, you had the > Capone team that felt like they had been stabbed in the back > by their own > company, which they had. Well, over the months that > followed, we gradually > picked up the pieces and went on. > > The story is worth telling because the underlying > organizational and vision > management problems that led to the Outlook Disaster still > persist. Who can > concisely describe Microsoft's strategy for the following" > - messaging > - telephony > - high mobility platforms > - embedded appliance servers > > There are others, but these four serve to make the point. In > quite a few > key areas Microsoft has multiple and inherently conflicted > strategies, and > some of the ones that they like the best are in deep denial > with long term > technical trends. Bill and Steve have built a culture that depends on > vigorous internal competition. Some of it is healthy and > some of it isn't. > Certainly their famous sense of paranoia has kept them ahead > of most of > their competitors. But, it also has created a situation in which key > decisions sometimes get made based on who has the most > political clout or > who shouts the loudest. This makes them just as susceptible > the Christensen > problem (read "The Innovator's Dilemma" by Clayton > Christensen) as anyone > else. > > Microsoft has several serious problems relative to Exchange, > and most of > them have been there since the beginning. They portable > calendar solution > is terrible. Pegasus (the HPC 1.0 version of the CE > platform) shipped in > 1996 eight months after Exchange. It's their mobile personal > calendar for > enterprise customers - right? Ok, so why is it that it can't > synch directly > to the store, even today, five years later? > > NetMeeting 1.0 shipped way back then as well. So why can't their CE > platforms talk to it? The directory team left the Exchange > team and joined > the NT group to build the AD in 1996. So why is the > NetMeeting ILS still > not integrated? DEN/CIM was proposed with Cisco in 1997, so > why can't a > MAPI client do a directory lookup on the MAC address of the > last device > someone used for a NetMeeting session, or an Exchange > session? Why isn't > the data storable in a meaningful way in one of the "tools" > menus in Outlook > and OWA (stored in the store of course) (think of them as an > attribute page > of "devices in my life")? Why can't the rules engine write messaging > handling, call forwarding and event notifications based on > these objects? > [Cisco's Unity can do some of these things.] > > These guys are drifting and nearly visionless, and well that > comes close to > being clueless. It didn't used to be that way. There once > was a time when > the Exchange architects were some of the most forward looking > visionaries > you could find - any place. > > Now to be fair, some parts of Microsoft are firing on all > cylinders. I have > great hopes for some things I've seen in the PocketPC team in > the past year. > The CE core team may (stress the word MAY) have just figured > out that data > sharing in multimedia telephony is more important than video in the > enterprise space, which is their core customer set (Palm is > still cleaning > their clock in the regular retail channel). > > Gee, I could go on like this for awhile, but I think you get > the point. If > Exchange keeps drifting, it will get knocked off. Remember > when OV was king > of the hill, and All-In-1 had a promising future? > > -----Original Message----- > From: Drewski [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, November 13, 2001 10:49 AM > To: Exchange Discussions > Subject: RE: Hi > > > yes. The Outlook Disaster specifically, but also the > "keeping Exchange > moving > forward" stuff as well... > > -- Drew > ******************************** > Visit http://www.drewncapris.net! Go! Go there now! > No mention shall be made of coral or of crystal; the price of > wisdom is > above > pearls. - Job 28:18 > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Dupler, Craig > Sent: Tuesday, November 13, 2001 12:40 PM > To: Exchange Discussions > Subject: RE: Hi > > > You mean about old times, or the Outlook disaster and why it's still a > problem, or what? > > -----Original Message----- > From: Drewski [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, November 13, 2001 10:06 AM > To: Exchange Discussions > Subject: RE: Hi > > > I, for one, would love to hear more about this. > > -- Drew > ******************************** > Visit http://www.drewncapris.net! Go! Go there now! > "Don't join the book burners. Don't think you are going to > conceal thoughts > by > concealing evidence that they ever existed." -- Dwight D. Eisenhower > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Dupler, Craig > Sent: Tuesday, November 13, 2001 11:58 AM > To: Exchange Discussions > Subject: RE: Hi > > > Austin was the last one I attended. But before that one, > there was the MEC > in Bellevue at Meydenbauer Center, and there was an Exchange > Deployment > Conference at the Seattle Convention and Trade Center. That > one was the > official transition from the Microsoft Mail Conference, which > I think had > its last big bash in Portland. Anyway, I made presentations > at Seattle and > Bellevue, and was on a panel at Austin. > > The thing I remember most about Austin was the Breavehearts > dinner where > Elaine, Eric and Brian told us what we and they were up > against in terms of > keeping Exchange moving forward. Also, the politics of the > Outlook disaster > were revealed. It was a real eye opener. > > > > -----Original Message----- > From: Darcy Adams [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, November 13, 2001 9:11 AM > To: Exchange Discussions > Subject: RE: Hi > > > I was at that one! Then absent until this year. > > Craig actually dragged me into this whole Exchange biz. . . > > Darcy > > -----Original Message----- > From: Ed Crowley [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 12, 2001 9:19 PM > To: Exchange Discussions > Subject: RE: Hi > > > It's funny you bring this up. At MEC, I was thinking back to > Austin (the > original Exchange Deployment Conference, MEC 1 if you will, > way back before > Orlando, Dallas, Atlanta, Boston and San Diego) and I > realized that I've > been working this technology for well over five years. I > KNOW you've been > at it even longer. > > Ed Crowley MCSE+I MVP > Tech Consultant > Compaq Computer > "There are seldom good technological solutions to behavioral > problems." > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Dupler, Craig > Sent: Monday, November 12, 2001 3:59 PM > To: Exchange Discussions > Subject: RE: Hi > > > Wasn't Peter subsidized by his company at the time? For some > reason I'm > thinking it was ASL, but I may be confusing that with another > UK firm. In > any case, I'm thinking that it was sometime around December > 1, 1995 that > Peter went live. > > The Bravehearts group was pre-web, pre list server. It > mainly existed in > the form of a weekly telecon and a forum on Compuserve. > > -----Original Message----- > From: Daniel Chenault [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 12, 2001 1:27 PM > To: Exchange Discussions > Subject: Re: Hi > > > Peter Bowyer > > ----- Original Message ----- > From: "John Matteson" <[EMAIL PROTECTED]> > To: "Exchange Discussions" <[EMAIL PROTECTED]> > Sent: Monday, November 12, 2001 1:58 PM > Subject: RE: Hi > > > > Yes to Bravehearts and No to Elaine. > > > > Another old timer question, Who was the original Sponser of > the Exchange > > list? > > > > John Matteson; Exchange Manager > > Geac Corporate Infrastructure Systems and Standards > > (404) 239 - 2981 > > > > ...the words that I remember from my childhood still are > true, that there > > are none so blind as those who will not see.... > > --The Moody Blues (I know you're out there) > > > > > > > > -----Original Message----- > > From: Dupler, Craig [mailto:[EMAIL PROTECTED]] > > Sent: Friday, November 09, 2001 4:19 PM > > To: Exchange Discussions > > Subject: Hi > > > > > > Is anyone left here that remembers what "Bravehearts" meant? > > > > > > > > > > _________________________________________________________________ > > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > > Archives: http://www.swynk.com/sitesearch/search.asp > > To unsubscribe: mailto:[EMAIL PROTECTED] > > Exchange List admin: [EMAIL PROTECTED] > > > > _________________________________________________________________ > > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > > Archives: http://www.swynk.com/sitesearch/search.asp > > To unsubscribe: mailto:[EMAIL PROTECTED] > > Exchange List admin: [EMAIL PROTECTED] > > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
