Neal's Admin.Notes.

Securing OWA using SSL and enabling Forms-based Authentication

First thing is to create or buy a certificate ( Verisign or Thawte ..there are others ) and assign that certificate to the server. This is performed on the Default Web Site properties, under the Directory Security Tab. Once the certificate has been added, no additional configuration is needed on the Default Web Site. The following steps detail how to enable SSL, and forms-based authentication.

1. On the properties of the Exchange Virtual Directory, go to the same Directory Security tab and under the Secure Communications area, click on Edit. Choose Require Secure Channel (SSL) and check the box next to require 128-bit encryption. Follow the same steps for the Public Virtual Directory.
2. Now that you have enabled SSL, you can enable Forms-based authentication. Go into Exchange System Manager, and go to the properties of the Default HTTP Virtual Server. Under the Settings tab, check the box Enable Forms-based authentication. Optionally, modify the compression settings. Setting this to High will have the greatest performance improvement to users. Forms-based authentication will allow Exchange to display the OWA logon screen instead of the popup window asking for username and password. .

Server Error in ‘/OMA’ Application" Error Message When You View the Outlook Mobile Access Web Site

When you try to view the Microsoft Outlook Mobile Access Web site on a server after you install Exchange Server 2003 on that server, you receive an error message that is similar to the following:

Server Error in ‘/OMA’ Application.
Access to the path “C:WINDOWSMicrosoft.NETFrameworkv1.1.4322Temporary ASP.NET Filesoma4707b1f2a6dd9810” is denied.

This problem occurs when you install the Microsoft .NET Framework on a server that is running Microsoft Windows 2000 or when you install Microsoft ASP.NET on a server that is running Microsoft Windows Server 2003 before you promote the server to the role of domain controller. When you promote the server, the access control list (ACL) permissions that you configured during the .NET Framework or during the ASP.NET installation are modified, and all ASP.NET applications are affected by this change. You must install ASP.NET after you promote the computer to a domain controller for applications that require ASP.NET. This problem may also occur if you upgrade a Windows 2000 domain controller to a Windows Server 2003 domain controller.

To fix this problem, use the ASP.NET IIS Registration Tool (Aspnet_regiis.exe) to reset the ASP.NET ACLs. To run Aspnet_regiis.exe, follow these steps:
* On the domain controller, click Start, and then click Run.
* In the Open box, type cmd, and then click OK.
* Type cd drive:WindowsMicrosoft.NETFramework, where drive is the drive that Windows is installed on, and then press ENTER.
* Type dir, and then press ENTER.
* Note the folder names that are listed, and then locate the folder name that begins with the letter v.
* This folder indicates the version of .NET Framework that is installed on your computer.
* Type cd VersionFolderName, where VersionFolderName is the folder that you noted in step 5, and then press ENTER.
* Type aspnet_regiis.exe -i, and then press ENTER.

Retry OMA - http://server/oma . success !!!