How OWA Works

How OWA works
Ver 1.0
Layout of OWA
 The client issues a HTTP request using browser using URL.

 The DNS resolves the request and forward to the IIS server.
 The HTTP request flows across the network to the IIS server.
 Exchange registers itself with IIS as a valid application, so when a request is received by HTTP
client IIS redirect the request to application. Davex.dll is an ISAPI extension that includes the
functions necessary to communicate with the Store. Exchange also registersDavex.dll with IIS as
the component to handle all incoming requests for the Exchange application.
 Davex.dll checks the request and contacts the Store through the epoxy
interprocesscommunication channel. Communication goes to the HTTP epoxy stub. Eproxy does
not use RPC.
 The HTTP epoxy stub communicates with Store using exoledb.dll to get the necessary
information from the Store.
 After getting information from Store the reverse path is followed and client gets its mailbox on
browser.
Structure in Exch 2000 and Exch 2003.
Outlook Web Access Before Exchange Server 2007

In Exchange 2003 and Exchange 2000, there were two server configurations: front-end and back-end.
The primary role of a front-end server was to proxy client requests for Outlook Web Access content. The
front-end server accepted requests and forwarded them to the back-end server. The back-end server
hosted content and handled all the business logic and display of the Outlook Web Access user interface.
In the Internet Information Services (IIS) metabase on a front-end or back-end server, three virtual
directories are typically associated with Outlook Web Access:
 /exchange Handles mailbox access requests for Outlook Web Access and WebDAV
 /public Handles requests for public folders
 /exchweb Contains resource files that are used by Outlook Web Access and WebDAV

If you access the /exchange virtual directory through a front-end server, you will be prompted to enter
your credentials. You will then be proxied to /exchange on the back-end server. This will display the
Outlook Web Access user interface.
Structure in Exch 2007.
Significant changes happened in 2007. Exchange 2007 provides Outlook Web Access through the Client
Access server role instead of relying on the front-end/back-end architecture like 2003 and 2000. The key
difference between the Client Access server role in Exchange 2007 and the front-end configuration used
for earlier versions of Microsoft Exchange is that the Client Access server contains the business logic and
also displays the Outlook Web Access user interface. For an Exchange 2007 server that is running the
Client Access server role to provide Outlook Web Access to Exchange 2000 and Exchange 2003
mailboxes, the Client Access server must emulate an Exchange 2000 or Exchange 2003 front-end server.
Virtual Directories
The following table shows the virtual directories that are installed by default on an Exchange 2007
computer. The virtual directories that are installed vary depending on which server roles are installed on
the computer.
Exchange 2007 virtual directories installed in different configurations

Only Client Access server role Only Mailbox role Client Access server role and Mailbox
installed installed role installed
/owa /exchange /owa

/exchange /public /exchange
/public /exadmin /public
/exchweb /exchweb
/exadmin
Accessing Outlook Web Access in mixed mode.
Because there are multiple servers and virtual directories involved in these coexistence scenarios, it can
be difficult to understand which virtual directories users should access. Users should access virtual
directories as follows:
 Users who have mailboxes on Exchange 2007 computers should access /owa or /exchange on
the Client Access server.
 /owa will take the user directly to Outlook Web Access.
 /exchange will use DAV to redirect the user to /owa.
 Users who have Exchange 2003 or Exchange 2000 mailboxes should access /exchange on the
Client Access server. This will return the Exchange 2003 Outlook Web Access experience or the
Exchange 2000 Outlook Web Access experience. Davex.dll will redirect the user to the correct
server if it is necessary.
The simplest strategy in a coexistence scenario is to have all users access the /exchange virtual directory
and let the Client Access server redirect users to the correct virtual directory if it is necessary.
To use the Exchange Management Console to view the properties on an Outlook Web Access virtual
directory
1. In the Exchange Management Console, locate the virtual directory that you want to view by using
the information in step 2 or step 3.
2. If you are running the Mailbox server role on the computer that is running the Client Access
server role, do one of the following:
 To view an Exchange 2007 virtual directory, select Server Configuration, select Client
Access, and then click the Outlook Web Access tab. The default Exchange 2007 virtual
directory is /owa.
 To view a legacy virtual directory, select Server Configuration, select Mailbox, and then
click the WebDAV tab. The default legacy virtual directories are as follows: /Public,
/Exchweb, /Exchange, and /Exadmin.
3. If you are not running the Mailbox server role on the computer that is running the Client Access
server role, select Server Configuration, select Client Access, and then click the Outlook Web
Access tab.
4. In the work pane, select the virtual directory that you want to view, and then click Properties.
5. In the virtual directory properties dialog box, select the tab that contains the properties that you
want to view.
6. View the properties that you want to review, and then click OK.
Unavailable Features in OWA
Some features that are included in Outlook 2007 are not provided in Outlook Web Access. For example,
the following features are not supported in Outlook Web Access:
 Displaying multiple calendars
 Proposing new time for meetings
 The To Do Bar
 Attaching items to items
 Pasting inline images
 The hierarchical address book

Some features require files be stored locally on the client computer so that they can be used. These
features include the following:
 Cached Exchange Mode
 Offline access
 Offline address book (OAB)
 Custom dictionaries
 Customizable views
 .pst files
 Import/export data
 The ability to send messages to Microsoft Office OneNote

Trouble shooting OWA Issues.
1, If OWA not working for some users.
Check for the recipient update services.
2, The filter level affects functionality
If the Pop-up Blocker is enabled in Internet Explorer, and if the filter level is set to the default setting of
Medium, and if the URL for Outlook Web Access is not in the Allowed Sites list, the functionality of Outlook
Web Access may no longer work as expected.

How OWA Works

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

How OWA Works

Uploaded by

Copyright:

Available Formats

How OWA works

 The client issues a HTTP request using browser using URL.

Structure in Exch 2000 and Exch 2003.

Outlook Web Access Before Exchange Server 2007

 /exchange Handles mailbox access requests for Outlook Web Access and WebDAV

 /public Handles requests for public folders

 /exchweb Contains resource files that are used by Outlook Web Access and WebDAV

Structure in Exch 2007.

Exchange 2007 virtual directories installed in different configurations

/owa /exchange /owa

Accessing Outlook Web Access in mixed mode.

 /exchange will use DAV to redirect the user to /owa.

Unavailable Features in OWA

 Displaying multiple calendars

 Proposing new time for meetings

 Attaching items to items

 Pasting inline images

 The hierarchical address book

 Cached Exchange Mode

 Offline address book (OAB)

 The ability to send messages to Microsoft Office OneNote

1, If OWA not working for some users.

Check for the recipient update services.

2, The filter level affects functionality

You might also like