|
Greetings! Welcome to Vol. 6, No. 13, of Exchange Messaging
Outlook, a biweekly newsletter about Microsoft Exchange and
Microsoft Outlook.
Today's highlights:
- Team Folders Return
- What's Ahead for Exchange
- New Non-Exchange Sharing Tools
Regular features:
- New utilities
- Updated utilities
- Other new resources
Team Folders Return
The Team Folders Kit is once again available for download from
http://www.microsoft.com/technet/prodtechnol/office/downloads/utils/teamkit.asp
after being pulled from the Microsoft site in August because of a
possible security problem. [EDITOR'S NOTE: Less than a week after
we noted the kit's availability, Microsoft pulled it again.]
However, the restored download contains the old version of the
Outlook 2000 View Control (OVC), version 9.0.0.3203. A newer OVC for
Outlook 2000, version 10.0.0.3124, is available at
http://office.microsoft.com/downloads/2000/outlctlx.aspx.
The inclusion of the old version is not as worrisome as it might
sound, because there was no real security vulnerability in the
Outlook 2000 version of the OVC. However, because a malicious web
page operator could have made changes to the display to make the
user think they'd lost data, Microsoft updated the control to
restrict the ability to script it in web pages that are not hosted
as Outlook folder home pages.
The Outlook 2002 version did, however, have a major security
hole. Downloading the latest public Outlook 2002 patch from
http://office.microsoft.com/downloads/2002/olk1004.aspx takes
care of that.
If Team Folders is new to you, it's a tool for building a very
nice team collaboration interface in Exchange Server public folders,
using Outlook's ability to display a web page for any particular
folder. Unfortunately, it apparently never caught on within
Microsoft or elsewhere. Microsoft itself has largely moved on to
collaboration web sites built with SharePoint Team Services (a new
feature in Office XP).
Still, I think Team Folders is a great tool for leveraging your
investment in Exchange Server, especially if you take the time to
read through the self-documenting code for the HTML pages it
creates. I've posted some pointers at
http://www.slipstick.com/dev/teamfolders.htm.
What's Ahead for Exchange
Our last EMO talked briefly about what was ahead for Outlook. If
you're wondering where Exchange is headed, check out John Fontana's
article for Network World Fusion on how a data store shared with SQL
Server will transform Exchange and may cause some firms to skip
Exchange 2000 and concentrate for now just on getting Active
Directory up and running:
Exchange's transformation to .Net coming in 2003
http://www.nwfusion.com/news/2001/1002netexchange.html
Fontana also interviewed Paul Flessner, Microsoft's senior vice
president for .Net Enterprise Servers, and Kevin McCuistion, group
product manager of Exchange server marketing, getting some
interesting answers on the licensing implications of Exchange
hosting .Net web services:
Exchange Changes
http://www.nwfusion.com/news/2001/1022apps.html
New Non-Exchange Sharing Tools
The New and Updated Utilities sections in this issue of EMO
include several noteworthy tools for sharing Outlook data without
Exchange Server. This has been a topic of growing interest since
Outlook 2002 arrived without the Net Folders feature, which
performed mail-based sharing -- not always reliably -- in Outlook 98
and 2000. Two products are in their initial release, while a third
is a major update to a product that first came out summer 2000.
SQLView XP (http://www.oaklodge.com/sqlview/)
allows you to use SQL Server 7.0, SQL Server 2000, or MSDE, the "lite"
version of SQL 2000 that comes with Office XP, as the repository for
Outlook contacts, appointments, tasks and notes. It works with
either Outlook 2002 or Outlook 2000 in Corporate/Workgroup mode,
operating as a MAPI data provider. Because the data is in a database
that can be shared, all users can work from the same data.
Epicenter (http://www.connectedsw.com/Epicenter.html)
automatically distributes address book updates to POP3 and IMAP4
users. The source address book can be Exchange, Lotus Notes, Eudora,
LDAP, Netscape, Outlook Express, or Pine, as well as Outlook. The
recipient has to load the update into Outlook, but this still makes
it relatively easy for everyone to have the same data, especially if
the users aren't normally connected to the same LAN.
WebPublisher for Outlook (http://www.outlookcentral.com/wpo/default.htm)
has undergone a massive overhaul in Version 2 to allow you to
publish any Outlook folder, even Exchange public folders, to the
Web. The destination can be an intranet web server, the Internet, or
a server where Outlook Central offers space for a small annual fee.
If you publish data to Outlook Central's server, you can also edit
it on the Web and have those changes posted back to Outlook.
Synchronization takes place automatically or on demand, but it does
trigger the Outlook Email Security Update's address book prompt. You
may want to consider using the Express ClickYes tool from
http://www.contextmagic.com/express-clickyes/ to bypass the
prompt, if automatic updating is essential. Bonus features include
SMS notifications of upcoming appointments and support for a shared
calendar in the Pro version.
|