XCCC: Exchange 2000 Server SP2 Server-Side OWA Registry Keys

Article translations Article translations
Article ID: 311342 - View products that this article applies to.
This article was previously published under Q311342
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
Expand all | Collapse all

SUMMARY

This article is a summary of the server-side Microsoft Outlook Web Access (OWA) administrative registry modifications available with Microsoft Exchange 2000 Server Service Pack 2 (SP2). Some of these options have been available before the release of Exchange 2000 Server SP2. Other articles and the Exchange 2000 Help file (exadmin.chm) are referenced instead of documenting the features completely in this article.

MORE INFORMATION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.


The following registry keys are set on the server and do not exist by default. They are all located (unless noted otherwise) in the following registry subtree:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeWEB\OWA
For most of these changes to take effect, you must restart the Information Store service.

DisablePassword
Some organizations may want to turn off this feature so that users can only change their passwords while inside the firewalls. When DisablePassword is set to 1, the Change Password button on the OWA Options page is hidden, so that users cannot change their password with OWA. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
297121 XWEB: How to Hide the Change Password Button on the Outlook Web Access Options Page
UserContextTimeout
UserContextTimeout is the value in minutes of user context timeout due to inactivity. User contexts take up resources on the server, so timing them out will allow the server to free up resources if the client is not using them. This is not an authentication timeout. The client's browser will still have a cache of the credentials. If the server times out the user context and the client then performs an action in OWA, the authentication information is sent back up to the server without user interaction and the server creates a new user context. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
294752 XCCC: Session Timeout Settings for Outlook Web Access on Exchange 2000 Server
DisableMultimedia
Outlook Web Access users can download the Exchange Multimedia Control from the Options page. This control enables users of Microsoft Internet Explorer 5 or later to insert audio and video content into messages. Because of the size of multimedia messages, some administrators may want to prevent Outlook Web Access users from taxing Exchange Server resources by sending audio and video content over a wide area network (WAN). For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
288119 XWEB: How to Disable the Multimedia Button in OWA
UseRegionalCharset
When Outlook Web Access users use Internet Explorer 5 or later to send a message, recipients who have mail clients that are not Unicode Translation Format-8 (UTF-8) aware cannot view the message. A solution to this problem is to disable regional characters. In a FrontEnd/BackEnd configuration this change need to be done on both frontend and backend servers. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
273615 XWEB: Mail Clients That Are Not UTF-8 Aware Cannot View Messages Sent from Exchange 2000
UseAltRegionalCharset
If the UseAltRegionalCharset key is not set or it is set to 0, uplevel browsers send messages in UTF-8 and downlevel browsers send messages in the appropriate encoding for the browser's acceptance language. For the following languages, downlevel browsers use the following encodings:
   Korean :   KS_C_5601-1987
   Japanese:  shift_jis
   Western Europe:  windows-1252 
   Russian:  windows-1251
   Central Europe:  windows-1250
				
If this key is set to 1, both uplevel and downlevel browsers send messages in the following encodings:
Korean :  euc_kr<BR/>
Japanese:  iso-2022-jp (JIS)
Western Europe: iso-8859-1
Russian:  koi8-r 
Central Europe: iso-8859-2
				
This key only changes the behavior for browsers configured for the above languages. If both the UseRegionalCharset registry key specified noted above and this UseAltRegionalCharset registry key are both set, the UseAltRegionalCharset registry key will take precedence. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
283214 XCCC: Outlook Web Access May Send a Japanese-Language Message in SJIS
UseISO8859-1
Add the UseISO8859-1 key to use ISO 8859-1 for messages sent with OWA. In Exchange 2000 Server, messages with extended characters are encoded with UTF-8 by default. Because some clients on the Internet do not understand this encoding, a feature has been added to instead use a regional character set. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
281745 XADM: Subject with Extended Characters Sent by OWA May Not Be Readable by Eudora Clients
ResolveForeignUsers
Users in a different Windows 2000 Active Directory forest can read and post messages in your Exchange Server organization's public folders, if this external forest is trusted by your own. However, the names of these external users may not be resolved, which results in blank "From" fields. Local users can reply to the postings of these unresolved users, but no one can send mail directly to unresolved external users. Set this value to 1 so that posts to public folders from trusted AD forests will have a valid name in the From field.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
311845 XCCC: From Field Not Populated With Posts to Public Folders
EnableLogoffWarning
If EnableLogoffWarning is set to 1, an alert message will appear each time the user tries to navigate away from Web client. If the key does not exist (default) or is set to 0, the alert will not appear. You must implement this key on each frontend and backend server for the warning to appear. Restart the W3SVC after you change this key. ReminderPollingInterval
This is the default minimum reminder polling interval in minutes. The default is 15 minutes, but administrators can customize this on a per-server basis. See the Exchange 2000 Server SP2 Help file for more information. ForceClientsDownLevel
This forces "downlevel" behavior in Internet Explorer 5.01 and later. Some proxy servers or firewalls strip out anything they do not understand, such as HTTP-DAV verbs that are used by newer browsers. Unexpected behavior can be exhibited by OWA if these verbs are stripped. One workaround is to use Secure Sockets layer (SSL); then the proxy or firewall cannot see these verbs. If this registry key is implemented, Internet Explorer 5.01 and later browsers will not exhibit the Internet Explorer 5 features.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
296232 XCCC: Empty Inbox When Using Internet Explorer 5 and Later to Gain Access to OWA
NewMailNotificationInterval
This setting is not user-customizable. The default New Mail Notification polling interval is 2 minutes if this registry key does not exist. If it does exist, the interval specified in this registry key will be used. Outlook Web Access users who use Internet Explorer 5 or later can receive a notification message at regular intervals when they receive new e-mail. See the Exchange 2000 Server SP2 Help file for more information about this registry value. Segmentation, also known as Tiered Licensing or Provisioning
Segmentation refers to the ability to selectively enable features of OWA. For example, calendaring, contacts, public folders, calendar reminders, new mail notification, and Internet Explorer 5 support can be disabled or enabled according to service offering. The ability to segment OWA available to administrators after the installation of Exchange 2000 Server SP2. OWA can be segmented on a per-server or a per-user basis. Per-user settings override per-server settings if both are in place.

MinimumFilterLevel (DWORD)
Allows administrators to decide whether users get unfiltered message bodies when going to the View As Web Page link. By default, dangerous content is always filtered, even if "&security=X" is not appended to the URL.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
311154 XCCC: SP2 OWA Segmentation

Properties

Article ID: 311342 - Last Review: February 27, 2007 - Revision: 1.5
APPLIES TO
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbinfo KB311342

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com