In order to run this sample, you need the following software installed on the system:
Server
Microsoft Windows NT version 4.0 with Service Pack 4
Microsoft Exchange Server version 5.5 with Service Pack 1
Microsoft Outlook Web Access (OWA - required for account impersonation)
Microsoft Internet Information Server version 3.0 or later. NT Option Pack (IIS 4.0) recommended.
Collaboration Data Objects version 1.21 (CDO 1.21 is in Exchange SP1)
The ACL COM component (ACL.dll) registered on the system.
Client
Microsoft Internet Explorer version 4.0 or other 4.0 level browser.
Registering the COM Components on Your Server
The CDO 1.21 COM component is already registered and available on your server if you have installed the required Microsoft Exchange Server 5.5 Service Pack 1. To register the ACL.dll COM component, you must first build it using Visual C++ version 5.0 or later (source code and Visual Studio projects are available in the Database and Messaging portion of the Platform SDK under Exchange) and then copy the component to the server. On that machine, type regsvr32.exe ACL.dll at a command prompt to register the component and make it available to the COM runtime.
Configuring IIS to Run the Sample
In order to run the sample, you need to create an IIS ASP application. The following steps can be used to configure the IIS 4.0 web server to run the sample:
Start the Microsoft Management Console (MMC) and open the IIS snap-in.
Create a new virtual directory and select an alias. Map a physical directory to the virtual directory that contains the files for the sample. These files are located in the [c:\mssdk]\Samples\dbmsg\Exchange\aclasp directory of your Platform SDK installation.
Select the permissions for the virtual directory. You must have script access allowed.
View the properties for the new virtual directory. Verify that an application with the alias is listed under the Application Settings in the property page. Select Configuration and look on the Application Mappings property page to verify that files with the extension .asp and .asa map to the dynamic link library ASP.dll.
Finally, to make sure you have the proper directory security set up for your new virtual directory. You can set this security level in the Directory Permissions tab for the virtual directory property page. You must set at least Basic Authentication, NTLM Authentication, or both. If your client applications are going to access the sample across a proxy server or their machine does not participate in the NTLM system, you must enable Basic Authentication. In this case, run the sample using a Secure Sockets Layer (SSL) only. (Basic Authentication sends the credentials in a simple UUEncoded format and thus is essentially plain-text) Otherwise, you can use NTLM authentication and the user's credentials will be provided by the client's browser or requested through a dialog in the standard fashion.
Note If you allow Anonymous access, and the client user does not correctly specify a set of credentials (i.e. runs as anonymous on the web server) the sample will not work correctly. Therefore, turn off anonymous access for this sample's virtual directory to avoid any problems.