I've never been as compelled to defend a piece of software, as I am Outlook 2003 in the context of this piece.
At TechEd in San Diego this year, Steve Ballmer stated something along the lines of, - at first it was all about features, features, features...now it's all about security, security, security....well, they still want features, features, features...
I could sense in him just a hint of well, "anger" - and perhaps the same kind we were feeling, too. A little fatigued - in "The years of retribution" or the years where scientists and IT/MIS Professionals stuck it out after all the irrational behavior that led to the Internet bubble bursting resulted in nearly outrageous demands for "it all" sans any kind of reasonable capital investment or service fees. Mr. Ballmer, as he always does, rebounded quickly and ended the presentation "up." Sort of...That hint was still there; the melancholy opposite an impossible dichotomy of interest.
So now, a bash on Outlook 2003 - by a man blind to among its greatest features and one that addresses both sides of the dichotomy facing all of us - the dual horns of features and security. Well, all the short-comings aside, Outlook 2003 has one huge “feature” that no other email client has – RPC over HTTP(S) – the ability to sustain a full MS MAPI Client Connection using SSL on default port 443 without having to use a VPN, or forced encryption [RPC over TCP] from behind an ISA Server! That is one feature that addresses both pressure for new capabilities and sustained demands for increased security. Easy to configure, on both client and server, once simply establishes the HTTP listener in IIS, applies the SSL certificate and voil’a – full MAPI support that is encrypted for remote, and or mobile users – full Exchange 2003 capabilities without the limitations of the OWA, or costs of VPN clients/switches, etc… We use it all day, every day and even super-encrypt by publishing as one would an SSL website behind ISA. In a stroke, MS not only secured the client, but also the host and host network – moving the Exchange back inside the protected network and out of the DMZ. Seems to me Mr. Ballmer has good reason to be a little melancholy, but also quite up-beat. I bet we will see this same thing in SMB on 445 or SSL VPN in R2 of W2K3 – e.g., toss out the Contivity 1500 and the Shasta split-tunnel FW Config, because it won’t be needed any longer…
|