With Exchange Server 2003 we have some integrated mobile access features with the Microsoft messaging solution. In this article we firstly discuss the chances and risks of providing mobile access in Exchange and then describe the best practises configuring these ones.
Mobility & Client Access
Ever since its first appearance, many Exchange Admins have attempted to customize the Outlook Web Access user interface. In Exchange 2003, the concept of 'themes' makes things a little easier. This article explains some of the theory.
The RPC over HTTP protocol allows your full Outlook 2003 MAPI clients to connect to Exchange 2003 Servers using HTTP/HTTPS. This solves the problem remote Outlook 2003 users have when located behind restrictive firewalls. The trick is to figure out how to properly configure the Outlook 2003 client to use this protocol. If you have remote users who need to access Exchange 2003 via Outlook 2003, then check out this article and see how to configure Outlook 2003 to use RPC over HTTP.
Following the implementation of Exchange Server in a company it is often desirable connect to users mailboxes using Web Access. Especially with the new release of Exchange Server it is quite interesting to use OWA because you have nearly all the functionality as Microsoft Office Outlook 2003. Within this article we provide a detailed step-by-step guide for implementing Outlook Web Access. Priority will be given to security issues at every stage of the implementation.
Marc Grote presents his first article for MSExchange.org and we are pleased to welcome him on board. Exchange 2003 provides a new cool Feature called Outlook Mobile Access (OMA). OMA allows users to access Exchange data by using mobile devices. Exchange 2003 provides two services for mobile users: Microsoft Exchange ActiveSync and Microsoft Outlook Mobile Access. This article is based on Windows 2003 Enterprise Edition (Build 3790), Exchange 2003 Enterprise RTM and the Mobile Browser Simulator / Gateway from Nokia.
With Exchange 2000 SP2 Microsoft added a feature, known as segmentation, that allows you to quite easily make some rather major changes to the appearance and functionality of OWA.
You can allow remote Outlook 2000/2002/2003 clients to connect to your Exchange Server and take advantage of the full functionality provided by the Outlook MAPI client. Unlike Outlook Web Access, full Outlook MAPI client functionality allows remote users to take advantage of the entire set of mail and groupware features provided by Exchange Server. But you must do this securely. Check out this article to find out how.
Using Windows 2003/XP's new RPC over HTTP feature, Outlook 2003 clients can now connect to Exchange 2003 by encapsulating regular RPC/MAPI communications in HTTPS communications.
I recently finished a five part series on how to publish the Exchange 2003 Outlook Web Access Web site using ISA Server 2000. The inspiration behind this series was the realization that ISA Server 2000 provides an absolutely unique ability to protect my OWA 2003 Web sites in a way that no other firewall in its class can do. Check out this series *before* you publish that OWA 2003 site!
In the first part of this series on how to publish the Exchange 2003 OWA site using ISA Server 2000, we went over some of the advantages the Exchange 2003 OWA site has over previous versions and a high level overview of the steps required to make the internal Exchange 2003 OWA available to external network users via ISA Server 2000 Web Publishing Rules. In this article we'll look at how the ISA Server firewall uses SSL bridging to provide a unique level of protection for your Exchange 2003 OWA site