Outlook Web Access (OWA) allows any client with a compatible browser to access Exchange Server folders.
The "premium" version of OWA in Exchange 2003 looks and acts much like the Outlook 2003 desktop client, although it does not offer support for the Journal folder. The "basic" version looks more like previous versions. You may want to try both and see which is faster for the conditions your users are likely to encounter. Microsoft Exchange Server Introduction to Exchange Server 2003 has a good chart comparing the feature sets.
For Exchange 2000, you create applications using web forms. No conversion tool is available to turn Outlook forms into Exchange 2000 OWA forms. For resources and tools, see Microsoft Exchange Server Development Technologies. With Outlook 2002 and Exchange 2000, you can connect using OWA and Outlook 2002's support for HTTP mail servers (at least those that use WebDAV). The correct URL would be http://servername.domain.com/exchange/mailboxname.
There are issues using OWA on Vista because the dhtml text editor control used by OWA is not supported in Vista. The Exchange administrator should have installed the security patch for this on the Exchange server months ago, but many have not. The patch will fix this and a similar issue that affects Windows XP users who've installed the security patch described in MS06-013. The hotfix installs a new editor for Internet Explorer which uses an iframe instead of an ActiveX control.
If you are an end-user, contact your administrator. If you are an administrator, see the following links for more information and the hotfix.
You receive an error message when you try to perform any editing tasks, or you must click to enable the compose frame in Outlook Web Access http://support.microsoft.com/default.aspx/kb/911829.
MS06-013: Cumulative security update for Internet Explorer (July 2006)
http://support.microsoft.com/kb/912812
OWA Problems on Vista (Exchange Messaging Outlook Jan 4 2007)
OWA 5.5 specific content is now at Outlook Web Access 5.5
OWA 2000 specific content is now at Outlook Web Access 2000
No comments:
Post a Comment