Where Client Access Server Stores Configuration Data
Table 1 outlines where the Exchange 2007 Client Access server role stores configuration and end-user data. It also indicates the backup and restore methods that you should use for each type of data.
In all cases, if you make any changes to the files or default settings for any of the data, document and back up the changes. If nothing has been modified, nothing needs to be backed up.
.gif) Note: |
|---|
|
In Table 1, the file paths all start in the root of the Exchange installation folder. The default Exchange installation folder path is C:\Program Files\Microsoft\Exchange\.
|
Table 1 Locations used by the Client Access server role for configuration and end-user data
|
Critical data
|
Location
|
Backup method
|
Restore method
|
|---|
|
Microsoft Office Outlook Web Access Web site, and Web.config file
|
File system
\ClientAccess\Owa
|
File-level backup
|
File-level restore
|
|
IMAP4 and POP3 protocol settings
|
File system
\ClientAccess\
|
File-level backup
|
File-level restore
|
|
Availability service
|
Active Directory configuration container and file system, including the Web.config file
\ClientAccess\exchweb\ews
|
Domain controller replication or Active Directory backup
File-level backup
|
Use Exchange Management Shell scripts to configure Availability service
File-level restore
|
|
Autodiscover
|
IIS metabase
|
System state backup, metabase export of Web sites
|
System state restore, or metabase import of the Web sites
|
|
Exchange ActiveSync
|
-
Active Directory configuration container
-
File system, including the Web.config file in the \ ClientAccess\Sync folder
-
IIS Metabase
|
Domain controller replication or Active Directory backup
File-level backup
Metabase export of Web sites
|
Use Exchange Management Shell scripts to reconfigure the service.
File-level restore
Metabase import
|
|
Outlook Web Access virtual directories
|
Active Directory configuration container and file system
\ClientAccess\
|
Domain controller replication or Active Directory backup
File-level backup
|
Use Exchange Management Shell scripts to configure clean Outlook Web Access virtual directories to match the old virtual directories
File-level restore
|
|
Registry (There is very limited information stored in the registry by Setup that is not essential to server restore. Unless changes were made to the settings, those changes should be backed up.)
|
Microsoft Windows registry
|
System state backup or registry export
|
System state restore or registry import
|
|
Web services configuration
|
IIS metabase
|
System state backup; metabase export of Web sites
|
System state restore or metabase import
|
Outlook Web Access Web Site
Office Outlook Web Access allows access to Exchange mailboxes via a Web browser. The Office Outlook Web Access Web site files are installed by default when you install the Client Access server role.
For more information about Outlook Web Access, see Managing Outlook Web Access.
IMAP4 and POP3 Protocol Settings
Most configuration information for IMAP4 and POP3 is stored in Active Directory. There are a few user-customized settings stored in the following files:
-
Microsoft.Exchange.Imap4.Exe.Config
-
Microsoft.Exchange.Pop3.Exe.Config
By default, these .config files are located in the following folder: C:\Program Files\ Microsoft\Exchange\ClientAccess\PopImap.
| Note: |
|---|
|
These settings are mainly related to protocol logging settings.
|
For more information about POP3 and IMAP4, see Managing POP3 and IMAP4.
Availability Service
The Exchange 2007 Availability service improves information workers' free/busy data by providing secure, consistent, and up-to-date free/busy information to computers running Microsoft Office Outlook 2007.
Most configuration information for the Availability service is stored in the Active Directory Configuration container. There are a few user-customized settings stored in the Web.config file at C:\Program Files\Microsoft\Exchange Server\ClientAccess\exchweb\ews.
For more information about the Availability service, see Managing the Availability Service.
Web.config Files
The Web.config files contain configuration data for controlling Active Server Page (ASP) Microsoft .NET parameters, such as the ConnectionCacheSize and MaxRequestLength values. Values such as these must be configured by using Web.config because these settings are specific to ASP .NET.
By default, the Web.config files are located at the following paths:
-
C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa
-
C:\Program Files\Microsoft\Exchange Server\ClientAccess\Sync\
-
C:\Program Files\Microsoft\Exchange Server\ClientAccess\exchweb\ews
| Important: |
|---|
|
Only use tools such as Notepad to modify the Web.config files. Modifying the web.config files through IIS will corrupt the file.
|
Autodiscover Settings
Office Outlook 2007 Autodiscover is a new feature in Exchange 2007 that makes Office Outlook 2007 client configuration much easier. Office Outlook 2007 Autodiscover provides configuration information that is required to connect to Exchange.
Autodiscover virtual directory settings are stored in the IIS metabase, and Autodiscover service configuration information for intranet deployment is stored in Active Directory.
For more information about Autodiscover, see Managing the Autodiscover Service.
Exchange ActiveSync
The Exchange ActiveSync protocol, based on HTTP and XML, lets mobile devices such as browser-enabled cellular telephones or Microsoft Windows Mobile®-powered devices access an organization's information on a server that is running Microsoft Exchange. Exchange ActiveSync enables mobile users to access their e-mail, calendar, contacts, and tasks and to continue to be able to access this information while they are working offline.
Exchange ActiveSync configuration data is stored in the following locations:
-
Active Directory configuration container
-
Web.config file in the directory C:\Program Files\Microsoft\Exchange Server\ClientAccess\Sync
-
IIS metabase (specifically the authentication settings)
For more information about Exchange ActiveSync, see Managing Exchange ActiveSync.